Ver este sitio en español

E-commerce

Checkout takes the payment. It should not be the only place the customer exists.

The store already has a catalog and payment. The pain is everything else: abandonment that only sees an email, WhatsApp “where is my order?” disconnected, returns that start from zero, and campaigns that do not know the last SKU.

D2C Marketplaces + owned channel Retail with e-comm Catalogs with an advisor

What is worth orchestrating around the store

MEXA does not replace Shopify, VTEX, or a custom engine. It orchestrates conversation, recovery, tracking, and post-purchase on the same order and the same person.

Real friction

Where the order drops

The abandoned cart is the symptom. The problem is that the conversation and the order are not the same object.

Abandonment = one email and silence

The email flow does not know if the customer asked about size on WhatsApp or if payment failed at the bank.

“Where is my order?” in a new chat

Support asks for an order number. The customer has it in email. Half an hour is lost on tracking that already existed.

Return as an orphaned ticket

The return label, the refund, and the exchange do not hang off the order. Each channel tells another version.

Product advice off the spec sheet

In consideration categories (tech, beauty, home) the customer needs to talk. The store chat does not carry the SKU.

What to orchestrate first

Use cases around the cart

The most useful: conversational tracking + abandonment with spec-sheet context. There is no need to redesign checkout.

Abandonment with the spec sheet still alive

If the customer talked or configured a product, recovery picks up that spec sheet, not a generic “you forgot something.”

Why it works. Recovers intent with memory. It is more effective than a blind coupon, and cheaper.

Order: a short-lived thread for life

Confirmation, tracking number, issue, and delivery in that order’s conversation. The human joins on the order.

Why it works. Cuts the typical 30–50% of “status” contacts when tracking is within reach on the same channel.

Advice in consideration categories

WhatsApp or web chat with the SKU open. Bundle quotes, demo scheduling, or a store visit if there is retail.

Why it works. Where checkout alone does not close (high ticket), a human with context does.

Repurchase and replenishment

Consumables and restock at N days. The experience remembers the SKU, not “products you might like” from a blind recs engine.

Why it works. It is the cleanest automation case: an order event fires the next one.

Success case (format)

D2C: the order stops being a confirmation email

Illustrative journey. Not a named customer. A MEXA case is published with a name when there is a full journey and evidence that can be told honestly.

A store drops the “order number?” Each order opens a tracking and post-purchase thread.

  1. Problem

    Blind support

    40% of chats (typical in operations like this) were status. The rest, late address changes.

  2. Strategy

    The order is the case

    E-comm events open or update the conversation. The human inherits the order object.

  3. Experience

    The customer does not switch apps to track

    They get the tracking number where they already talk. If there is an issue, they do not start from zero.

  4. Implementation

    Store webhooks + WhatsApp

    Payment, fulfillment, and carrier. MEXA orchestrates; e-comm charges and ships.

  5. Result

    Fewer status tickets, more repurchase with memory

    Support concentrates on exceptions. Marketing stops sending coupons to someone who just received the package.

Frequently asked questions

Is MEXA a store?

No. It is the experience and conversation layer around the one you already have.

Do we have to migrate the catalog?

Not necessarily. It is synced or linked. The rule is that the conversation does not talk about a SKU the store does not have.

Want to see it in your operation?

Book a demo and we’ll walk the customer journey with your industry and current channels.

Request a demo