Most explanations of WhatsApp automation start with the technology and work toward the use case. This one goes the other way. Start with what the customer experiences, then trace the technical chain backward to understand what is happening at each step.
What the customer experiences
A customer in Thane places an order on a Mumbai D2C brand's Shopify store at 8 PM. Within 30 seconds, a WhatsApp message arrives:
"Hi Priya! Your order #1234 for the Rose Clay Face Mask (50g) has been confirmed. Expected delivery: 3 5 business days. Track your order here: [link]"
Three days later, when the order ships, another message arrives automatically with the courier tracking link. When delivered, a third message asks for a review.
Priya did not interact with any human at the brand. No one typed those messages. They were sent automatically triggered by events in the Shopify store, processed through the WhatsApp API, and delivered through Meta's infrastructure.
What happened behind the scenes
Breaking that chain into its components:
Component 1: The trigger event
Every automated WhatsApp message starts with a trigger. Common triggers in a Mumbai business context:
- Order placed (Shopify, WooCommerce)
- Appointment booked (Google Calendar, Calendly, booking software)
- Form submitted (website enquiry form, lead ad)
- Payment received or overdue (payment gateway, CRM)
- Customer inactive for X days (CRM, e-commerce platform)
- Incoming WhatsApp message received (chatbot flow trigger)
Your system detects this event via a webhook a real-time notification sent to your automation platform the moment the event occurs.
Component 2: The automation rule
When the webhook arrives, your automation platform (n8n, Make, Zapier, or the BSP's built-in flow builder) checks: what should happen? The rule says: "When an order is placed, send WhatsApp template ORDER_CONFIRMATION to the customer's number, filling in their name and order details."
Component 3: The message template
For outbound messages (business-to-customer, where the customer has not messaged you in the last 24 hours), WhatsApp requires a pre-approved template. The automation selects the right template and fills in the personalisation variables name, order number, delivery date.
Component 4: The BSP and Meta's API
The automation platform sends the populated template to your BSP's API endpoint. The BSP forwards it to Meta's WhatsApp API. Meta delivers it to the customer's phone typically within seconds.
Component 5: The customer's reply
When the customer replies, the message goes from their phone to Meta's API to your BSP to your system. Your chatbot or shared inbox receives it and either responds automatically (if the flow has a response for that input) or routes to a human agent.
Ready to take the next step?
Let Perceptra scope the right approach for your business.
Book a Free Strategy Session ?The inbound flow (chatbot)
For inbound automation where a customer initiates the conversation the chain is simpler. The customer sends a message. Meta delivers it to your BSP. Your BSP routes it to your chatbot flow. The chatbot processes the input, selects the appropriate response from your knowledge base, and sends a reply through the same chain in reverse.
Because the customer initiated the conversation, you can use freeform text in your response (not a template). This 24-hour window from the customer's first message allows natural conversation.
What the infrastructure looks like in practice
For a Mumbai business deploying a complete WhatsApp automation system:
BSP: Interakt, Wati, or Gupshup (based on volume and integrations) Automation platform: n8n (self-hosted, most flexible), Make, or Zapier Integration: Shopify webhook ? n8n ? BSP API ? WhatsApp Shared inbox: BSP dashboard, accessible to your full team CRM logging: n8n writes lead data to HubSpot or Zoho simultaneously
This full stack handles triggered outbound messages, inbound chatbot flows, and CRM logging all from a single WhatsApp number, all managed in one dashboard.
See workflow automation for how we build the n8n integration layer.
Frequently asked questions
Yes. The entire outbound chain trigger, template selection, sending is automated. No human action is required. The automation runs 24/7.
Message delivery is queued and retried automatically by the BSP. For short outages, customers receive messages minutes later when the API recovers. For extended outages (rare), your BSP provides status notifications.
Yes. Your BSP dashboard shows every message sent, delivered, read, and any reply received. Full audit trail.
The automation targets the number on record. If a customer changes their number, the message goes to the old number. Update contact details in your CRM promptly when customers notify you of a number change.