Salesforce Decode
Salesforcedecode
Back to questions
Headless 360Advancedwhatsappcommerce-apinotificationsevents

Send WhatsApp order status updates via Commerce API event pipeline

Real World Scenario

Customers opt into WhatsApp shipping updates at checkout but messages arrive hours late or with wrong tracking numbers after order export delays.

Expected Answer

• Subscribe to Commerce order and shipment status events via webhooks or Order Management events • Map order lifecycle states to approved WhatsApp template messages per locale • Include tracking lookup Agent Action validating carrier API before send • Queue messages respecting WhatsApp template and session window policies • Idempotent send keyed on order ID plus status transition preventing duplicate texts • Handle partial shipments with multi-message sequence coordinated in orchestration layer • Monitor delivery failures, template rejections, and opt-out keyword processing

Follow-Up Questions & Answers

Click to expand — each follow-up includes a direct, interview-ready answer

Main difference: use case and scale. Subscribe to Commerce order and shipment status events via webhooks or Order Management events. Map order lifecycle states to approved WhatsApp template messages per locale. Pick based on your integration pattern and team capability. Transactional WhatsApp is event-driven architecture—checkout opt-in means nothing without reliable order event pipeline and template governance. Optimize for scale and operational observability.

Architect Perspective

Transactional WhatsApp is event-driven architecture—checkout opt-in means nothing without reliable order event pipeline and template governance.