The short answer on WhatsApp customer service for ecommerce is that it belongs on your channel list if a meaningful share of your customers already message businesses on WhatsApp, and if you can staff a first response inside a few minutes. A Salesforce survey of 14,300 consumers across 27 countries put WhatsApp as the preferred messaging channel for 58% of respondents globally, and 84% of under-35s. Adding it well means picking a route to the Business Platform, wiring it into your inbox, planning around the 24-hour session window, and using AI for the routine volume so humans handle the rest.
Why WhatsApp is on the shortlist in 2026
WhatsApp is a scale channel now, not a novelty. Over 3 billion monthly active users, per Infobip's 2026 statistics roundup, and eDesk reports more than 200 million businesses on WhatsApp Business with 175 million people messaging a business account daily. For ecommerce specifically, eDesk's 2026 review puts the customer preference at "45% of global eCommerce shoppers prefer WhatsApp support where it is available," and notes that 58% of support inquiries now originate from mobile devices. If your buyer opens WhatsApp before opening your website, that is where the ticket wants to be.
The channel also converts. eDesk reports "WhatsApp business conversations result in completed purchases for around 66% of consumers" and cites a "94% lift in conversion rates for businesses using WhatsApp." Take single vendor stats with a pinch of salt, but the direction is clear: WhatsApp is a support channel that doubles as a sales one.
The two ways in: Business App vs Business Platform (API)
Two products, one brand. The Business App is a phone-based tool for a small merchant answering messages themselves. The Business Platform, sometimes called the WhatsApp Business API, is the route real ecommerce teams take: it lets you route messages into a shared inbox, run automation, connect the shop, and use official templates.
If you are past a handful of tickets a day, use the Platform. The App does not support multi-agent inboxes or automation.
The 24-hour customer service window, in plain English
Every WhatsApp conversation runs on a 24-hour session window. SleekFlow's 2026 pricing summary spells it out: "When a customer messages your business first, it opens a 24-hour window, during which you can send any free-form message for free." That is your service window. Reply inside it and you can send anything conversational.
Outside that window, you can only start a new conversation with a pre-approved template message, and template messages are charged.
Two implications for operations:
- Reply within the session window whenever you can. A reply at hour 25 costs more and is less flexible.
- Draft templates for the outbound cases you know you will hit: order shipped, refund issued, back-in-stock, review request. Get them approved before you need them.
Pricing is changing on October 1, 2026
Plan for a cost model change. From October 1, 2026, Meta's WhatsApp Business Platform pricing shifts. Per MMDSmart's 2026 briefing: "Service replies sent by a human agent or third-party AI agent inside the 24-hour customer service window will become part of the cost exposure, and utility messages sent in response to users inside the same window will also become chargeable. Additionally, Meta will introduce a free monthly tier of 1,000 service messages per business phone number."
For a small store, the free monthly tier will absorb most of the volume. For a growing store, model it into the cost per resolution now, and revisit our per-resolution pricing trap post if your provider charges per resolution on top.
Response-time expectations are tightening
The Zendesk 2026 Customer Experience Trends Report, based on 8,900 consumers in 20 countries, reads: "The average consumer response time to business-initiated WhatsApp messages has dropped to 38 seconds, down from 45 seconds, while businesses using AI-assisted WhatsApp response tools achieved a median first-response time of just 11 seconds, producing a 34% improvement in customer satisfaction scores."
Two things to do with that number. First, set your first-response target on WhatsApp at two minutes, not two hours. A store that stretches WhatsApp response times to a working-hours SLA will lose the customer to a competitor who does not. Second, use AI for the first reply. A human writing every WhatsApp reply from scratch cannot sustain a sub-minute response at any real volume; an AI reply grounded in your help centre and order system can. For the wider first-response framing see our first response time benchmarks post.
What to automate first, and what to keep human
Rank inbound WhatsApp questions by volume, not by feeling. The top of the list for ecommerce is almost always the same three buckets.
Where is my order. By far the biggest. Wire the AI into your order and tracking data and answer WISMO tickets from live status, per our note on WISMO automation for Shopify. Do not send a generic reply that says "check your email".
Returns and refunds. Policy lookup, eligibility check, label generation handoff. The AI explains the policy and starts the return. See automating returns questions for the wider setup.
Pre-sales product questions. Sizing, compatibility, stock. This is where WhatsApp doubles as a sales channel. Framework in pre-sales product questions with AI.
Keep four categories human by default: complaints with an angry tone, disputes over a specific charge, anything involving fraud or account takeover, and any request that requires a policy exception. See when not to automate a ticket for the full list.
A practical setup, in the order you do it
| Step | Owner | Notes | | --- | --- | --- | | Verify a Business Account and pick a Business Solution Provider or connect directly | Ops | Meta requires a verified business | | Connect the number to your shared inbox | Support lead | Same inbox as email and chat | | Draft and submit the four core templates: shipped, delivered, refund, back-in-stock | Marketing + support | Approval takes 24 to 48 hours | | Point the AI agent at your help centre, orders, and returns policy | AI lead | The integrations layer does the wiring | | Set the first-response target at two minutes and alert on breach | Support lead | Use the widget and inbox targets | | Add WhatsApp opt-in on checkout and the order confirmation page | Marketing | Consent needed for outbound | | Rollout: soft launch to a percentage of traffic, review week 1 logs, expand | Support lead + AI lead | Watch handoff and reopen rates |
Two to three weeks end to end for most stores.
What good looks like after 90 days
A store running WhatsApp well after three months shows a pattern: 30 to 50% of tickets on WhatsApp instead of email, median first response inside a minute, an AI handling roughly two thirds of the volume unaided, a handoff to human on the rest, and CSAT that matches or beats the email channel. Cost per resolution comes down because response speed drops re-contact rate. If you are not seeing this pattern, look at the audit playbook and the dashboard tiles before adding channels.
How Keloa approaches WhatsApp
Keloa treats WhatsApp as one channel among the rest, not a separate stack. The unified inbox shows WhatsApp threads alongside email and chat, and the AI agents answer from the same connected sources whether the ticket arrived over email or WhatsApp. For Shopify stores the Shopify Brands solution wires order and tracking data in on day one, so the AI answers WISMO from live status rather than a template. Session-window awareness and templated outbound are built in; you draft the template once and the inbox routes based on window state.
For pricing, Keloa uses transparent per-reply pricing. See our note on the per-resolution pricing trap for why we do not charge per resolution.
Frequently asked questions
Do I need the WhatsApp Business App or the Business Platform? The Business App is fine for a solo founder answering a handful of messages. Any team, any automation, any multi-agent inbox needs the Business Platform (the WhatsApp Business API), which you access through a Business Solution Provider or directly.
What is the WhatsApp 24-hour customer service window? When a customer messages you, a 24-hour window opens during which you can reply freely. Outside that window you must use a pre-approved template message. Reply inside the window whenever possible; drafting templates ahead of time covers the rest.
How much does WhatsApp Business messaging cost in 2026? Costs are shifting on October 1, 2026: service and utility replies inside the session window will start counting against a paid volume once you exceed the new 1,000-message free monthly tier per phone number. Model this into your cost per resolution.
What response time do WhatsApp customers expect? Sub-minute is the working target. Zendesk's 2026 report puts the average consumer response time to business-initiated messages at 38 seconds, and AI-assisted teams achieve a median first response of 11 seconds. Set the alert at two minutes.
Can AI safely handle WhatsApp tickets end to end? Yes for routine WISMO, returns, and product questions when the AI is grounded in live order and policy data. No for complaints, disputes, fraud, and account changes. Route those to a human by default and log handoffs so you can tune the split. Framework in when not to automate.
Does WhatsApp support work for B2B, or only consumer brands? Both. B2B teams see slower response-time expectations, so the sub-minute pressure eases, but the same session-window and template rules apply. The bigger question is whether your buyers actually message on WhatsApp; check the mobile share of your existing support inbox for a first signal.
Want WhatsApp wired into a shared inbox with AI handling the routine volume? Book a demo and we will walk through the setup, the templates, and the response-time targets against your own catalogue.