For ecommerce brands, WhatsApp becomes a merchandising-aligned front door: shoppers ask about linen fits, preorder copy, and influencer sampling without waiting on hold. The agent repeats size-chart rows and return steps exactly as your CX wiki states, tags wholesale stockist pings separately from DTC order edits, and logs exchange photos plus order IDs for humans who can see fulfillment tools.Warehouse scans, refund buttons, and influencer commission tables stay off-limits in automated replies. When someone demands an instant label or a secret discount, the thread hands off with the notes your coordinators need instead of fabricating carrier events or SKU availability.
Shoppers message about a delayed tote bag, a size swap before a wedding, or a TikTok creator asking for wholesale terms while your CX team is buried in email. The agent opens the right path, quotes your published return window and measurement guide, notes order numbers for staff lookup, and routes wholesale requests to the B2B inbox with the chat attached.
The managed agent covers the shopper conversations that repeat every launch: order questions, return intake, sizing FAQ, wholesale handoffs, and cart nudges your team still approves.
When someone asks where a package is, the agent collects order number, email on the order, and SKU context you choose, then explains that live tracking stays with your support tools.
It never fabricates carrier scans or delivery dates. Staff continue in the same WhatsApp thread with notes already structured.
Shoppers describe wrong size or damaged items. The agent walks through your published return steps, reason labels, and photo prompts without promising same-day refunds.
Exchange requests capture desired variant from your published availability language. CX confirms inventory and refund timing after review.
Retail shoppers, stockists, and influencer partnership asks hit the same public number. Path labels route wholesale margin questions and line-sheet requests to your B2B or PR queue.
Consumer cart help stays with DTC support. The agent does not negotiate MOQ or commission rates in chat.
When a shopper abandons after asking about shipping cutoffs, the agent can send approved reminder copy referencing items they mentioned, without auto-issuing discount codes.
Finance-controlled offers stay in templates your leadership signs off on. Quiet browsers get a helpful nudge, not a fake price drop.
Brand teams field Instagram DMs, email tickets, SMS, and WhatsApp about the same drop. Merch updates size charts while support still pastes the old return policy into every thread.
Shoppers ask for tracking while agents hunt OMS tabs
A customer texts on WhatsApp while support is in Shopify and the WMS. The message waits. They buy replacement sizing from a competitor who answered first.
Size and fit answers vary by agent
Someone asks if a medium runs small. One rep guesses; another links the chart. Inconsistent guidance drives returns that your ops team could have prevented with one published chart answer.
Wholesale DMs land in consumer queues
A boutique owner asks for line sheets on the same line consumers use for order edits. Retail support treats it like a missing package ticket and the wholesale lead goes cold.
Backorder language is improvised
Preorders and delayed SKUs need the exact wording legal approved. Agents paraphrase ship windows and create expectation gaps that show up as chargebacks later.
A WhatsApp chatbot keeps first touch on-brand: published sizing FAQ, structured return intake, wholesale routing, and cart nudges with offers you control. Fulfillment truth and refund decisions stay with people who can see systems of record.
See If It Fits Your TeamWe mirror your help center: return rules, size charts, backorder blurbs, wholesale labels, and the fields support needs before they open an order.
Send help article links, size chart text, return reason labels, wholesale qualification questions, backorder paragraphs, and cart recovery copy legal approved.
Sample threads cover tracking asks, exchange intake, creator outreach, and cart follow-ups. You approve tone before the number goes live.
Conversations collect order context, route paths, and policy answers from your text. Support and wholesale teams pick up threads with structured notes.
When you revise return windows, add a size guide for a new silhouette, or refresh backorder banners, the Connexa team updates the agent. You are not rebuilding conversation trees after every drop.
Peak drops and collab launches still follow the same limits: no invented tracking, no refund promises, no unpublished discounts whispered in chat.
Illustrative exchange showing size chart FAQ, exchange intake, and a clear handoff when the shopper asks for an instant refund approval.
Example conversation
Ordered the linen dress in medium, fits tight in shoulders. Can I swap for large before Saturday?
I can start an exchange intake. Our published size chart notes shoulder measurement for that style. I cannot confirm warehouse stock or same-week delivery in chat. Do you still have tags attached and is this your first exchange on the order?
Tags on. Also where is my other order 88421? Says processing for days.
For order 88421 I can collect the email on the order for support lookup. I do not see live fulfillment status here. For the exchange I can record desired size large and reason fit per your return page. A CX specialist will confirm timing and send label steps if eligible.
Fine. Any discount if I keep both?
I cannot create discount codes in chat. If your team has a published offer for multi-item orders I can share that wording. Exchange notes are queued for CX with size large and order details attached.
Example only. Your live agent uses brand copy you approve and never marks returns complete or quotes unpublished promo codes.
From launch day sizing spikes to wholesale pings, these flows use your published language and handoff rules.
The shopper shares order ID and email. The agent explains that tracking updates come from support after they check fulfillment systems you use.
It never states a delivery date pulled from imagination. The thread records what was asked so the first human reply is not a blank how can I help.
Reason codes, photo requests, and tag-on-item questions follow your policy page. International return caveats can be quoted verbatim when you supply them.
Refund completion and label issuance stay human steps after eligibility review.
Measurement questions map to chart rows you maintain for each SKU family. The agent does not guess slim versus relaxed fit beyond published notes.
When a style is between sizes, it suggests the chart guidance and offers exchange intake if the shopper already ordered.
Only approved delay language appears when shoppers ask about waitlisted SKUs. No invented ship weeks.
If fulfillment updates a batch date, operations sends new copy and Connexa refreshes the agent.
Creator and stockist keywords trigger B2B or partnerships labels. MOQ, pricing tiers, and line sheets are not negotiated in the bot.
Wholesale gets contact fields you define; DTC shoppers stay on consumer flows.
Approved nudges reference cart context the shopper already mentioned, such as shipping cutoff FAQs.
No silent price slashes unless finance published a code for that template.
Care instructions, fabric content, and collab story bullets can be shared from merchandising docs you upload.
Safety or compliance claims beyond your text escalate immediately.
Collects arrival date, packaging photos requested in your policy, and order reference for replacement review.
Does not promise same-day reship; passes urgent flag if you define thresholds.
If someone asked sizing then went silent, a short follow-up references the style discussed using tone you approve.
No pressure language; helpful check-ins only.
Strong fit for label-led shops with recurring post-purchase volume and published help content worth automating first touch.
Your support queue mixes order edits, sizing, and wholesale DMs
Path routing keeps wholesale margin talks out of consumer refund threads.
You already maintain size charts and return articles
The agent quotes that text consistently instead of agents improvising from memory.
Cart recovery depends on timely nudges but finance controls codes
Templates carry approved offers; the bot does not mint new ones.
International shoppers prefer WhatsApp for quick questions
Threads stay async-friendly across time zones without forcing portal logins first.
You want Connexa to maintain wording after each collection drop
Merch sends updated blurbs; we patch the agent without your team learning a builder UI.
You process only a few shopper messages per week
Very low volume may not justify a managed agent; personal replies might stay simpler.
Every ticket must open inside your helpdesk only
This design centers WhatsApp first with handoff notes; if you forbid any bot collection, direct desk workflows may fit better.
You need full OMS automation inside chat
Connexa focuses on intake and published FAQ, not replacing warehouse systems or auto-refunding from chat.
Post-purchase questions happen on the phone people already use for friend chats. Meeting them there reduces friction before they escalate to chargebacks or public reviews.
Shoppers check order questions between meetings without sitting on hold. Threads reopen when your CX shift starts.
Photos of fit issues or damage stay beside order numbers support needs, instead of scattered email attachments.
Drop day spikes hit messaging before phone lines scale. The agent absorbs sizing and policy repeats while humans handle edge cases.
Boutique buyers expect quick professional replies. Structured intake looks intentional even before a rep joins.
Clear language that refunds and tracking need staff review builds trust compared to bots that fake certainties.
Results mix generic storefront bots with heavy ticket portals. This page targets brand-led DTC and wholesale intake on WhatsApp.
Marketplace seller bots focus on marketplace SLAs. Brand pages focus on your own catalog, size charts, returns, and wholesale paths you publish.
Connexa aligns to your help center, not a generic cart abstraction.
Searchers want consistent fit guidance. The agent repeats chart rows you maintain per collection.
Staff handle nuanced fit consults after intake notes land.
Many bots over-promise refunds in chat. Here, eligibility language stays request-only until CX reviews.
That protects finance and reduces disputes when warehouse disagrees.
Creators and stockists often use the public WhatsApp. Labels separate B2B from DTC without a second line purchase on day one.
Partnership desk sees qualified notes, not confused retail tickets.
Leaders compare routing, Meta pass-through costs, and whether chat will invent tracking or discount codes.
Marketing wants speed; support fears stale scripts. Connexa updates copy when you email policy changes.
Your team keeps packing orders while conversation language stays current.
Ops leaders worry about bots inventing ETAs. The agent defers to staff with collected order context.
Boundaries are tested on sample threads you approve pre-launch.
Growth wants nudges; finance controls margin. Templates carry only approved offers.
No silent percentage markdowns invented mid-chat.
Finance asks how WhatsApp fees stack during BFCM. Connexa explains service reply allowances and billed utility templates.
Planning message volume is separate from quoting shoppers in chat.
Message costs include platform fees and Meta charges per delivered message by category and country. Understanding Meta rules helps operators plan volume without confusing those fees with lane rate promises in chat.
Since Oct 1 2026, service replies are free only for the first 1,000 per business phone number per month, then charged. That free allowance applies per business phone number each month. After the first 1,000 service replies in a month, additional service replies are charged under Meta pricing for your category and country.
Connexa pricing conversations can include how your expected inquiry volume relates to Meta message categories. Contact us for pricing tailored to your company.
Utility templates inside an open customer service window are also charged. Operators should not assume that every message inside an open window is free. Utility in-window traffic still follows Meta category pricing. Marketing and authentication categories follow their own rate cards by country.
Meta fees do not change brand boundaries. Tracking events, refund approvals, and unpublished promo codes are still not invented in chat. Staff confirm outcomes after reviewing intake.
Default scope is conversation and handoff. Integrations are scoped during onboarding if needed; the agent does not fabricate order status without a connection you approve.
You send revised chart text or links; Connexa updates answers and re-tests a sizing sample thread.
Media stays in the WhatsApp thread for CX review. The agent does not auto-approve replacements.
Yes with path labels routing to different queues or emails your operations define.
Notify Connexa; we disable or swap templates until you re-enable.
Only templates you approve and that comply with your WhatsApp opt-in rules.
Handoff notes can reference ticket IDs if your workflow includes them; Connexa focuses on the WhatsApp layer.
Configured per markets you specify with localized copy you provide.
After-hours messages collect context and set expectations using hours text you publish.
Talk to us about order volume, return rules, size chart assets, wholesale routing, and cart nudges your team wants on WhatsApp without inventing tracking or discounts.
Start Conversation on WhatsAppOrder ID or email, SKU nicknames, and whether they need a delivery exception note. Support owns carrier truth. Never invent scan events or ETA stamps the OMS did not emit.
Gather order ID, line item, fit-or-damage reason codes from your returns matrix, plus photos when the brand allows. CX still issues RMAs and refunds; chat never closes an exchange alone.
Quote chart cells and fabric callouts merchandising uploaded. Do not invent shopper body measurements or guarantee post-purchase fit.
Wholesale packets ask company, assortment interest, and bulk versus sample intent. Creator packets ask handle and seeding interest so partnerships is not buried under retail tracking tickets.
Only merchandising ship-window blurbs already on the PDP. If inventory truth is unknown, say a coordinator will confirm instead of inventing restock dates.
Remind shoppers of styles they discussed and point at PDP copy. Promo strings appear only when marketing loads approved code text; never invent discount math.
Collect handle, product interest, and sample ship-to when your program asks. PR or influencer managers approve comps; chat does not green-light free product.
Treat product-drop Fridays and January return piles as different traffic shapes. Connexa quotes the brand line from features and expected WISMO volume. Network fees follow Meta rate cards by category and destination country. Beginning Oct 1 2026 a business phone number keeps 1,000 service replies free each month; replies after that allotment invoice, and utility templates that fire while a shopper window is open invoice as well.
Swap chart excerpts and rehearse fit-plus-return samples on staging before the public number speaks the new rows.
Brand intake stresses WISMO packets without fake scans, chart education, wholesale versus creator routing, preorder blurbs, and drop-week nudges. Broad storefront pages stay cart-and-catalog generalists.