WhatsApp automation: what pays off, and what gets your number banned
By Manoj Gurumurthy · 2026-03-28 · 8 min read
Most of what a business receives on WhatsApp is the same handful of questions, over and over: prices, timings, sizes, delivery, how to book. Answer them in seconds, day and night, and WhatsApp becomes one of your best sales channels. Answer them hours later and the customer has already moved on.
If you're thinking about building anything serious on WhatsApp Business API, here's the brain-dump I wish I'd had when I started.
The three use cases that actually pay off
The order matters. These are listed in increasing complexity.
Support and FAQs
Opening hours, pricing, policies, delivery times, returns. An agent trained on your FAQs and policies answers these in seconds, day and night, and passes anything unusual to your team with the chat attached. This is the lowest-risk, highest-return place to start.
Product enquiries
"Does this come in medium?" "Do you ship to Dubai?" "Which plan fits a team of 20?" An agent that knows your catalogue answers with the right details and suggests the right fit, instead of leaving the customer waiting until morning.
Booking calls
When a customer is ready to talk, the agent books a call straight into your team's calendar. This is where much of the value is, and also where the complexity lives: people send voice notes and images, or change the subject halfway through.
If you're just starting out, get support and FAQs right first.
The WhatsApp API gotchas nobody mentions
Bulk messaging gets numbers banned. WhatsApp suspends numbers that send unsolicited or repeated promotional messages. Use WhatsApp to answer the customers who message you, and keep newsletters and promotions on email.
Template approval takes 3–7 days. Every marketing-style message you send outside a 24-hour customer window has to use a Meta-approved template. Submit them early. Keep them short. Use variables sparingly. Meta's approval bot is picky about anything that "feels promotional."
The 24-hour window is brutal. Once a customer messages you, you have 24 hours to respond freely. After that, only approved templates work. This changes how you design flows. You'll want to keep conversations flowing with open-ended questions that encourage replies.
BSPs matter more than you think. The Business Solution Provider you pick (Twilio, MSG91, Gupshup, 360dialog, AiSensy, etc.) affects pricing, template approval speed, and how much control you have. I use 360dialog for clients that need fine control and AiSensy for clients that want a simple interface. Twilio is fine but expensive at volume.
Don't skip the webhook. Every deployment I've done that skipped webhooks and used polling broke at some point. Set up the webhook properly, handle 200 responses correctly, and save yourself future pain.
The stack I default to
For most SMB-level deployments: WhatsApp Business API via 360dialog + n8n for orchestration + OpenAI for conversational AI + Google Sheets or Airtable for tracking. Simple, cheap, fast to ship.
For scale (10K+ messages/day): swap n8n for a custom Node service, Sheets for Postgres, and add a message queue. You'll know when you need this because n8n will start timing out.
When not to use WhatsApp
Honestly, this is the section I wish existed when I started.
- If your audience is mostly in the US, they don't really use WhatsApp. Use SMS.
- If your messages need to be longer than 2-3 short paragraphs, email is still better.
- If you need to share regulated data (medical records, account details), keep that part off WhatsApp. Use WhatsApp for questions and bookings, and a channel with proper compliance support for the sensitive part.
Deploy it right and WhatsApp becomes your highest-ROI channel. Deploy it wrong and you'll get your number banned in 30 days and spend another month getting a new one reapproved.