AI support agents for WhatsApp

What connecting WhatsApp actually involves

The WhatsApp you connect for support is not the app on a phone. It is the WhatsApp Business Platform, Meta's hosted Cloud API, which routes messages between a registered business number and Evoriqa with no handset and no QR code in the loop. That distinction shapes the whole setup, so it helps to know it going in.

There are three ways to carry a WhatsApp number, chosen per channel at connect: Meta Cloud API (recommended — your own Meta app talking straight to WhatsApp, with no per-message middleman fee and your app's own name and branding), or the same Telnyx or Infobip credentials you'd use for SMS, pointed at a provider-provisioned WhatsApp sender. The Cloud API setup below is the one most businesses want, and the rest of this page assumes it.

Connecting comes down to a short sequence, and the account work happens on Meta's side before anything reaches your agent:

1. 1A Meta Business account holds the WhatsApp Business Platform, so you start

from Meta Business Suite rather than the phone app.

1. 1You choose the phone number that will carry your WhatsApp Business messages.

It can be a new number or one you already own.

1. 1Meta verifies the number and reviews the display name customers will see,

which is the name shown at the top of every thread.

1. 1The number connects to Evoriqa, so inbound messages route to your agent

and replies go back out on the same number.

The business-number reality

Here is the part that catches people out. A number registered on the WhatsApp Business Platform belongs to the platform. It cannot also be signed in to the consumer WhatsApp app or the WhatsApp Business app on a phone at the same time, because Meta ties one number to one of those at once. So the number your team uses for personal chats is usually the wrong one to connect.

The safest choice is usually a dedicated line: a new mobile or landline number, or a support number that isn't already living on someone's phone. If you migrate an existing number onto the platform, it stops working in the app it was in before, which is fine if you planned for it and a nasty surprise if you didn't. None of this is a Evoriqa limit; it is how Meta's platform is built. Knowing it up front keeps you from connecting a number you still need somewhere else.

The display name matters more here than on other channels. On WhatsApp the customer sees a business name and, once Meta approves it, a verified badge, so the name you register is the name that shows above every conversation. It is worth getting right the first time rather than after customers have already seen a placeholder.

Handoff to a human, mid-thread

WhatsApp conversations don't end cleanly, and some of them should reach a person. When your agent hits something it shouldn't answer, a billing dispute, an upset customer, a request outside what it is allowed to do, it can hand the thread to your team without the customer noticing a seam.

From the customer's side, nothing switches apps or numbers. They keep typing in the same WhatsApp thread, and replies still arrive from your business number, whether the sender is the agent or a person.

What changes is who is answering, and here WhatsApp forces a clean rule: once a teammate opens the conversation and takes it, the agent stops replying on that thread. It does not keep answering alongside the human, so the customer never gets two voices on the same message. The teammate replies in their own words, with the earlier exchange and the agent's notes in view, and when they hand the thread back or mark it resolved, the agent resumes picking up new inbound messages there. Until then it stays silent on that one conversation while still handling every other thread in parallel.

Read receipts and typing, both ways

On the Cloud API, WhatsApp's delivery and read receipts flow into your shared inbox. Each reply your team or the AI sends shows a muted Delivered and then Read hint under it, and a failed send is marked Not delivered with the reason and a one-click retry, so you can see what actually reached the customer without leaving the inbox.

It runs the other way too. The moment a customer's message arrives, the platform marks it read — the blue ticks they know — and raises a typing… indicator, so the customer sees they were heard while the AI composes its reply rather than staring at silence. It needs no extra setup and rides the same connection. The Telnyx and Infobip transports still surface a reply's delivery status — delivered or failed — but not read receipts or the inbound typing signal, so the blue ticks and the live typing… indicator are specific to the Cloud API.

Messages at midnight, and the 24-hour window

Meta only lets a business message a customer freely within 24 hours of that customer's last message. Because your agent answers inbound questions rather than cold-messaging, its replies sit inside that window by definition: the customer just wrote, so a reply is always allowed.

That is what makes the out-of-hours experience on WhatsApp different from an away message. A customer who writes at midnight is not met with "our office is closed, we'll reply Monday." The agent answers the actual question then and there, from what you have taught it, in the thread already open on their phone. No form to fill, no ticket number, no wait for opening time.

The edge case to plan for is the handoff that lands off-hours. If the agent passes a midnight message to a human and no one is on shift, the clock that now matters is the customer's 24-hour window. A teammate who replies the next morning, still inside 24 hours, sends for free. If more than a day passes before anyone answers, WhatsApp no longer allows a free-form reply, and reopening the thread requires one of Meta's pre-approved template messages. It is worth knowing which conversations can wait overnight and which cannot before that window quietly closes on one that mattered.

What the agent handles inside the thread

Most of what the agent does on WhatsApp is ordinary support, done in line without moving the customer anywhere. It can qualify a lead by collecting the details you ask for, and it can book appointments in the conversation when you connect a calendar, so a customer goes from question to booked slot without leaving the chat. For an estate agency, that is a Saturday viewing arranged on Friday night rather than a callback queued for Monday.

WhatsApp also shapes what comes in. People use it like a personal chat, so a support request often arrives as a photo of a receipt, a screenshot of an error, or a voice note rather than a neatly typed question. The agent works from the text of the conversation; when resolving something depends on a person actually looking at that attachment, that is one of the clean moments to hand the thread over, since a person can open the image and the agent is working from text.

Putting an agent on the channel instead of a keyword auto-reply matters most for that reason. Someone messaging your business on WhatsApp expects the back and forth of a chat, not a menu that answers "reply 1 for hours, 2 for location," and they get a response to the question they actually asked, at the hour they asked it, in the app already open in their hand.