Chatbot flow builder with analytics and handoff to an agent or ticket

Bot for the repetitive work, agents for what matters

Most support messages are repetitive: business hours, order tracking, return policy. Hodhod's flow builder lets you answer these with a simple flow, collect the details you need (email, order number) before the conversation reaches an agent, and pass only the requests that truly need a human. Step-by-step guide: build a website chatbot without coding.

17 step types to build your flow

Steps are organized into groups:

• Menu: topic, subtopic, FAQ and answer (with a "Did that help?" question).
• Messages: a bot message with an image and a link button.
• Asking the customer: collect information (text, email, phone number, number or date), yes / no, multiple choice and ratings (stars, emoji, NPS or thumbs up and down).
• Logic: conditions (based on business hours, page, language and more), A/B tests and jump to step.
• Connections and actions: a webhook to fetch data from an external API, and an action to add a label, set a priority or create a ticket on the conversation.
• Handoff: connect to an agent or team, and end.
• Note: an internal comment on the canvas that customers never see.

Handoff to an agent or a ticket

Every flow has a "dead end": the point where the bot isn't enough. There you can connect the customer to an agent or team, or, if you're outside business hours and an instant answer isn't possible, create a ticket from the same conversation so nothing gets lost.

Test before you publish

• Simulator and preview: walk through the flow like a real customer.
• Validation: the editor flags incomplete steps and dead ends before you publish.
• Versions: every publish is a version, and you can roll back to the previous one.
• Templates, export and import: start from a ready-made template, export a flow or import one from elsewhere.
• Settings and triggers: choose which inbox the flow runs for and under what conditions it starts.
• Safe webhooks: the webhook step works with security controls, not an unrestricted request.

See whether the flow really works

The "Flow analytics" section shows how visitors move through your flow:

• Funnel and drop-off for every step: where customers abandon the flow.
• Handoff rate and resolved-in-flow rate.
• 19 report types (overview, funnel, steps, paths, handoffs, entries, audiences and experiments) with filters for date range, inbox, language, device and version.
• On-canvas view: see the numbers directly on the steps in the editor and fix the weakest one.

Frequently asked questions