Why one message often contains three questions
Customers do not write like forms. A refund, a price and an opening hour arrive in the same paragraph, and menus cannot handle it.
Here is a real message, lightly anonymised:
Hi, are you open Saturday? Also how much is the deep clean for a 3 bed, and I paid twice last month by accident can someone check
Three questions. Three different systems. One paragraph, no punctuation, sent at 21:40. This is what customer contact actually looks like, and it is the single biggest reason menu-based automation disappoints.
Forms assume decomposition. People don’t decompose.
Every menu, every chatbot flow and every “choose a department” widget makes the same assumption: that the customer arrives having already sorted their problem into one category.
They have not. They arrived with a situation, and the situation spans categories. Asking them to pick one is asking them to do the classification work on your behalf — and the moment they pick the wrong one, they are in a branch that cannot help them, and the only exit is to start again or give up.
Most give up. Which is why the abandonment on these flows is high in exactly the place it hurts most: the messages with a billing problem inside them.
The three failure modes
When a multi-part message hits a single-intent system, it fails in one of three ways:
- It answers the first question and drops the rest. The customer gets Saturday’s opening hours and no price, no refund. They now have to write again, and they are already annoyed.
- It routes on the loudest keyword. “Refund” wins, so the message lands in billing, who cannot quote a deep clean and bounce it back.
- It asks the customer to pick. Which restarts the conversation and loses the context they already typed.
All three produce the same outcome: the customer does more work than they did before you automated anything.
What handling it properly requires
Not much, conceptually — but it has to be true of the whole system, not one part of it:
- Read the whole message before acting. Obvious, and routinely not done.
- Hold more than one open thread at a time. Saturday’s hours and the deep clean price can both be answered immediately. The double charge cannot.
- Split the response. Answer what is answerable, and escalate only the part that genuinely needs a person — with the original message attached.
- Do not silently drop the remainder. If one part is going to a human, say so in the same reply.
The result for the message above is one response that gives the hours and the price, says a person is checking the duplicate payment, and puts exactly one item — the billing check — in front of a human, with context.
Why this matters more than it sounds
The multi-question message is not an edge case. In the samples we have looked at it is somewhere between a quarter and a third of all inbound text, and it over-indexes hard on the messages that carry money in them.
Optimising for the clean single-intent question is optimising for the traffic that was never the problem.