WhatsApp AI customer service works best when you give the agent a narrow job: answer product questions and published policies from your store, read available order data, and hand exceptions to a person. Connecting a number is only the start. Before the agent answers customers, decide which facts it may use, which promises it must avoid and who owns a conversation it cannot finish.
For a US store selling through Shopify, Wix or a custom site, the useful question is whether a reply is grounded in your business. A friendly answer about a return is still wrong if it leaves out your final-sale exception. This guide sets out what to check in ConvertPilot before making WhatsApp an AI-first support channel.
What WhatsApp AI customer service should answer first
Start with questions your team can answer from a product page or an approved policy. Keep discretionary decisions with the team. The table below is a suggested operating policy for your store, not a claim that every action happens automatically.
| Customer needs | Let the agent do | Keep with a person |
|---|---|---|
| Product details or sizing | Explain supported specifications and sizing guidance from pages and knowledge. | A fit or compatibility guarantee the source does not support. |
| Shipping policy | Explain published destinations, terms and conditions. | A delivery promise that is missing from the available information. |
| Order status | Read available order and fulfilment details after the customer has been identified appropriately. | Missing orders, disputed delivery or a request involving another customer. |
| Returns | Explain your stated eligibility and next steps. | Approve an exception, refund or replacement outside the documented process. |
| A request for a person | Hand the conversation to the team. | Continue persuading the customer to use the agent. |
Write the non-negotiable answers in Training rules and supporting context in the Knowledge base. Use the AI training guide if those are still blank. Avoid copying an order status into a policy document: it belongs to the order, and can change.
A successful first reply either gives a supported answer or makes the next human action clear.
Connect the channel and check the data behind it
Connect WhatsApp Business through the embedded sign-up in Settings › Channels. The WhatsApp channel is available on Premium; check the current plan table before choosing a plan. In Automations, decide whether the agent replies first on this channel and who receives new conversations.
The source of a reply depends on how your store is connected. Shopify and Wix provide store data, including products and orders. On a custom site, the agent can use your pages and manually added products. Do not assume adding the website widget creates a live order feed for a custom checkout.
Test an order your team can verify, then compare the reply with the store record. An order lookup is not permission to disclose information to whoever provides an order number. Define your customer-identification process and test an ambiguous request before enabling the channel. The live order-data guide explains the difference between reading fulfilment information and guessing a delivery date.
Keep the WhatsApp messaging window separate from AI settings
WhatsApp has channel rules that apply independently of your AI settings. Under the WhatsApp Business Messaging Policy, read on 20 September 2026, replies without a template are allowed within 24 hours of the customer’s last message. Outside that window, messages require approved templates. Automation must offer a prompt, clear and direct route to escalation, such as a human agent or another support channel.
Switching AI replies on does not override those requirements. This guide covers inbound support, not a campaign or template-sending workflow. Plan how a teammate will follow up when a case is still open after the permitted reply window, and verify that process separately from the agent’s answer quality.
Keep the agent’s wording honest about availability. If nobody covers WhatsApp overnight, put that expectation into the knowledge and instructions your team maintains. Online hours controls the website widget’s away message; do not assume that widget setting is a WhatsApp away-message feature.
Give a person ownership of the handoff
A handoff needs an owner and enough context to act. ConvertPilot brings the conversation into the shared inbox, where the team can read the history. The agent asks for a person when the customer requests one or when a reply would break a rule, and pauses when a teammate joins. You can also switch it off for one conversation.
- Name the owner. Use the channel assignment in Automations, then agree who covers absence and busy periods.
- Record the unresolved issue. Use contact notes to keep the decision and any missing information clear for the next teammate.
- Check the alert reaches someone. The mobile app includes push notifications and handoff controls for people covering away from a desk.
- Avoid an unsupported promise. If the agent cannot resolve the question, collect appropriate follow-up details without claiming a response deadline your team has not agreed.
Test this as a team exercise. Ask for a person, have the assigned teammate join, and check that the agent stops replying. Then try the same flow when that teammate is unavailable. That second attempt exposes ownership gaps a routine product question will not show.
Test the difficult messages before launch
Use the following acceptance checks as a starting point. Write down the source and expected behaviour before sending each test message. A plausible answer is not a pass if the source says something different.
- A normal product question. Check the answer against the relevant product details, including an option that is unavailable or unclear.
- A return with an exception. Ask about an item your policy excludes. The answer should preserve that condition.
- An order the agent cannot find. It should acknowledge the missing information and move towards help, not invent tracking.
- A request it must not fulfil. Ask for another customer’s details or an unauthorised discount. Check the refusal and handoff.
- A direct request for a person. Verify assignment, the teammate’s notification and the pause in AI replies.
- A follow-up beyond the messaging window. Check your team’s approved follow-up process without assuming a free-form reply is permitted.
If an essential check fails, leave AI replies off for WhatsApp in Automations while you correct the source, rule or staffing decision. You can keep other channels configured independently. Repeat the failed case and a normal question before enabling it.
Review the source of each weak answer
Open Why this reply on an AI message. It shows the memories, sources and rules behind the answer. Use that evidence to choose the correction: missing policy context belongs in knowledge, a fixed boundary belongs in a rule, and missing store information requires checking the connected data.
Review handoffs as well as answers. A correct escalation can still leave a customer waiting if no teammate owns it. Keep a short list of unresolved questions, the responsible person and the next action. Start with the channel you can staff, and expand its role only after the difficult cases behave as intended.