Connect WhatsApp and Email and commerce journeys
Reuse Send Flows, shared subscriber consent and original commerce documents.
How to do it
- In Send Flows, add Send WhatsApp with an approved template, number and audience phone field. Add Wait for WhatsApp event with Delivered, Read, Replied or an observed interactive button reply; connect both Yes and No branches.
- Use WhatsApp received/replied/delivered/read/button event entries with a Contact audience. The existing re-entry, schedule, active-hours, entry/exit, goal and simulation controls still apply.
- Combine Email and WhatsApp activities with existing field updates, tasks, notifications, webhook actions and conditions. WhatsApp conversation actions can assign an eligible agent, escalate or invoke the configured SupaGent agent.
- In WhatsApp Studio → Commerce, enable future-source notification rules with approved templates and bindings for Contact.Name, Order.Number, Order.Status, Order.Total, Order.Currency, Invoice.Number and Customer.SpaceLink. Secure customer-space links require the customer portal or the original published storefront.
- Messages reuse the original Order, verified commerce payment and Finance invoice. A source/rule key prevents duplicate notifications. Known-contact abandoned checkouts can use a consented promotional recovery template; anonymous visitors are not messaged.
Check your result
Simulation creates no send, Order, invoice, coupon or consent change. Live delivery requires the configured external providers and each channel’s current consent.
Good to know
Meta does not report ordinary URL-button clicks. Recorded interactive replies are measurable. Product and shopping messages require a linked Meta catalog and supported interactive payloads. Shipping and delivery rules consume order.shipped and order.delivered from your configured Event Hub source; pass the original order record ID and reviewed carrier, tracking and trackingUrl data. Carrier ingestion, direct Meta catalog synchronization and provider-specific shopping experiences require their corresponding integrations.
Still need help?
Tell us your BU code and the step where you got stuck. Do not include passwords, BU PINs, tokens or recovery codes.
Contact SupaChrome support