What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
A WhatsApp chatbot can handle routine e-commerce questions—especially order tracking, shipping FAQs, and return instructions—but it should not be left to make sensitive decisions or strand customers without human help. A production-ready setup combines the WhatsApp Business Platform, reliable store data, clear customer verification, approved message templates, and an agent handoff.
This guide explains how to choose an implementation, design useful support flows, meet messaging rules, estimate costs, and launch with safeguards. Pricing details are dated to August 18, 2026; Meta has announced a scheduled pricing change for October 1, 2026, so check current rate cards before budgeting.
What a WhatsApp chatbot for e-commerce actually is
“WhatsApp chatbot” is not a single product. It is a support system built around a WhatsApp business account and phone number, automation logic, connections to store or support systems, and a way for agents to take over.
- WhatsApp Business App: A practical option for smaller businesses handling conversations manually. It is not, by itself, the programmable platform used for custom bots and webhooks.
- WhatsApp Business Platform: Meta’s business-messaging infrastructure for automated and agent-assisted communication.
- Cloud API: Meta-hosted API that developers can connect to a bot, help desk, CRM, order system, or custom application. A business can use it directly; a third-party provider is not universally required. See Meta’s Cloud API overview.
- BSP or API provider: A service that can simplify onboarding, messaging infrastructure, templates, and support. Depending on the provider, it may not include a complete agent inbox or chatbot builder.
- Shared-inbox or chatbot platform: A higher-level tool combining some mix of automation, routing, and agent operations.
Before choosing a vendor, decide whether you need only messaging infrastructure, a ready-made bot and inbox, or an integration into an existing help desk.
#1 Best Overall
Choose support work that is safe to automate
Begin with frequent requests that have predictable answers and dependable data behind them. Good starting points include:
- Order status and tracking links.
- Shipping times, delivery areas, store hours, and payment-method FAQs.
- Return and exchange policy explanations and return-label instructions.
- Product availability, sizes, colors, warranty terms, and care instructions.
- Address-change requests before fulfillment, when the order system confirms that a change is still possible.
- Subscription-management instructions, promotion FAQs, and routing to the correct support queue.
- A short satisfaction question after a verified resolution.
Keep a human in control of disputes, suspected fraud, account-access problems, refund exceptions, damaged or missing parcels requiring investigation, safety or regulated-product advice, and complicated or emotionally charged cases. Automation should make agent help faster to reach, not harder.
Give the bot the right kind of knowledge
Separate stable content from live customer data. The bot can answer policy questions from an approved knowledge base, but order status, inventory, refund state, and delivery estimates should come from the relevant commerce, fulfillment, or CRM system at the time of the request. An AI model’s remembered or generated answer is not an order lookup.
Free tools Windows power users keep installed
One-click scans. No signup required.
If the system is unavailable, records conflict, or the bot cannot verify an answer, it should say so and offer an agent or ticket—not guess. Do not give it full payment-card information, passwords, or sensitive documents it does not need to complete the support task.
Choose an operating model
| Option | Best suited to | Main trade-off |
|---|---|---|
| Direct Meta Cloud API | Engineering teams with an existing support stack or capacity to build one | Control over integrations and workflows, but your team owns the inbox, monitoring, retries, security, and operational tooling. |
| Twilio | Developer-led teams, existing Twilio users, and businesses using several messaging channels | A mature API option, with Twilio charges added to applicable Meta messaging fees; agent tooling may require another product or custom work. |
| 360dialog | Teams wanting WhatsApp-focused API infrastructure and freedom to select a separate inbox or automation layer | WhatsApp specialization, but a complete support workflow may require additional integrations and products. |
| WATI | Low-code teams looking for WhatsApp-centric automation and shared-inbox capabilities | Can reduce implementation work; verify current plan limits, charges, and data terms. Exact current plans were not verified here. |
| Respond.io | Support teams needing shared inboxes, routing, and multiple channels | Operational tooling can be useful, but platform subscriptions and messaging charges are separate considerations. Verify current plans and fees. |
| Existing help desk integration | Organizations that need WhatsApp conversations inside established support operations | Keeps work in familiar systems, but integration effort and ongoing maintenance can be substantial. |
For an engineering team that already operates its own support backend, direct Cloud API may avoid a full-service inbox subscription. Twilio is worth considering when its developer ecosystem or other channels matter. A WhatsApp-focused API provider can suit teams pairing infrastructure with their own tools. Low-code or shared-inbox products may speed up a nontechnical rollout. Compare the actual onboarding route, supported integrations, number migration options, data-processing terms, staffing workflows, plan limits, and total fees for your country and volume—not just the headline subscription.
Product references: Twilio WhatsApp, 360dialog, WATI, and Respond.io.
Design the conversation before building it
Map the most common contact reasons in support tickets. Pick five to ten flows with high volume, low ambiguity, dependable backend data, and low financial or regulatory risk. For the first menu, use a small set of choices:
Hi — I can help with:
Track my order
Start a return or exchange
Product questions
Shipping and delivery
Talk to a support specialist
Use supported buttons or lists where appropriate rather than requiring customers to remember exact numeric commands. Meta’s API documentation includes interactive messages, templates, and messaging requests.
Example: order tracking
- Customer selects “Track my order.”
- Ask for the order number and a second verification factor, such as a matching email or phone fragment, or direct the customer through a secure account link.
- Look up the order using the commerce or order-management API.
- If verified and found, return a concise status, latest scan if available, and tracking link.
- If the parcel is delayed or the record is unclear, explain what is known and offer a human handoff.
- If the order cannot be found after one retry, create a ticket rather than looping.
The response should distinguish among states such as payment pending, preparing, fulfilled, in transit, out for delivery, delivered, delayed, returned to sender, cancelled, or refunded. A known order number alone is not enough to justify exposing a customer’s address or entire order history.
Other useful flows
- Return or exchange: Confirm the order and item, check the published policy and eligibility from authoritative systems, explain the next step, and hand off exception requests. Do not decide on a policy exception or issue a refund unless a controlled, authorized workflow permits it.
- Delivery problem or damaged item: Capture only the information needed to open a case, invite a photo if the channel and workflow support it, and create a ticket for investigation. Do not promise a replacement or compensation without authorization.
- Product availability: Query live inventory by SKU, size, or variant. If inventory cannot be checked, say so rather than claiming an item is in stock.
- Product advice: Answer straightforward questions from approved product information. Route nuanced suitability, safety, or high-value purchasing advice to a person.
Reference architecture and implementation
Customer on WhatsApp
↓
WhatsApp Business Platform / Cloud API
↓
Webhook receiver
↓
Message router
├── FAQ / approved knowledge base
├── Order-status service
├── Returns and exchanges workflow
├── Product / inventory lookup
├── CRM or help-desk ticket creation
└── Human-agent escalation
↓
WhatsApp response, template, interactive message, or agent replyThe webhook receiver should validate incoming events, record message IDs and timestamps, prevent duplicate processing, identify the conversation, classify the request, verify authorization before returning order data, call the appropriate system, log the outcome, and escalate if permissions, confidence, or a backend system are insufficient. Subscribe to inbound-message and delivery-status events. Keep an audit trail of message IDs, timestamps, status and error details, bot decisions, and handoff state.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Use queues, bounded retries, timeouts, and idempotency so a repeated webhook or delayed order-system response does not create duplicate actions or messages. A WhatsApp channel is not automatically a help desk: the business still needs ticket ownership, internal notes, SLA tracking, refund authorization, customer history, and reporting.
Cloud API request example
This illustrative request sends a text response from a Cloud API phone number. Replace every placeholder with the current Graph API version, phone-number ID, access token, and E.164-formatted recipient number; protect tokens as secrets.
curl -X POST
"https://graph.facebook.com/<GRAPH_API_VERSION>/<PHONE_NUMBER_ID>/messages"
-H "Authorization: Bearer <ACCESS_TOKEN>"
-H "Content-Type: application/json"
-d '{
"messaging_product": "whatsapp",
"to": "<E.164_PHONE_NUMBER>",
"type": "text",
"text": {"body": "Your order is currently in transit."}
}'Outside an open customer-service window, business-initiated messaging generally requires an approved template. In that case the template name, language, variable count, and parameter positions must match the approved version; arbitrary free-form text is not a substitute. See the Cloud API request and template documentation.
Messaging rules, templates, and timing
Under the current policy model described in Meta’s WhatsApp Business Messaging Policy, a customer message generally opens a 24-hour customer-service window. During that window, the business may reply with free-form messages. Outside it, the business generally needs an approved template. A qualifying customer-initiated conversation from a Facebook or Instagram entry point may open a 72-hour free-entry-point window if the business responds within the required initial period. Check the current policy and account-specific requirements before relying on an exception.
Templates are reviewed and must be used for their approved purpose. Keep transactional messages genuinely transactional; do not disguise a promotion as a Utility template. Suitable template concepts include order confirmation, order shipped, delivery delayed, return received, refund processed, and payment failed. A template may be rejected, paused, or reclassified.
- Customer replies within 24 hours: The service window is generally open for free-form support replies under the policy and pricing regime in effect at the time.
- The customer returns two days later: The prior service window has generally closed; a business-initiated follow-up usually needs an approved template.
- A delivery or return update is needed: Choose an appropriate approved transactional template if required by the current window rules.
- A marketing offer is mixed into support: Treat it as marketing, obtain any required opt-in, and use the appropriate approved template category rather than relabeling it.
Businesses using automation must maintain a clear, direct path to human escalation. Offer an agent option and define what happens outside staffed hours: for example, acknowledge the request, create a ticket, and state when a reply is expected.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Costs: budget for the whole system, not just messages
There is no single universal WhatsApp chatbot price. Meta messaging rates can depend on recipient country, category, rate card date, and volume tier. Providers may add per-message, subscription, seat, or infrastructure charges. The total also includes the inbox or help desk, bot or AI usage, hosting and monitoring, integrations, and the human labor needed for cases the bot cannot resolve.
As of August 18, 2026, Twilio’s US pricing page displays a $0.005 per-message Twilio fee in addition to applicable Meta fees, and shows an example US Utility template Meta fee of $0.0034 per message outside the customer-service window. Those are country- and date-specific examples, not a universal rate; consult Twilio’s live pricing page and current Meta rate cards for your recipients and traffic.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Important scheduled change: A Twilio notice says Meta is scheduled to begin charging per message for Service messages and Utility template messages sent during an open customer-service window on October 1, 2026. The change is future-dated as of August 18, 2026, so do not describe it as already active. Recheck the notice and rate cards before setting a forecast; “support messages are always free” is not a safe long-term budget assumption. See Twilio’s notice on the scheduled change and Respond.io’s WhatsApp pricing explanation.
360dialog says its WhatsApp message fees are based on Meta rate cards and separately documents its plans and payment options. Its documentation notes that marketing sent through the standard /messages endpoint may incur a 7% marketing-rate increase relative to the relevant Marketing Messages API route; treat this as provider-specific, not a universal Meta rule. Review 360dialog pricing and its plans and payment information.
Model costs using expected message volumes by category and recipient country, plus provider charges, seats, AI usage, integration maintenance, and agent time. Twilio notes that failed-message processing fees may apply in certain circumstances; include provider-specific failure charges where relevant. Compare cost per correctly resolved case, not simply cost per bot reply.
Privacy, security, and customer trust
Meta’s policy places responsibility on the business to provide required notices, obtain necessary permissions and consents, publish a privacy policy, and comply with applicable law. Exact obligations vary by jurisdiction, sector, and data type; this is operational guidance, not legal advice.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstall- Explain what WhatsApp support data is used for and how customers can opt out of nonessential messages.
- Minimize information collected and displayed. Redact addresses and payment details; never ask users to send passwords or full payment-card data.
- Verify identity before exposing order details or making account changes. Use a secure link or authenticated session for sensitive actions.
- Restrict staff access by role, protect API tokens, validate webhook requests, and use encryption in transit and at rest.
- Set retention and deletion rules for chat logs, attachments, and support records; review vendor data-processing terms and subprocessors.
- Keep human authorization for refunds, cancellations, compensation, identity-sensitive requests, and other consequential decisions.
Test and launch in stages
Before launch
- Confirm the Meta business portfolio, WhatsApp Business Account, phone number, permissions, app setup, and webhook endpoint. Business verification may be required depending on the setup.
- Choose a new number, migration route, or supported coexistence arrangement early. Do not assume every existing Business App number can be reused with every provider; availability depends on the onboarding route, account, market, and provider.
- Set up token management, approved templates, privacy and consent language, order-system access, monitoring, and an agent queue with named ownership.
- Test an inbound message, duplicate webhook, invalid order number, unauthorized lookup, timeout, delayed order API, delivery failure, rejected template, and agent takeover.
- Test a conversation outside the 24-hour window, opt-out, topic changes, time zones and business hours, and multiple languages.
- Test voice notes, images, emojis, misspellings, mixed-language messages, and unsupported files. Acknowledge unsupported input, ask one clarifying question, or route to a person.
Soft launch and improve
Release one low-risk flow—usually order tracking—to a limited audience or support queue. Review the transcript and backend result for every early failure. Add returns or product FAQs only after the first flow reliably verifies identity, returns current data, and hands off exceptions. Maintain a fallback for bot, provider, and store-system outages.
Measure resolution, not bot activity
A high count of bot replies does not prove that customers got help. Track:
- Correct-resolution and repeat-contact rates.
- Bot containment rate, alongside human escalation rate and reasons.
- First-response time and time to resolution.
- Customer satisfaction after confirmed resolution.
- Cost per correctly resolved case.
- Template delivery and read rates, opt-outs, and complaint or block signals.
- Webhook failures, duplicate events, integration timeouts, and unresolved intents.
Review unresolved questions and handoff transcripts regularly. If customers repeatedly abandon a flow, receive stale data, or ask for an agent, simplify or remove the automation instead of optimizing only for containment.
Conclusion
Start with a single high-volume, low-risk task—typically order tracking—then expand only when data access, verification, templates, and human takeover work reliably. The right platform is the one that fits your team’s engineering capacity and support operations, with all Meta, vendor, integration, AI, and labor costs included. A useful WhatsApp chatbot resolves the predictable cases and makes the difficult ones easier for a real person to solve.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
