WhatsApp & automation
Hiring a WhatsApp agency: what to include in a bot project brief
Define what a WhatsApp bot agency should build, which systems it can access, who owns the account and how you will test the customer journey.
What is the difference between a WhatsApp agency and a bot builder?
A WhatsApp agency may handle conversation design, campaign operations, integrations and ongoing support. A WhatsApp bot agency may focus more narrowly on building automated conversations. These labels do not establish what is included. Ask for a written scope that separates setup, customer support workflows, marketing activity, integration work and maintenance.
Start with one customer journey. A hypothetical appointment business might need a bot to explain services, collect a preferred time and pass the request to a staff member. That is different from a bot that directly reserves a slot in a live booking system. The second requires availability checks, failure handling and clear rules about who can change a booking.
List the data and actions the bot needs
For every question the bot will answer, name the source of truth. Store opening hours can come from an approved knowledge document; an individual order status needs a customer-specific lookup. Decide how the user will be verified before exposing private information. A phone number alone should not automatically grant access to every record a person mentions.
Separate read-only actions from changes. Looking up a booking, creating a booking and cancelling a booking should be independently scoped and tested. Define what happens when a connected system is unavailable. The bot should say the action could not be completed, not invent a confirmation or silently retry a consequential change.
Define ownership, consent and the support boundary
Document who owns the business account, phone number, integration credentials, conversation content and deployment. Ask for a handover plan, access removal procedure and named maintenance contact. Keep messaging charges, platform subscriptions and development fees separate in the proposal so the recurring cost is understandable.
WhatsApp's business policy requires opt-in for subsequent contact and honoring opt-out requests. Ask the agency to demonstrate how those preferences are captured and enforced. Include a route to a real person, published support availability and a policy for unresolved questions. Platform policy review is part of launch preparation, not a one-time guarantee of compliance.
Use acceptance tests instead of a polished demo alone
Prepare sample conversations for the happy path, an unknown question, a misspelled request, a duplicate submission and a failed integration. Add an opt-out conversation and a request for a human. For each, write the expected response and the expected backend state. A smooth demo is useful, but it does not replace checking whether the right record was created once.
Begin with a limited pilot and a staff member watching unresolved conversations. Expand only after the business can maintain answers and respond to escalations. A useful brief names what the bot will not do as clearly as what it will do; that is how a small first version stays dependable.