The official WhatsApp Business Platform built directly into your own admin panel or CRM, with a custom AI chatbot answering enquiries around the clock and a defined handoff to a human the moment it matters.
Your number, your CRM, your data. Instant, correct, and handed to a human at the right moment.
Best for
Businesses with WhatsApp enquiries, slow response times, missed leads, appointment booking needs, or repeat customer questions — and anyone who wants the WhatsApp layer inside their own CRM rather than rented from a SaaS dashboard.
Typical timeline
2-4 weeks
What we measure
Response time and lead-to-appointment rate
What does WhatsApp Automation include?
Alphenex builds WhatsApp automation directly on the official WhatsApp Business Platform (Cloud API) and integrates it into the client's own admin panel or CRM, rather than reselling a third-party dashboard such as Wati or AiSensy. That means the conversation data, the automation logic, and the customer relationship stay inside systems the business owns. Each build includes a custom-designed AI chatbot that runs 24 hours a day to answer enquiries, qualify leads, book appointments, and handle the recurring tasks specific to that business — with compliant opt-in, approved message templates, CRM routing, and explicit escalation rules for handing a conversation to a person.
WhatsApp is the largest messaging platform in the world, with its biggest user base in India and near-universal business use across the Gulf. In those markets a buyer who has an enquiry does not send an email — they message, and they expect an answer now. Automation lets you respond instantly, qualify the enquiry, answer the questions that come up every time, and route the conversations that need a person to one.
Automation that survives contact with real customers
A chatbot that cannot say "let me get someone" is a liability, not an asset.
WhatsApp is the default business channel across the Gulf and increasingly in the UK and USA. That makes it the fastest way to answer an enquiry — and the fastest way to annoy a customer, get reported, and lose the number entirely.
01
Why does the official WhatsApp Business Platform matter?
Because unofficial gateways get numbers banned, and the ban takes the conversation history and the customer relationship with it. Tools that automate the consumer WhatsApp app violate the terms of service, and enforcement is automated and permanent. Alphenex builds only on the official WhatsApp Business Platform, integrating Meta’s Cloud API directly, which means approved message templates, documented opt-in, proper rate limits, and a number that survives being used at scale.
Official WhatsApp Business Platform, integrated directly against Meta’s Cloud API
No automation layered over the consumer WhatsApp app
Message templates submitted and approved before launch
Rate limits and quality rating monitored rather than discovered
02
Why build WhatsApp into your own CRM instead of using Wati or AiSensy?
Because a third-party dashboard is a tenancy, not an asset. Tools like Wati and AiSensy are competent products and they get a business messaging quickly — but the conversation history, the automation logic, and the customer data live in someone else’s system, the pricing usually carries a per-conversation markup on top of Meta’s own charge, and what the flows can do is capped by what that vendor built. Alphenex integrates the Cloud API directly into the client’s own admin panel or CRM instead. The business keeps its data where the rest of its customer records already are, the automation can do anything its own systems can do, and leaving a vendor never means leaving the conversation history behind.
Conversation history and customer data stored in systems the business owns
No per-conversation SaaS markup layered on top of Meta’s own pricing
Automation logic can reach the rest of the CRM — orders, bookings, inventory, invoices
No vendor lock-in: the number, the templates and the history stay with the business
Custom flows are limited by what the business needs, not by a vendor’s feature roadmap
03
What can a custom AI chatbot actually handle on WhatsApp?
Whatever repeats. The chatbot Alphenex builds is designed around one business rather than shipped as a generic template, so it runs 24 hours a day answering the enquiries that arrive every week, qualifying leads against the rules agreed before launch, booking appointments into a real calendar, checking an order or booking reference, and handling the tasks specific to that operation. What it is deliberately not built to do is improvise on price, argue with a complaint, or keep a frustrated customer in a loop — those escalate immediately.
Runs 24/7, so an enquiry at 2am is answered rather than queued until morning
Qualification questions matched to the business, not a generic template flow
Appointment booking written into a real calendar, not promised and forgotten
Can read from the connected CRM — order status, booking reference, account history
Escalates on pricing nuance, complaints, negative sentiment, or a request for a person
04
What are the rules for messaging customers on WhatsApp?
Two constraints drive the whole design. First, opt-in: you may only message people who agreed to be contacted on WhatsApp, and that consent must be captured and stored. Second, the 24-hour customer service window: outside 24 hours from the customer’s last message you can only send pre-approved template messages, not free-form text. Workflows that ignore either get flagged by recipients, and a falling quality rating reduces how many messages the number can send at all.
Explicit opt-in captured at the point of enquiry and recorded
Free-form replies only inside the 24-hour service window
Approved templates for anything outside it, with clear opt-out
Quality rating watched as an operational metric, not an afterthought
05
How much should the bot handle before a human takes over?
Acknowledge, qualify, answer the genuinely repetitive questions, and stop. Automation is excellent at instant response, structured qualification, appointment slots, and the same six questions every enquiry asks. It is bad at pricing nuance, complaints, and anything where the customer is already frustrated. Alphenex defines escalation triggers explicitly — high-value enquiry, repeated misunderstanding, negative sentiment, or a direct request for a person — and every flow has a route to a human that the customer can reach immediately.
Bot handles acknowledgement, qualification, FAQs and scheduling
Escalation triggers defined explicitly, including "talk to a person"
Business hours and out-of-hours behaviour handled differently
No loop a customer can get stuck inside
06
Which markets treat WhatsApp as the default business channel?
India first — it is WhatsApp’s largest market by a wide margin, and messaging a business there is simply how commerce works. Across the Gulf the same is true: in the UAE, Saudi Arabia, Qatar and Oman, WhatsApp is the normal channel for a business enquiry rather than an alternative to email, and response expectations are correspondingly short. Adoption in the UK and Europe is growing but still trails both. A business selling into any of those markets while offering only an email form is asking buyers to use a channel they have largely abandoned for commercial conversation — usually visible as a high landing-page bounce rate on that traffic long before anyone diagnoses the cause.
India: WhatsApp’s largest user base, and the default channel for business contact
Gulf: default enquiry channel across UAE, Saudi Arabia, Qatar and Oman
Response expectations measured in minutes, not next business day
Arabic-language flows added where the audience justifies them
Business-hours logic set to the customer market, not the delivery team’s
Third-party dashboards vs a WhatsApp layer you own
Third-party dashboards vs a WhatsApp layer you own
Wati / AiSensy-style SaaS
Alphenex built into your CRM
Where the data lives
The vendor’s platform
Your own admin panel or CRM
Underlying API
Official platform, resold
Official platform, integrated directly
Pricing
Meta’s cost plus a per-conversation markup
Meta’s cost, plus a build you own
What the flows can do
Capped by the vendor’s feature set
Anything your systems can do
CRM integration
Via connectors, where supported
Native — it is the same application
Leaving the vendor
History and automation stay behind
Nothing to leave — you own it
AI chatbot
Template flows, generic
Custom-designed for the business, 24/7
Human handoff
Supported
Defined escalation triggers, no dead ends
Same channel, different job
What the chatbot is for changes completely by business.
A dental practice and a Shopify store both want faster WhatsApp replies. What "faster" is supposed to achieve — and therefore what gets automated — is not remotely the same.
01
Clinics, dental and appointment-based services
The goal is a filled diary. Every conversation is trying to become a booking, and the second-biggest cost after a missed enquiry is a no-show.
Live calendar availability offered in the chat, not "we will get back to you"
Appointment confirmations, reminders and reschedule links as approved templates
Triage questions that route urgent cases to a person immediately
No clinical advice given by automation — that escalates every time
Post-appointment follow-up and recall built from opted-in templates
02
E-commerce and Shopify stores
The goal is fewer support tickets and more recovered revenue. Most inbound messages are the same three questions about an order that already exists.
Order status, tracking and returns answered from live CRM or store data
Abandoned-cart recovery through opted-in template messages, not blasts
Product and stock questions handled without a human where the data allows
Refund and complaint conversations escalated on first sentiment trigger
Post-purchase flow used for repeat orders, which is where the margin is
03
B2B and high-ticket services
The goal is a qualified conversation with a real decision-maker. Volume is low, value is high, and a badly handled first message costs a great deal more than it does elsewhere.
Qualification against the written rules — budget, timeline, market, decision role
Routing straight to a named person for enquiries above a value threshold
Meeting booking as the conversion event, with calendar integration
Conversation history written back to the CRM against the right opportunity
Automation kept deliberately light — a high-value buyer should reach a human fast
Scope of work
What's included
A focused delivery system with every component designed to support the same business outcome.
WhatsApp Business setup
Official Cloud API onboarding, number and display-name verification, templates, opt-in logic, and compliant customer messaging.
Built into your own system
The WhatsApp layer is integrated into your admin panel or CRM by Alphenex, so conversations, contacts and automation live where the rest of your customer data already is.
Custom 24/7 AI chatbot
A chatbot designed around your business rather than a template flow — answering enquiries, qualifying leads, booking appointments, and handling the tasks that repeat.
Chatbot qualification
Flows that ask the right questions, answer FAQs, collect details, and route serious leads.
CRM and notifications
Lead capture, team notifications, pipeline updates, and handoff rules.
Broadcast and reactivation
Segmented follow-up and approved message templates for opted-in contacts.
How we deliver
A clear, accountable process
Each stage produces something measurable before the next one begins.
01
Map conversations
We identify common enquiry types, qualification questions, support needs, and human handoff points.
02
Build flows
We create chatbot paths, templates, routing, notifications, and CRM capture.
03
Test compliance
We review opt-in, message templates, reply windows, and edge cases before launch.
04
Improve
We refine based on real conversation data and sales feedback.
Why Alphenex
Built for useful outcomes, not activity reports.
A practical delivery model for teams that need clarity, momentum, and visibility from day one.
Faster replies to new enquiries
Better qualification before sales calls
Fewer missed WhatsApp leads
Reusable follow-up paths for sales and support
Questions, answered
Frequently asked questions
Is WhatsApp automation compliant?
It can be compliant when opt-in, approved templates, customer-service windows, and unsubscribe expectations are handled properly. We plan workflows around those rules instead of sending spam broadcasts.
Can a chatbot hand off to a human?
Yes. Good WhatsApp automation should hand off complex or high-value conversations to a human quickly. Automation handles speed and structure; humans handle nuance.
Can WhatsApp connect to CRM?
Yes. WhatsApp enquiries can be captured, tagged, routed, and reported inside a CRM or dashboard depending on the tools used.
What is the 24-hour rule on WhatsApp?
Outside a 24-hour window from the customer’s most recent message, a business can only send pre-approved template messages rather than free-form text. Inside that window, normal conversation is allowed. This single rule shapes most of the workflow design — it is why templates are drafted and submitted for approval before launch, and why re-engagement sequences have to be built from approved templates rather than written ad hoc.
Can I send broadcasts to my customer list?
Only to contacts who opted in to WhatsApp specifically, using approved templates, with a clear way to stop. Uploading a purchased list or a general customer database that never consented to WhatsApp contact is the fastest route to recipient blocks, a falling quality rating, and reduced sending limits on the number. Segmented, consented, genuinely useful messages are what the channel supports.
Do you use the official WhatsApp Business API?
Yes, exclusively — integrated directly against Meta’s Cloud API. Tools that automate the consumer WhatsApp app violate the terms of service and enforcement is automated and permanent, taking the number and the conversation history with it. That risk is not worth the lower setup cost, particularly for a business whose enquiries all arrive on that number.
Why not just use Wati, AiSensy or a similar platform?
You can, and for a business that needs to be messaging next week they are a reasonable way to start. The trade-off is that a third-party dashboard is a tenancy rather than an asset: the conversation history and customer data sit in the vendor’s system, the pricing generally adds a per-conversation markup on top of what Meta already charges, and the automation can only do what that vendor has built. Alphenex integrates the Cloud API directly into your own admin panel or CRM instead, so the data stays where the rest of your customer records are, the flows can reach your orders, bookings and invoices, and changing your mind about a vendor never means leaving your conversation history behind.
Is the AI chatbot a generic template or built for my business?
Built for the business. The flows are designed around the enquiries you actually receive, the qualification rules you actually use, and the systems you actually run — which is what lets the bot answer an order status, offer a genuinely free appointment slot, or check an account reference rather than replying with a menu. It runs 24 hours a day, and it is deliberately scoped: pricing nuance, complaints, negative sentiment, and any direct request for a person escalate immediately rather than being handled by automation.
Can the chatbot handle Arabic?
Yes, where the audience justifies it. Flows can run in Arabic or as a bilingual path with language selection at the start, and templates are submitted per language. As with the rest of the site, Alphenex adds a language only when there is genuine capacity to handle the replies it generates — an Arabic bot that escalates into an English-only team creates a worse experience than not offering it.
Where we deliver
WhatsApp Automation by market
Alphenex delivers whatsapp automation remotely for businesses in or targeting these markets. Each market page covers the local search behaviour, buyer expectations, and conversion patterns we build around.