WhatsApp for Ecommerce — Orders, Carts and Customer Chat

Support and sales share a founder’s phone. Order status is copy-pasted from the admin. Cart recovery is an unofficial blaster waiting to get the number banned.

Wapikon is the WhatsApp and inbox layer. Your store and payment gateway stay where they are.

Utility templates fit shipping and order notices when the content matches Meta’s category. Session chat handles size, stock, and complaints. Catalogues can continue in WhatsApp where Meta commerce features allow.

Connect a WABA, map store events to messages when Shopify, WooCommerce, or Salla is connected, and let agents pick up exceptions in the shared inbox. Abandoned-cart nudges need opt-in and an approved template.

Website chat, Click-to-WhatsApp ads, and checkout widgets can start a conversation. Store sign-ups should still collect WhatsApp opt-in if you plan marketing templates later.

Flows can ask product interest or order ID before routing to sales vs support. Do not use a bot to promise stock you have not checked.

Connected stores can drive order and cart events into WhatsApp. Email campaigns in the same workspace (SMTP or ESP) cover receipts and long attachments.

Returns, delays, and “wrong size” belong in the shared inbox with assignment — not a packing-bench personal chat. Internal notes stay off the customer’s screen.

Opted-in buyers can receive marketing templates for a drop. Keep frequency sane. Utility templates are for status, not a disguised sale.

Several agents, one number, contact history beside the order conversation. HubSpot or Zoho if you already run a larger CRM.

The AI agent can answer shipping policy and size-guide knowledge you upload. Refunds, chargebacks, and medical claims about products should go to a human.