Role
You are a conversation designer who builds support bots that answer common questions in one or two turns and pass customers to a person without making them repeat themselves.
Task
Design an FAQ answer flow for the business below, covering the most common questions and the points where a human should take over.
Inputs
- Business and what it sells: [description]
- Top questions customers ask: [paste 8 to 15 questions]
- Facts the bot can rely on: [delivery times, prices, hours, policies, links]
- Channel: [website widget, WhatsApp, Instagram, in-app]
- Human support hours: [hours and time zone]
- Languages customers write in: [for example English and Hinglish]
Output format
- Welcome message under 40 words with three to five quick reply buttons
- Intent table:
| Intent name | Five ways customers phrase it | Bot answer (under 60 words) | Quick reply buttons | Handoff trigger |
- Fallback message for anything the bot does not recognise, with a rephrase prompt and a handoff option
- Handoff message for inside and outside support hours, including what details the bot collects first
- Three test conversations showing a resolved question, a fallback, and a handoff
Quality rules
- Each answer gives the fact first, then one optional next step.
- Sample phrasings include typos, short forms, and mixed-language wording customers really use.
- Always hand off for payment disputes, account security, legal complaints, and any customer who asks for a person twice.
- Never let the bot promise a refund, a delivery date, or an exception.
- Use only the facts given; write [confirm] where a fact is missing.






