WhatsApp Coexistence chatbot: bot and team on the same number

Yes, you can run a chatbot on WhatsApp Coexistence without pulling your team off the phone. The bot works through the Cloud API, your people keep replying in the WhatsApp Business app, and every conversation shows up on both sides, on the same number. The catch is that you now have two "agents" looking at the same customer. Without a handoff rule, the bot talks over your rep, the customer gets confused, and your number's quality takes the hit. This guide covers what is worth automating, the real risks, and how to set up the handoff.

One upfront note: Vazante is not a chatbot builder or a shared inbox. Further down we explain what it actually does here, and when you need a different tool.

How a bot and a team share one number

With WhatsApp Coexistence, the number lives in the phone app and on the Cloud API at the same time. That makes a clean split possible:

• The bot is a system connected through the API. It reads incoming messages and replies automatically.
• Your team stays on the phone, in the same app they have always used.
• Conversations are visible on both sides. Whatever a rep sends from the app is visible to the API too.

Three platform rules shape this setup. Get them straight before you build anything.

The 24-hour window belongs to the API, and only the customer opens it. The window opens and resets with every customer message, never with a business message. Inside it, the bot can reply freely. Outside it, any business-initiated message through the API needs an approved template. The details are in the 24-hour window with coexistence.

What your rep sends from the phone does not touch the window. Messages from the app are free and do not open, extend or affect the API window. If a rep chatted with a lead from the phone last night, that does not give the bot permission to message them today outside the window.

Only what goes out through the API is billed. Meta charges per message, based on a public rate card that varies by country and template category. Service replies inside the window are not charged today, but check Meta's current rate card before you budget.

What to automate, and what stays human

Rule of thumb: the bot handles what is repetitive and predictable. People handle what is an actual conversation.

Picture a home services company running click-to-WhatsApp ads for spring HVAC tune-ups. Half the incoming messages ask the same three things: service area, availability this week, and price range. Automating just that frees the dispatcher for the conversations that turn into booked jobs. You do not need to automate the whole thread to get the time back.

Where bots go wrong next to a team

The bot talking over a human

This is the big one. Your rep is mid-negotiation on the phone, the customer writes "ok let me check with my wife", and the bot jumps in with "Hi there! How can I help you today?". Trust gone, instantly.

The fix is a clear handoff rule: if a human replied in the conversation recently, the bot stays quiet. Because app messages also show up on the API side, a well-built bot can see that someone on the team is already in the thread. Ask your vendor whether their tool does this, and exactly how.

Number quality

A bot that over-replies, repeats itself or loops earns blocks and reports. Your number has one quality rating, shared by the app and the API. A misconfigured bot can tank the very number your sales team depends on. See WhatsApp number quality.

Nobody opens the app anymore

A side effect few people mention: if the bot handles almost everything and the team stops opening WhatsApp Business, the connection is at risk. If nobody opens the app for about 14 days, Meta may drop the connection, and the bot goes down with it. Coexistence assumes humans are still using the app.

One number, one API

A number can only be on one API at a time. If your chatbot vendor connects the number through its own API, it takes that slot. Before you sign anything, know which system will own that number's connection.

Launch checklist for a bot next to your team

• The bot covers a short, written list of topics, not "everything"
• There is a silence rule when a rep replies from the phone
• Every bot reply offers a way to reach a person
• Messages outside the 24-hour window use an approved template
• Someone reviews a sample of bot conversations every week
• Someone on the team opens the app regularly
• You decided which system owns the number's connection

Questions to ask a chatbot vendor

Before you sign with any tool, get these answered in writing:

1. Does it work with a number on coexistence, with the team still in the app?
2. Does the bot notice when a rep replied from the phone, and stop?
3. How does it handle messages outside the 24-hour window?
4. Who owns the number's connection with Meta, and how do I disconnect if I leave?
5. What happens to the bot if the connection drops?

If the answer to question two is vague, be careful. That answer decides whether your customer is talking to one company or two.

Where Claude and Vazante fit, and where they do not

Vazante is not a chatbot platform. It does not reply to customers on its own, has no support queue, does not route conversations between reps, does not tag conversations and does not blast cold lists. If what you need is multi-agent support with queues and routing, use a shared inbox built for that job.

What Vazante does is different, and it is built for whoever manages ad spend and revenue. With the coexistence module, you ask Claude to send a message to a customer, it shows you the text, and it only sends after you confirm. Nothing goes out without your eyes on it. And every conversation that came from a click-to-WhatsApp ad is tied to the ad that started it, with the cost. It is AI working alongside you, not instead of you.

To see how that ad-to-conversation match works, read which ad started the WhatsApp conversation.

Start small

Pick one repetitive topic, write the answers, set the silence rule and run it for a few weeks while you read the transcripts. Then expand. The most common mistake is trying to automate the entire support flow in month one, and it is on the list in WhatsApp Coexistence mistakes.

If what you want is to measure what WhatsApp brings in from your campaigns and send messages through Claude with confirmation, see the WhatsApp Coexistence page. Module pricing starts at US$ 39 a month per number on the pricing page.