ManyChat Built a Great Button Tree. Real Quotes Don't Stay Inside It.
Read in: English · 中文 · Bahasa Melayu
A client messages, gets pulled through a few menu options, and lands on a quote. Then they ask a follow-up question that was never one of the menu buttons, and the reply that comes back does not remember anything from the last three messages. That is the moment a job is lost, not because the price was wrong, but because the conversation forgot itself.
Where button-driven flows work, and where they stop
ManyChat and similar tools are genuinely good at the first step: narrowing a broad enquiry down with a few tappable options, this service or that one, this area or that one. The flow works exactly as designed, right up until the client types an actual sentence instead of tapping a button. "Can you also do Saturday instead" is not a menu option. Once the client goes off-script, a flow built around fixed choices has nowhere natural to put that information.
What a lost-context conversation looks like
A contractor gets asked "what's your rate for a small bathroom repaint," replies hours later with a flat number, and the client has already asked two follow-up questions in between: is it urgent, what date works, is there a callout fee. None of those got answered in the same breath as the rate, so the client is left piecing together a quote from three disconnected replies instead of one clear answer.
Keep the job details in one place
The fix is not more menu options. It is treating every quote conversation as one continuous thread where the job type, urgency, preferred date and any specifics the client already gave stay attached, no matter how the conversation branches. A client should never have to repeat something they already told you three messages ago.
Where a sales assistant fits
This is the specific gap YunaChat closes. Instead of routing a client through fixed menu choices, it holds the conversation in natural language, the way a client actually talks, and keeps the job details (urgency, date, address, the specifics they mentioned) attached as the conversation continues. A client who asks a follow-up question outside the original flow still gets an answer that accounts for everything they already said. It works on the WhatsApp number you already use. See pricing when you are ready.
The short version
A button-driven flow is a fine way to start a conversation, but it breaks the moment a client asks something outside the menu, and that is exactly when jobs get lost. Keep the job type, urgency, date and specifics attached to the conversation as it continues, so a client never has to repeat themselves. A sales assistant that follows natural conversation, not just menu taps, keeps that context intact from the first message to the quote.