E-commerce
June 26, 2026
WhatsApp and on-site chat both allow you to speak with your customers. However, they do not serve the same moment of the journey. On-site chat captures hesitation during the visit. WhatsApp often extends the relationship after the visit, on mobile, in an already familiar channel.
The difficulty comes from the choice: launching WhatsApp because the channel is popular, or installing an on-site widget because it is simple, is not enough. The right trade-off depends on your customer intent, your post-purchase volume, your markets, and your ability to connect Shopify data.
This article #18 covers an angle still missing from the silo: how to choose between WhatsApp chatbot, on-site chat, or a hybrid model, with practical cases, KPIs, and routing rules that can be used directly.
Summary
What is the difference between WhatsApp and on-site chat?
The onsite chat lives in the store. It often knows the page being viewed, the product, and sometimes the cart. WhatsApp lives in the customer's messaging app: more personal, more mobile, more continuous.
Onsite Chat
It answers immediate doubts: size, delivery, comparison, return, compatibility, promo code. The customer is still only one click away from adding to the cart.
It is better suited for continuity: order tracking, returns, invoices, post-delivery exchanges, messages from Instagram, QR codes, or transactional emails.
When should you prioritize onsite chat?
Pre-purchase: product questions, comparison, variant
Conversion: hesitation on product page or cart
Page context: the bot already knows which product is being viewed
Quick launch: fewer API constraints and opt-in
Desktop or mobile web: the customer is still in the store
Shopify Inbox illustrates this role well: free chat in the Shopify admin, cart and profile information, suggested responses and instant answers with Shopify Magic (Shopify Inbox). For a store that wants to respond during the visit first, onsite is often the first channel to test.
When should you choose WhatsApp as a priority?
Mobile-first: customers used to interacting on WhatsApp
Post-purchase: WISMO, return, invoice, exchange
Continuity: conversation that resumes after the visit
Local markets: countries where WhatsApp is already the support default
Campaigns: Instagram, QR code, email, SMS, packaging
In 2026, Meta presented Meta Business Agent to respond to customers on WhatsApp, Messenger and Instagram, with possible connection to systems like Shopify and Zendesk (Meta Business Agent). WhatsApp is thus becoming a key channel, but it must remain consensual, useful, and well-integrated.
Which use cases should be placed on each channel?
The easiest way to make a choice is to organize your inquiries by stage of the customer journey.
Product discovery: onsite chat
Comparison before purchase: onsite chat
Delivery question before payment: onsite chat
Order tracking after purchase: WhatsApp
Return or exchange from mobile: WhatsApp
Sensitive dispute: human, regardless of the channel
Example: "which size should I choose?" should stay on the website. "where is my package?" can easily live on WhatsApp, especially if the link is in the shipping email.
Sorting rule
If the question influences an immediate purchase, keep it onsite. If it concerns an order already placed, WhatsApp often becomes more natural.
What WhatsApp constraints should be anticipated?
WhatsApp is not just a simple widget. The channel requires more governance.
Opt-in: the customer must accept messages depending on the context
Templates: proactive messages are often pre-approved
Window: free response is limited after the customer's initiative
Number: an official number can be dedicated to the platform
Cost: API, conversations, helpdesk, and integration
The WhatsApp Cloud API documentation highlights the logic of the customer service window and the use of template messages outside of this window (WhatsApp Cloud API). Before selling WhatsApp internally, therefore, check the rules as much as the potential.
Point of vigilance
Do not mix support responses with sales follow-ups. A customer asking for a return is not expecting a promotion. On WhatsApp, the line between useful and intrusive is very quickly seen.
What are the limitations of onsite chat that you should know about?
On-site chat is easier to launch, but it is not magic.
Session: once the customer leaves, they don't always return to read the reply
Visibility: widgets can be too discreet or too intrusive
Coverage: useful on site, weak after delivery
Routing: risk of sending everything to the same bot
History: limited continuity without email, account, or helpdesk
The right approach is to place the chat where it sells or reassures: complex PDPs, cart, checkout, returns page, contact page. A widget on every page without a specific scenario quickly becomes decorative.
How to build an omnichannel model?
The best system does not oppose channels. It connects them.
Onsite chat for pre-purchase questions
WhatsApp for post-purchase and mobile follow-up
Same knowledge base to avoid contradictions
Same customer history in the helpdesk if possible
Human handoff with summary, order, and original channel
Gorgias presents WhatsApp as an integrated helpdesk channel, with conversations transformed into tickets and Shopify profiles linked by phone number when details match (Gorgias WhatsApp 101). It is this type of unification that makes omnichannel useful.
30-day test
Activate onsite on 5 high-hesitation pages and WhatsApp only in the shipping email. You will quickly know whether the primary need is pre-purchase conversion or post-purchase reassurance.
What messages should be prepared?
Onsite pre-purchase
“Are you hesitating about the size, compatibility, or delivery? I can check before you add to your cart.”
WhatsApp post-purchase
“Hello, I can help you track your order, request a return, or find your invoice.”
Bridge from website to WhatsApp
“Would you prefer to continue on WhatsApp? We will send you the tracking and keep the context of your request.”
Human fallback
“I am forwarding your request to the team along with your order details and our conversation, so you don't have to repeat yourself.”
Which KPIs should be compared?
Onsite chat: widget opening, assisted cart addition, assisted conversion
WhatsApp: response time, WISMO resolution, CSAT, cost per conversation
Omnichannel: avoided tickets, successful handoff, conversations without repetition
Quality: reviewed answers, policy errors, sensitive escalations
Business: cart saved onsite, repurchase or post-purchase satisfaction
Do not compare WhatsApp and onsite with a single KPI. Onsite must above all prove its conversion effect. WhatsApp must above all prove continuity, speed, satisfaction, and support load reduction.
Practical reading
An underused WhatsApp may simply lack a visible entry point. A rarely opened onsite chat may be poorly placed. Before concluding that the channel does not work, test visibility, callout message, and trigger timing.
Which mistakes should be avoided?
WhatsApp too early: no real post-purchase volume
Onsite neglected: pre-purchase questions left unanswered
Two separate bots: conflicting policies and customer repeating themselves
Unsolicited messages: WhatsApp follow-up perceived as intrusive
No routing: support, sales, and disputes mixed together
The rule of thumb: do not choose the trendiest channel, choose the one that fixes your most expensive friction. Abandoned cart on product page? Onsite. Mobile WISMO saturation? WhatsApp.
Re-evaluate this choice every quarter: a secondary channel can become a priority when a market, a campaign, or a post-purchase volume changes.
How does Qstomy fit into this strategy?
Qstomy is particularly relevant for onsite chat connected to Shopify: product advice, objections, pre-purchase FAQ, order status and clean escalation.
DTC fashion scenario
Shopify store, 900 orders/month. Qstomy is launched onsite on size charts, cart and return page. Pilot hypothesis: 1,800 conversations/month, 38% pre-purchase questions, 210 assisted cart additions, 54 size tickets avoided. After 30 days, WhatsApp is added only in the shipping email for parcel tracking.
This model avoids launching two half-ready channels. Qstomy first captures the onsite conversion, then WhatsApp takes over if mobile post-purchase justifies it.
The store thus keeps a simple logic: the site helps to choose and buy, WhatsApp helps to track and resolve. Both channels read the same policies to avoid contradictory answers.
See AI customer support, AI sales assistant, Shopify integration and request a demo.
Which playbooks should be launched this week?
Playbook 1: Channel Audit
Export 30 days of inquiries: website, email, Instagram, WhatsApp, form. Classify by channel, stage of the customer journey, reason, urgency, business value, customer risk, and frequency.
Playbook 2: Onsite First
If you receive many pre-purchase questions, launch onsite chat on 5 high-traffic pages and measure assisted cart additions.
Playbook 3: Targeted WhatsApp
If WhatsApp is already part of your customers' habits, start with order tracking, simple returns, and invoices, not with promotions.
Playbook 4: Bridges Between Channels
Add a WhatsApp link in the shipping email, but keep the onsite chat for product pages and the cart.
Useful Links
Handoff: human chatbot handoff
Post-purchase: automated post-purchase support
Shopify: Is Shopify Inbox enough?
Omnichannel: omnichannel vs multichannel
Enzo
June 26, 2026
