Separate the app, platform integration and bot scope
When defining an AI support scope, do not treat the WhatsApp Business app and Business Platform integration as identical setups. Examine team workflows, required system connections and features available to the account. Basic greetings and quick replies involve different preparation from an integrated flow that retrieves orders and assigns conversations across a team.
Write the permitted topics first. Product information, opening hours, delivery explanations and escalation may be separate flows. AI is not required for every question; a clear menu or rule-based response can address some needs. Do not apply one eligibility assumption to a bounded business-support function and general-purpose AI assistant distribution. Review the current applicable terms separately.
Define excluded actions too. Refund decisions, exceptional prices and changes to customer accounts may require separate authority. When a response creates a service promise, it should match the real operating process. “Answer everything” is too vague to serve as an acceptance condition.
Information
Answer bounded questions from approved current content.
System lookup
Use an authorized source with the relevant identity and record checks.
Escalation
Provide a defined route for uncertain, excluded or specially authorized decisions.
Prepare account, number and access ownership
An automation setup should use clearly owned business accounts and access. Identify the number, administrator, integration provider and team inbox. Verify current account architecture and migration or coexistence conditions through Meta and provider documentation. Do not assume that every existing number follows the same transition path.
The technical team should separate test and live environments and manage event delivery and credentials appropriately. Secrets do not belong in briefs, customer messages or public logs. Record ownership and management methods rather than secret values. Establish account ownership early so changing an agency or provider does not remove the business’s access.
The first acceptance check extends beyond receiving and sending a message. Can support staff access the journey, can the correct person take over, and are failures visible? Use dedicated test conversations for these checks. Adding a number or creating a provider account does not demonstrate that the whole operating flow is complete.
FROM READING TO A NEXT STEP
Define the support flow
Share the customer questions, account setup and handoff owner.
Implement the service window and template path correctly
In the messaging automation plan, distinguish user-initiated contact from business-initiated messages. WhatsApp’s current public policy permits replies without a template during the 24-hour customer service window, opened or reset by each user message. Outside it, approved Message Templates are required. A bot’s reply is not a new user message that resets the window.
Knowing a number does not independently authorize unwanted messaging. Design permission and expectation flows around message purposes, and recognize opt-out requests. Check template category, language, variables and approval state. An approved template does not automatically establish the legal or commercial suitability of an entire campaign; applicable business obligations require their own review.
Confirm current pricing, limits and provider fees for the account and usage. This guide does not promise a fixed message price or a universally free integration. Decide what happens when the window closes: an appropriate template, another support route or a human queue. Repeatedly attempting free-form sends is not a working fallback.
Design approved answers and escalation together
The chatbot knowledge base identifies current product, delivery and support guidance. A bot should not invent company prices or policies from general model knowledge. Record the owner, approved version and conditions for each source. Changing stock or personal order status requires a separately designed authorized lookup.
WhatsApp’s policy requires prompt, clear and direct escalation paths alongside automated responses. Suitable options can include team takeover, telephone, email or web support. Define the response when someone requests a representative or the source is insufficient. A loop that repeatedly asks the same question does not provide a useful handoff.
In an original illustrative scenario, a customer asking about dimensions receives approved product information, while someone requesting a delivery exception is routed to the relevant team. This is not a Prix implementation or measured outcome. Explain after-hours conditions without promising a response time that the support team cannot meet.
Verify the pilot through message quality and support operation
The AI agent pilot approach also applies to normal and boundary chatbot scenarios. Check missing information, wrong language, excluded questions, closed windows, rejected templates and representative requests. Use an appropriate test environment that does not affect actual customer queues or account data.
The handover should contain the flow map, sources, template list, escalation owners and data access and retention plan. Operations staff need to know how to stop automation and return to manual support. Recheck relevant scenarios after model or content changes; one working answer does not verify every future version.
Evaluate correct routing, unanswered questions and human correction workload alongside response counts. Examine blocking or complaint signals separately. Avoid universal resolution rates or guaranteed conversion improvements. Consider expansion only when there is evidence of reliability in the current flow and capacity to manage the additional support load.
Prepare
Assign account, source, messaging and escalation ownership.
Pilot
Test normal, boundary and outside-window scenarios in a dedicated flow.
Operate
Monitor quality, unresolved questions and human workload; narrow scope when needed.
BEFORE YOU DECIDE
Frequently asked questions
Does a chatbot require AI?
No. Clear menus and rule-based answers can address bounded needs. AI may support interpretation of varied questions, while source verification and escalation ownership remain. Define the questions to solve before selecting the technology.
Does a bot reply reset the 24-hour window?
The policy opens or resets the window through user messages. Do not treat the bot’s own send as another user message. Plan an appropriate approved-template path for contact outside the window.
Can I message everyone whose number I know?
A known number is not sufficient permission by itself. Define expectations, relevant consent and an opt-out route. Review platform rules alongside the business’s applicable obligations.
Is AI eligibility identical for every account?
Account, country, purpose and current terms can matter. Distinguish business support from general-purpose assistant distribution. Confirm the relevant use-case scope with the provider rather than assuming universal availability.
How is setup completion established?
Verify sources, templates, escalation, failure and stopping scenarios as well as message exchange. Support staff should be able to operate the flow. A single test message does not prove readiness across all conditions.
LET’S DEFINE THE SCOPE
Define the support flow
Share the customer questions, account setup and handoff owner.
Discuss the chatbot plan