WhatsApp Automation
WhatsApp Automation: The Channel They Prefer, Properly Staffed
Vedixx builds WhatsApp Business API automation — instant replies to common questions, order and booking notifications, lead capture straight into your CRM, and routing to the right person. Every conversation is logged, so a channel your customers already prefer stops being invisible to the rest of your business.
What is WhatsApp automation?
WhatsApp automation uses the WhatsApp Business API to send, receive and act on messages programmatically. It covers automatic replies to common questions, order and appointment notifications, capturing enquiries into a CRM, and routing conversations to the correct team member. It requires a verified business account, and messages sent outside a 24-hour service window must use pre-approved templates.
What's included
Business API setup
Business verification, number provisioning and account configuration — the administrative gate that stalls most WhatsApp projects before they start.
Template design & approval
Notification templates written to WhatsApp’s rules and submitted for approval, with fallbacks designed for the categories most likely to be rejected.
Automated replies
Instant answers to the questions that make up most of your inbound volume, grounded in your real policies rather than a guessed script.
CRM integration
Every conversation creates or updates a contact record with the transcript attached, so WhatsApp activity is visible alongside every other channel.
Notifications & reminders
Order updates, appointment reminders and delivery notifications triggered by events in your systems, sent within the template rules.
Consent & opt-out handling
Opt-in captured and stored, opt-outs honoured immediately. WhatsApp penalises senders whose messages get blocked, so this protects the channel itself.
How an automated WhatsApp conversation flows
The 24-hour service window governs everything. Inside it you can reply freely; outside it, only approved templates are permitted — and designing around that rule is most of the work.
- 1
Inbound message
A customer messages your business number, opening a 24-hour window for free-form replies.
- 2
Identify
Match the number against your CRM to retrieve order history, bookings and previous conversations.
- 3
Answer or route
Automated reply for known questions; routed to the right human with full context for anything else.
- 4
Act
Create the lead, book the slot, look up the order, raise the ticket — through your existing systems.
- 5
Log & follow up
Transcript written to the CRM, and later follow-ups sent as approved templates once the window closes.
Where it pays for itself
Enquiries into the CRM
- The problem
- WhatsApp enquiries arrive on a phone that one person watches. Nothing reaches the CRM, and there is no record of what was promised.
- What we build
- API-connected number where every conversation creates a contact record with transcript, source and owner, routed by topic or territory.
- The result
- WhatsApp becomes a tracked acquisition channel rather than an invisible one.
Order and delivery notifications
- The problem
- Customers ask "where is my order?" by message, and each answer costs a manual lookup in another system.
- What we build
- Event-triggered template notifications at dispatch and delivery, plus automated order lookup when a customer asks directly.
- The result
- Status questions largely disappear because the answer arrives before the question.
Appointment reminders
- The problem
- No-shows are expensive, and email reminders are ignored while SMS costs add up.
- What we build
- Template reminders on a schedule before each appointment, with reply-to-confirm and reschedule handling written back to the calendar.
- The result
- Higher confirmation rates on the channel people actually read.
After-hours coverage
- The problem
- Messages arriving in the evening or at weekends sit unanswered until Monday, by which time the customer has gone elsewhere.
- What we build
- Automated handling of common questions around the clock, with genuine escalations queued and prioritised for the next working morning.
- The result
- Out-of-hours enquiries are answered rather than aged.
How it works
- 1
Account setup and verification
Business verification, number selection and API provisioning. Started first because approval timelines are outside anyone’s control.
- 2
Map the conversations
The questions you actually receive, taken from real message history, and which of them can safely be answered automatically.
- 3
Write and submit templates
Notification templates drafted to the content rules and submitted early, since rejections cost days and are best discovered at the start.
- 4
Build automation and integrations
Reply logic, routing, CRM writes and event-triggered notifications, with consent state tracked throughout.
- 5
Launch and monitor
Live with delivery, read and block-rate monitoring — the last of which is the metric that protects your account health.
Typical timeline
| Phase | Duration | What you get |
|---|---|---|
| Business verification | 3–10 days | Verified WhatsApp Business account and provisioned number. Timeline set by Meta, not by us. |
| Conversation mapping | 3–5 days | Categorised message history and a defined automation scope. |
| Template approval | 1–5 days | Submitted and approved message templates with fallbacks. |
| Build & integration | 2–4 weeks | Automated replies, routing, CRM integration and event notifications live. |
| Launch & monitoring | Ongoing | Delivery and block-rate reporting plus conversation review. |
WhatsApp Business app vs Business API
The free app is not a smaller version of the API — it is a different product for a different purpose. Almost every stalled WhatsApp automation project starts by trying to automate the app.
| Business app (free) | Business API | |
|---|---|---|
| Automation | Away messages and quick replies only. | Full programmatic send, receive and act. |
| Multiple agents | One primary device, limited linked devices. | Unlimited agents through a shared inbox or CRM. |
| CRM integration | None. | Native — every conversation logged against a record. |
| Bulk notifications | Manual and easily flagged as spam. | Approved templates with delivery reporting. |
| Cost | Free. | Per-conversation pricing plus platform fees. |
| Best for | Sole traders and very small teams. | Any business needing records, scale or automation. |
Technologies we build on
Messaging
- WhatsApp Business API
- Meta Cloud API
- Template management
- Webhook handling
Automation
- n8n
- Make (Integromat)
- Custom services
- AI reply drafting
Records
- HubSpot
- Salesforce
- Pipedrive
- PostgreSQL
Monitoring
- Delivery & read reporting
- Block-rate tracking
- Conversation logs
- Consent records
Systems we connect
Who this is for
E-commerce
Order status, delivery updates and returns on the channel customers already message from.
Clinics & healthcare
Appointment reminders and preparation instructions, scoped away from clinical advice.
Real estate
Instant response to property enquiries and viewing scheduling, where speed decides the lead.
Education
Enrolment questions, deadlines and reminders across time zones.
Hospitality & travel
Booking confirmations, pre-arrival information and on-trip support.
Local services
Quote requests and scheduling for businesses whose customers will not use a web form.
What drives the cost
WhatsApp has a running cost that other channels do not: Meta charges per conversation, on top of any platform fees. That belongs in the business case from the beginning rather than as a surprise in month two.
Conversation volume
Meta bills per 24-hour conversation window, and pricing varies by country and category. Volume is the primary running cost.
Number of templates
Each notification type needs its own template, written to the rules, submitted, and sometimes revised after rejection.
Systems connected
Reading order status or writing to a CRM means integration work per system, with its own error handling.
Depth of automated answering
A handful of fixed replies is quick. A grounded assistant handling open questions is a chatbot build in its own right.
Compliance requirements
Consent capture, opt-out handling and retention rules are non-negotiable and take real design, not a checkbox.
Multi-language support
Each language multiplies templates and testing, and templates must be approved per language.
Setup & notifications
API access, verification and event-triggered notifications. The fastest route to value.
Full automation build
Automated replies, routing, CRM integration and notifications as one connected system.
Managed channel
Build plus monitoring of delivery, block rates and conversation quality.
What you end up with
- Every WhatsApp conversation logged against a CRM record
- Common questions answered instantly, day or night
- Order and appointment updates sent before customers ask
- Enquiries routed to a named owner rather than a shared phone
- Consent and opt-outs handled correctly by default
- Delivery and block-rate reporting protecting account health
Key takeaways
- The free Business app cannot be automated properly. Anything programmatic needs the Business API.
- The 24-hour service window governs the design: free-form replies inside it, approved templates outside it.
- Start business verification first — the timeline is Meta’s, not yours, and it blocks everything else.
- Meta charges per conversation. Model the running cost before committing to high-volume notifications.
- Block rate is the metric that protects the channel. Consent handling is account protection, not paperwork.
Further reading
Why most AI chatbots don't convert
Chatbots usually fail for reasons that have nothing to do with the model. Four design faults that cost conversions, and what to build instead of a bot.
Read the guideWhatsApp Business API: what it can and cannot do
Template approval, the 24-hour service window, opt-in rules and the pricing model that surprises teams — plus what the API genuinely cannot be used for.
Read the guideShould you automate this? A decision framework
Most automation advice assumes the answer is yes. Here are the four conditions that make automating a process actively worse than leaving it alone.
Read the guiden8n vs Make vs Zapier: choosing an automation platform
How the three genuinely differ on pricing model, self-hosting, error handling and complexity ceiling — and which one to choose for each specific use case.
Read the guideRelated services
AI Automation
Automations that keep running after the engagement ends.
Read moreAI Chatbot Development
Assistants that resolve enquiries instead of deflecting them.
Read moreAI Development
Custom AI features built into your existing product.
Read moreAI Integration
Connecting AI models to the systems you already run.
Read moreWorkflow Automation
Multi-step processes that run without supervision.
Read moreBusiness Process Automation
End-to-end process redesign, then automation.
Read moreQuestions? Answered.
WhatsApp automation uses the WhatsApp Business API to send, receive and act on messages programmatically. It covers automatic replies to common questions, order and booking notifications, lead capture into a CRM, and routing conversations to the right person, all logged rather than sitting in one phone.
Let's Turn Your Traffic
Into Revenue.
Book a free 30-minute strategy call. We'll audit your current growth, spot the biggest opportunities, and map a clear plan, no pressure, just value.
Free audit · Custom plan · Clear pricing & timelines