How to Create and Add a Formito Chatbot to a Website

You can build and publish a Formito chatbot without writing code: start from a ready-made template (or a one-click converter), add messages, inputs, and actions in the visual builder, then share the bot through a code snippet launcher, a page embed, or a direct chatbot URL. Responses appear in your dashboard and can be exported as a spreadsheet. This guide covers the full path from an empty builder to a live widget, plus the common places people get stuck.

Before you start

Formito's own walkthrough describes a three-step flow — create, share, track — and the builder is explicitly designed for non-technical users. To follow it you need:

• A Formito account (the site links a Pricing page; check it for current plan limits before you commit).
• Access to your website's HTML or a CMS that accepts a custom code snippet, if you plan to use the launcher or embed option.
• A clear goal for the bot: lead capture, feedback survey, or support are the three use cases Formito organizes its templates around.

If you only want to test the experience, the chatbot URL option means you can share a bot without touching your site at all.

Step 1: Create the chatbot

1. Log in and choose a starting point. Formito offers ready-made templates and one-click converters — the converter path is meant for turning an existing form into a conversational flow, while templates cover scenarios like tour booking, real estate agent, photography service, and "buy me coffee."
2. Open the visual builder. Add messages (what the bot says), inputs (what the visitor types or selects), and actions (what fires immediately after, such as an automation step).
3. Order the blocks into a conversation. The builder is drag-and-drop style and no-code, so the sequence you see is the sequence the visitor experiences.

Expected result: a complete conversation flow you can preview before publishing.

Common sticking point

People often build the conversation but forget the actions. A message without a following input or action is a dead end — the visitor has nothing to do. For every message that asks something, confirm there's an input to capture the answer and an action that does something with it.

Step 2: Share the widget

Formito gives you three distribution options. They are not interchangeable, so pick based on where the conversation should live.

Expected result: the bot is reachable by your intended audience through at least one of these routes.

Common sticking point

If the launcher doesn't appear after adding the snippet, the usual causes are the snippet being placed outside the page body, a CMS stripping the script, or caching. Test the chatbot URL first — if that works, the bot itself is fine and the problem is on the embedding side.

Step 3: Track results

Open your dashboard to browse responses as they come in. From there you can:

• Print a single record when you need one response in isolation.
• Save all responses to a spreadsheet file format for analysis or handoff to a CRM.

Expected result: you can see every completed conversation and get the data out of Formito when you need it.

What each use case looks like in practice

Formito frames its templates around three jobs, and the build steps differ slightly for each:

• Lead capture. The bot opens the conversation with visitors rather than waiting for a form submission. Formito's pitch is that this lowers bounce rate and raises engagement, and that leads get captured outside working hours. For example, a tour-booking business can run the Tour Booking template so after-hours visitors book a slot instead of leaving.
• Feedback and surveys. Ready-to-use templates cover product feedback, website questionnaires, post-event surveys, and sponsor applications. The bot asks, the visitor answers, and the dashboard collects it.
• Customer support. Put contact forms, FAQs, a help center, and ticketing at the visitor's fingertips in one conversation. This suits teams that want a first-response layer before a human picks up.

Deciding whether Formito fits

Formito is a reasonable choice if you want a conversational replacement for a static form, need it live quickly without developer time, and are comfortable with a template-first approach. It is a weaker fit if you need deep custom logic beyond messages, inputs, and actions, or if you require a specific integration that isn't among the listed automation options — check the Pricing page and feature list for your must-haves before building.

A practical way to decide: build one bot from the template closest to your use case, share it via the chatbot URL, and send it to a handful of real visitors. If the conversation captures what you need and the dashboard export is usable, move to the launcher or embed. If not, you've lost an hour rather than a migration.