What does this integration do?
The WhatsApp Business integration works with message templates approved by Meta: order confirmation, shipment tracking and delivery notifications reach the customer over WhatsApp. When the customer replies, the support team can continue with free-form messages inside the 24-hour window that opens. Template approval, number verification and provider choice (Netgsm, VatanSMS, Infobip or the Cloud API directly) are all part of the setup.
The data it synchronises
Approved message template management
Order and shipping notifications
Cart abandonment reminders
Inbound message / support flow
Delivery and read receipts
Number and profile verification
How the data flows
01
Business account and number verification
The WhatsApp Business account is created, the number verified and the business profile completed. We never build this on a personal number.
02
Template approval
Every notification you plan to send is submitted for template approval. Bulk notifications cannot go out on an unapproved template, so this step is factored into the schedule.
03
Event mapping
Order confirmation, shipping notifications and return processes are mapped to templates.
04
Inbound message flow
Customer replies reach the support team. The channel is not opened until it is defined who answers and within what time.
05
Measurement
Delivery and read receipts are monitored, and whether the channel actually reduces support load is measured.
What we watch for in this integration
Template approval takes time; the launch schedule is built around it
Once the channel is open, customers expect a reply; an unanswered WhatsApp line does brand damage
Commercial content requires consent; campaigns are never sent dressed up as notifications
If the support flow cannot be covered outside working hours, an automatic response is set up
Cart abandonment reminders work well on this channel, but the balance of consent and frequency has to hold
The setup process
01
Data and permission analysis
We decide which data flows in which direction, which system is the master, and what API permissions are required.
02
Mapping table
Product, variant, category, warehouse and account fields are mapped between the two systems, one by one.
03
Development and testing
The integration is built on a development store; order, return and error scenarios are tested with real data.
04
Going live
It is released through a controlled switchover, watched closely for the first few days, with the error queue monitored.
05
Monitoring and maintenance
Logging, error alerting and API version updates continue under the maintenance retainer.
What we need from you before we start
WhatsApp Business account and a verified business number
The notification templates you will use
Where the support flow lands and your target response time
Your consent-system brand registration