Industries / E-commerce

Order questions, product photos, and payment confirmations - all in one thread.

A customer asking "is this in stock?" or "where's my order?" doesn't want a support ticket number - they want a fast answer in the same chat they already have open. E-commerce on WhatsApp works when that thread has a real catalog and pipeline behind it.

1 catalog

Products attached directly to a conversation

Auto deal value

As items are added to an order

Shared inbox

So no order question waits on one person

THE REALITY ON THE GROUND

Order support scattered across DMs doesn't scale past a handful of sales

Answering "is this still available in blue?" from a personal phone works fine at ten orders a week. At a hundred, the same phone is buried in unanswered questions, stock mix-ups, and no reliable way to see which orders are actually confirmed versus still being negotiated.

Payment confirmation is its own headache without structure - a screenshot sent in one thread with no tracked status means someone has to manually cross-reference every claimed payment by hand.

HOW INBOX HELPS

A catalog and pipeline behind every conversation

Attach products to an order

Add catalog items to a conversation-turned-lead so the order total calculates itself, no manual math.

Track order status as a pipeline

Move an order from Enquiry through Confirmed to Shipped, visible to the whole team at a glance.

Tag by product or issue

Tag conversations by product line or issue type (sizing, stock, delivery) to spot patterns over time.

Shared inbox for shared load

Any teammate can answer any customer, so order questions don't all funnel through one person.

How this actually plays out

1
A customer asks about a product

The conversation is converted to a lead, with the relevant catalog item attached.

2
They confirm and pay

The lead moves to Confirmed, its value already calculated from the attached product.

3
Fulfillment is tracked

The order moves through Shipped, visible to the whole team without asking around.

4
Follow-up if needed

A task is set if a payment or shipment needs checking on, so nothing silently stalls.

What's built in

Product catalog with pricing, attachable directly to a conversation-turned-lead

Pipeline stages for order status - enquiry through fulfilled

Tags for product, size, or issue type, feeding into segments for targeted follow-ups

Shared inbox so multiple teammates can handle order volume without a bottleneck

Follow-up tasks for pending payments or delayed shipments

Automations to tag or route a conversation the moment a keyword like "refund" or "where's my order" appears

A customer asks if a specific item is available in a certain color. The rep attaches the product to a new lead, confirms availability, and the customer sends payment confirmation minutes later - the lead moves to Confirmed with its value already calculated from the catalog price. A follow-up task is set for the shipping date, so if it slips, someone notices before the customer has to ask.

Common questions

Can more than one team member handle order conversations?

Yes - that's the core benefit of a shared inbox over a single personal number. Any available teammate can pick up and respond.

Does Inbox track inventory levels?

No - the product catalog tracks pricing and what's attached to a lead, not live stock counts. It's not a full inventory management system.

Can we tag orders by issue type for reporting?

Yes - tag conversations by issue (delayed shipping, sizing questions, refund requests) and build segments or reports from those tags over time.

Don't see your exact setup?

The same shared inbox, pipeline, and automation flex to fit most WhatsApp-driven sales or support workflow.