Landbot Alternatives

A flow is excellent where the path is known: qualifying a lead, booking a slot, collecting details before a handover, running a quiz. It is predictable, testable and it never invents anything. That is genuinely valuable, and it is why Landbot has the following it does.

A flow is poor where the question is unpredictable — which is most of e-commerce support. "Does this fit a 15-inch laptop", "is the blue one back in stock", "how long is delivery to Portugal" cannot each be a branch. Retrieval handles those by answering from your catalogue and policy pages, and where it cannot, it hands over to a person.

The billing consequence matters: in a flow tool, AI is the expensive escape hatch and therefore rationed. In a retrieval tool, AI is the normal case, so metering it separately would make no sense.

Beyond the allowance, AI chats are EUR 0.10 each. Prices are published primarily in euros by a Spanish entity, and the headline figures are annual-billing rates. Prices as published on the vendor's own site in September 2026.

Vatdi — retrieval-based website chat trained on your store, with AI on every plan including the free one. Free covers 15 conversations a month; Starter is $4.49 for 150; Grow is $7.49 for unlimited conversations. Native plugins for seven self-hosted platforms handle catalogue sync and live order lookup.

Tidio — website chat with flows and the Lyro AI add-on, priced by conversation volume; a reasonable middle ground if you want both shapes.

Chatfuel — if the flows you care about are really Instagram and WhatsApp automations; AI PRO is $49 a month and the free plan has no AI.

Botpress — if you need the bot to take actions in back-end systems and you have developers. Free is a hard cap of 100 conversations; Plus is $150 a month billed annually with 250 conversations, and extra packs of 100 cost $65.

Kommunicate — AI plus a human inbox in one console from $40 a month, with 250 conversations and one seat included.

The worry about moving off a flow builder is usually about losing control, so it is worth being specific about what control remains. You still choose the greeting and the follow-up bubble, the quick replies shown as buttons, which fields the pre-chat form asks for and which are required, the tone and reply length, whether product links appear at all, and how many products a single reply may include. Handover has its own rules: the AI can offer a person when it fails, and agent hours decide whether that offer is made at all.

What you give up is the branch. There is no canvas where you draw the conversation, and no conditional path that guarantees a fixed sequence. In exchange, adding a product line, a policy change or a new FAQ does not require touching a diagram — the content sync carries it.

• How many of your conversations are genuinely scripted? If it is most of them, stay with a flow builder.
• Is your AI allowance separate from your chat allowance? Two meters means two ways to run out.
• Does the tool read your catalogue? Answering product questions from a feed is different from answering them from a flow you wrote.
• What happens at handover? Check the inbox, the alerts and whether availability hours exist.
• What is the real annual cost? Headline prices in this category are usually annual-billing rates.

Assume a store with 300 support conversations a month, of which perhaps 250 are open questions the AI should answer and 50 are scripted paths.

The scripted 50 are the honest caveat: Vatdi handles them with quick replies, a pre-chat form and handover rules rather than a designed flow. If those 50 are your highest-value interactions, a flow tool earns its price.

Be clear-eyed: a retrieval assistant will not reproduce a designed multi-step flow with conditional logic and payment steps. Vatdi has a pre-chat form with fields you choose, quick replies, and handover rules — but no visual flow canvas, no branching logic and no payment collection inside the chat. If your best-performing asset is a carefully built qualification flow, keep it.