What should a WhatsApp chatbot project brief include?
Direct answer. A useful WhatsApp chatbot brief names five things: customer journeys, approved answers, captured data, human handoff and acceptance tests. Start with one bounded workflow; a menu bot, a CRM integration and an AI assistant are different purchases.
Commissioning work now? Compare the WhatsApp chatbot setup scope, or send the project details for a scope check.
Describe the customer task, not the word chatbot
Write the questions the customer arrives with and the action the business wants to take next. A local service company might need to collect a service type and preferred contact time; an existing store might need an order lookup. These are example workflows, not client results. Choose the first journey you can actually support with reliable answers and an available person.
WhatsApp’s first-party platform overview distinguishes the Business Platform and its APIs from the Business App, and describes templates, automation, routing and integrations. Tell your supplier which account and phone number you use today. Ask how the proposed setup fits that starting point rather than assuming that every existing inbox can be replaced without a transition plan.
Write an answer source and a boundary for every branch
For a menu or FAQ bot, supply the exact approved responses, the person who can update them and the cases that must leave the flow. A price list can be linked or maintained from a defined source; avoid copying it into several separate branches with no update owner. When the answer is not known, the bot should ask a useful clarifying question or hand off.
Separate deterministic menus from generated AI replies. The latter need their own model access, usage charges, knowledge source and evaluation cases. “It answers everything” is not a scope. Ask which subjects it will refuse to guess about, how stale information is updated and what staff see when a conversation needs review.
| Case | Expected behaviour | Evidence |
|---|---|---|
| Known enquiry | Approved answer and next step | Transcript matching the approved source |
| Missing information | Relevant clarification | Required fields captured without a guess |
| Unknown/custom request | Human handoff | Named team receives the agreed context |
| Lead capture | Correct destination record | Contact and requested work match |
| Operating boundary | Excluded task explained | No invented price, answer or outcome |
Make human handoff a complete workflow
Name the destination team and the information they receive: contact, requested service, the customer’s answers and the reason for handoff. Decide whether the bot pauses, what the customer sees while waiting and how a staff member resumes the conversation. Do not promise immediate or round-the-clock human support unless the business actually staffs it.
A flag in a spreadsheet is not the same thing as an agent inbox. A CRM lead is not the same thing as the full conversation. Define which result is needed and test it. This is particularly important when comparing two quotes that both say “lead capture” but deliver different records.
Keep platform and operating costs separate
The implementation fee pays for the defined work. Platform messaging, any business-solution-provider subscription, connected software and optional AI usage may be separate. Use the current WhatsApp pricing information and your chosen provider’s terms for the actual route; do not turn an old per-message example into a permanent operating budget.
The current ZoopCoder WhatsApp chatbot scope lists a bounded menu/FAQ and lead-capture setup, human handoff and template submissions. It separately excludes AI replies and their usage fees, as well as bulk promotional campaigns. Check the live page for price and limits before checkout; Meta review or business verification outcomes are not a deliverable a supplier can guarantee.
A test conversation is more useful than a feature list
Prepare a short set of example conversations covering the main path, a wrong menu answer, an unknown question, a handoff and an interrupted conversation. Specify what is saved and what staff receive. Use test contacts controlled by your business; do not send unsolicited messages to real customers as an acceptance test.
Example brief: “Start with a service enquiry flow. Capture the selected service, name and contact preference. Save the lead to our agreed destination, flag custom requests for a person, and use approved answers only. We will provide the FAQ wording. AI-generated advice, payment collection and promotional broadcasts are outside this first phase.” Adapt the example to your business rather than claiming it is a universal ideal bot.
Buy the smallest complete journey first
A working first journey can reveal missing inputs before you commission a larger integration. If you already have a bot, provide a reproducible transcript of one failure and compare a single chatbot bug fix with a rebuild. If the real problem is staff response, a more elaborate menu will not solve it by itself.
We publish this guide as a chatbot service provider. It describes how to make the work testable, not a claim of increased sales or an affiliation with Meta. Review the current official platform rules and the proposed account-access arrangements before commissioning the setup.
Questions before you commission the work
Is a menu chatbot the same as an AI chatbot?
No. A menu or FAQ flow follows defined responses; generated AI replies require separate scope, knowledge controls, evaluation and usage costs.
What should human handoff include?
Name the responsible team, destination, context supplied, customer waiting message and who resumes the conversation.
Does a setup fee cover all future WhatsApp messages?
Only if the agreement explicitly says so. Check current platform and provider charges separately from implementation.
Sources and scope
Primary documents checked 3 November 2026. The commissioning tables and sample briefs are editorial suggestions, not platform requirements or measured client outcomes. Live service pages govern the current price and included work.