Most automated conversations fail for the same handful of reasons, and none of them are technical. The flow works exactly as drawn — it is just that nobody wants to have that conversation.

Here is what separates a flow people complete from one they abandon.

1. Know what the flow is for

A flow should have one job, stated in a sentence: qualify this enquiry and book a call. Confirm this booking and collect the details. Answer this question and offer the next step.

Flows that try to be a menu for the entire business produce menus with nine options, and nine options produce no taps at all.

2. Turn every question into a tap

Every question you can answer with a button is one the flow cannot misread, and one the customer does not have to type on a phone. Buttons also open the reply window, which a link click does not.

Reserve free text for things that genuinely vary — a name, a date, a specific request. Everything else should be a choice.

For anything longer than two questions, use a form inside the chat rather than a conversation. Completion rates are dramatically higher, because the customer can see the whole thing at once instead of being drip-fed.

3. Ask for the minimum that makes the next step possible

Every field you add costs completions. Before including a question, ask what changes if you do not have the answer. If the honest answer is “nothing until later”, get it later.

A travel enquiry usually needs four things: destination, rough dates, party size, budget range. That is enough for a consultant to quote. Passport numbers can wait.

4. Design the exit before the path

The best automated conversations end at the right moment. Decide in advance where a human takes over, and make it a deliberate step rather than the flow running out of nodes.

A handover should carry everything collected with it, so the first human message is a useful one rather than a repeat of questions the customer has already answered.

5. Plan for the off-script message

Someone will type something you did not anticipate — usually in the middle of your carefully designed path. If the flow has no answer for that, it dead-ends and the customer leaves.

The fix is a catch-all that answers from your knowledge base, so an unexpected question still gets a real answer and the conversation continues instead of stalling.

6. Test it as a customer, not as its author

The builder can tell you that a branch is connected. It cannot tell you that the wording is confusing, that the third question feels intrusive, or that the confirmation message does not actually confirm anything.

Run it on your own number. Then have somebody who did not build it run it, and watch where they hesitate.

7. Measure completions, not sends

The number that matters is how many people finished, and where the rest stopped. A big drop at one step is a message problem — usually a question that feels like too much to ask at that point in the relationship.

A flow that works, in outline

• Greet and state the point — one line, so the customer knows what is about to happen
• Two or three taps — the facts you genuinely need
• Do something visible — book the slot, send the link, create the lead
• Hand over with context — to a named person, with everything attached
• Catch-all underneath — so an off-script question is still answered

Short, specific, and honest about when a person should take over. That is nearly the whole craft.