Problem
Customers leave the order experience to ask what happens next.
Order updates that turn replies into action
Send fulfillment events to WhatsApp, answer safe order questions and route restricted requests without confusing message state with commerce state.
Outcome pattern for commerce and operations teams with an existing order system.Interaction
The alert contains the order status and permitted next actions.
Outcome
Routine questions resolve quickly while sensitive changes stay controlled.
Operational problem
A status page may contain the answer, but customers still ask about ETA, carrier, address changes and cancellations. Generic automation either repeats the link or risks promising an action it cannot authorize.
Event source
Send only after the commerce system confirms an immutable transition such as dispatched or delayed. Persist its source event ID so provider retries cannot create duplicate customer messages.
WhatsApp interaction
Keep the message short and attach a deliberately small order context: public reference, status, ETA, carrier and flags describing which actions remain possible. Exclude payment data, internal risk scores and unrelated history.
Reply behavior
Answer facts from context. Route refunds, cancellations, identity changes and post-dispatch address changes to authenticated workflows or a human. WhatsApp identity alone should not authorize a sensitive commerce action.
Measurable outcome
Measure repetitive support contacts avoided, response time, successful self-service actions, escalation rate and delivery reliability. Keep these separate from parcel fulfillment metrics.
Frequently asked questions
Does delivered mean the parcel arrived?
No. It means the WhatsApp message reached the account.
Can a customer cancel by replying?
A reply can start the request, but cancellation should follow your authenticated commerce policy.
Where does order data live?
Your commerce system remains the source of truth; attach only the context required for the conversation.
CONTROL THE OUTCOME
Start with one event and one reply path.
Prove the operational loop before increasing traffic or automation.
Gain Access