WhatsApp business automation is the process of building automated conversation flows on WhatsApp that handle incoming messages, qualify intent, send structured responses, and route to a human when needed, without requiring a developer to configure each step. In Telerivet, this works through a combination of a connected WhatsApp route, a service you build inside the platform, and the conversation logic you define to handle what happens when a message arrives.
Most people who reach this page already know they want WhatsApp. The question they are actually asking is: how does it work inside Telerivet specifically, what do I need to get started, and what can I realistically build?
This post answers all three.
How WhatsApp Connects to Telerivet
There are three ways to bring WhatsApp into your Telerivet account, and the right one depends on whether you already have a WhatsApp Business API number and what your volume and compliance requirements look like.
Native provisioning through Telerivet is the fastest path for operators who do not yet have a WhatsApp Business API setup. Telerivet handles the number provisioning and connects it to your account directly. You get a dedicated WhatsApp number, a route in your account, and access to the full service-building layer without needing to manage a separate BSP relationship. This is the right starting point for most new WhatsApp operators.
Bring your own connectivity (BYOC) is for those who already have a WhatsApp Business API number through another provider or Meta directly Rather than provisioning a new number, you connect your existing number to Telerivet and route it through the platform's service and automation layer. BYOC makes sense when you have an established number with message history, a specific pricing arrangement with your BSP, or a regional provider requirement. The setup is slightly more involved but the end result is the same: your WhatsApp number sits inside Telerivet alongside your other channels and benefits from the same workflow logic.
As an official Meta Business Partner, Telerivet supports WhatsApp alongside Instagram and Facebook Messenger from the same account, which matters for operators who want to manage Meta channel conversations without switching between platforms.
The Architecture That Makes WhatsApp Different
The reason WhatsApp changes what is possible, compared to SMS or email, comes down to one concept: the user-initiated conversation.
When a customer messages your WhatsApp number, they open a 24-hour service window. Inside that window, you can respond with text, images, product catalogs, numbered menus, and automated flows, and none of it requires template pre-approval. The conversation is two-way, unfiltered, and automation-ready.
Business-initiated WhatsApp messages are a different matter. They require approved templates, carry per-message costs, and are increasingly subject to delivery filtering as Meta tightens spam controls. Most operators who try to use WhatsApp the way they use SMS broadcast quickly hit the ceiling of what business-initiated messages allow. The goal here is quality reach outs.
One architecture that works is built around getting the customer to initiate. An SMS broadcast goes out to your contact list with a short message and a single call to action: tap this link. The link opens a WhatsApp conversation from the customer's side. From that point, your automated service takes over: a greeting, a menu, a product or service inquiry flow, a routing decision. The customer initiated the conversation. The service window is open. Everything that happens inside it costs a fraction of a business-initiated message and carries none of the template restrictions.
This is the pattern that runs underneath most of the use cases described in this post, and it is the reason operators who build on WhatsApp through Telerivet tend to see significantly higher engagement than they achieved through broadcast-only channels. The broader question of how channels fit together across a customer journey is worth thinking through early, because WhatsApp rarely operates in isolation for long.
What Operators Build on WhatsApp in Telerivet
WhatsApp in Telerivet supports a range of workflows depending on the operator's vertical and the problem they are solving. The most common patterns fall into four categories.
Customer intake and service routing is the most immediate use case for most operators. A customer messages in, an automated service captures their name, issue type, and contact details, and routes the conversation to the right team member or triggers a follow-up action. Building this kind of intake service is typically the first thing an operator builds once their WhatsApp route is live, and it handles the highest-volume, lowest-complexity requests without requiring any manual attention.
Appointment reminders and scheduling is particularly well-suited to WhatsApp because the two-way nature of the channel makes confirmation and rescheduling easy. A reminder goes out, the patient or client replies to confirm or request a change, and the service handles the response. Clinics and healthcare operators using this workflow consistently see no-show rates drop within the first month.
Lead capture and qualification works on WhatsApp because the conversation format naturally captures intent signals that a form cannot. A prospect who taps a link from an ad or a property listing and messages your WhatsApp number has already demonstrated interest. The service qualifies them through a short conversation flow before any human time is spent. Real estate operators use this to filter serious inquiries from browsing traffic automatically.
Alerts, dispatch, and field coordination is the enterprise and NGO pattern. A field team receives a WhatsApp message with an assignment, confirms receipt, and updates status, all within a structured service flow that logs responses without manual data entry. Organizations running early warning or dispatch operations use WhatsApp here because it reaches field staff reliably and the two-way flow creates an auditable record and valuable data capture such as images, voice files, location coordinates.
When these workflows are connected to each other and to other channels in a coordinated sequence, the result is what practitioners are starting to call communication orchestration: the logic layer that decides which channel reaches which contact at which point in a workflow, and what happens next depending on the response. WhatsApp is typically the highest-engagement channel in that sequence, which is why getting the activation right matters.
Choosing Where to Start
For operators who are new to WhatsApp on Telerivet, the right first step is almost always a customer intake service. It is the most universally applicable workflow, it shows the full capability of the platform in a single build, and it starts generating value on the day it goes live. A walkthrough of how to build that first service is available [here].
For those running larger-scale deployments or connecting an existing WhatsApp Business API number, the enterprise WhatsApp guide covers routing architecture, template management, and multi-team access in more depth.
And for those in markets where Viber competes with WhatsApp for user penetration, the channel comparison guide for Philippine businesses is a useful starting point for channel selection decisions before building. We support both.
Frequently Asked Questions
Do I need a developer to set up WhatsApp in Telerivet? No. The native provisioning path and the service-building interface in Telerivet are designed for non-technical operators. You configure conversation flows through a visual interface without writing code. BYOC setup requires following a provider-specific connection process but does not require custom development.
What is the difference between a WhatsApp route and a WhatsApp service in Telerivet? The route is the connection between your WhatsApp number and your Telerivet account. The service is the logic layer that handles what happens when a message arrives on that route. You need both: the route brings messages in, the service decides what to do with them.
Can I use the same Telerivet account to manage WhatsApp, SMS, and other channels? Yes. Telerivet is built as a multichannel platform. WhatsApp, SMS, Viber, voice, USSD, and other channels all operate from the same account, share the same contact database, and can be combined in a single workflow. A message that fails to deliver on one channel can fall back to another automatically.
What happens when the 24-hour WhatsApp service window closes? Once 24 hours have passed since the last user-initiated message, you can no longer send freeform messages to that contact. To re-engage outside the window, you need an approved template message. Many operators handle this by designing workflows that close within the window, or by using SMS as a re-engagement channel that drives the customer back into a new WhatsApp conversation.
Is WhatsApp available in all the markets where Telerivet operates? WhatsApp has very high penetration across most of Telerivet's core markets including the Philippines, Southeast Asia, South Asia, Sub-Saharan Africa, and Latin America. API availability varies by market and can affect which activation path is most practical. If you are unsure about the best setup for your geography, the options are worth discussing with the Telerivet team before you begin.
Ready to activate WhatsApp in your Telerivet account? We will walk through the right setup for your use case.
