---
title: "WhatsApp for support, the bridge route and the official route, honestly compared"
description: "Linking a WhatsApp number by QR code and going through Meta's Business API are two different products with different failure modes. Which one you want depends on how much you can afford to lose the channel."
date: "2026-08-12"
tags: "whatsapp, integrations, meta"
canonical: "https://www.proxyai.app/blog/whatsapp-bridge-vs-official-business-api"
---

> For the complete documentation index, see [llms.txt](https://www.proxyai.app/llms.txt). Request public content pages with `Accept: text/markdown`.

# WhatsApp for support, the bridge route and the official route, honestly compared

Linking a WhatsApp number by QR code and going through Meta's Business API are two different products with different failure modes. Which one you want depends on how much you can afford to lose the channel.

12 August 2026·6 min read

**In short:** There are two ways to put an AI assistant on a [WhatsApp](/services/channels/whatsapp) number. A **bridge** links an existing number by scanning a QR code, instant, available in any country, no Meta account, but unofficial, and the phone needs opening every 14 days. The **official WhatsApp Business API** runs through Meta, is not spontaneously disconnected, and limits businesses Meta has not verified to starting 250 conversations a day. Choose the bridge to test the channel; choose the official route once you cannot afford to lose it.

There are two ways to put an assistant on a WhatsApp number, and most tools quietly pick one for you. They are not equivalent, they fail differently, and the right answer changes as the business grows. Worth understanding before you commit a number your customers already have.

## At a glance

|  | Bridge (QR pairing) | Official Business API |
| --- | --- | --- |
| Route | Links an existing number as a device | Meta-sanctioned business account |
| Setup time | Minutes | Days, plus Meta review |
| Meta account required | No | Yes |
| Official support | No | Yes |
| Phone must be opened every 14 days | Yes | No |
| Can be disconnected by WhatsApp | Yes, at any time | No |
| Message fees | None from Meta | Billed by Meta to your own account |
| Daily limit before Meta verifies you | None | 250 conversations the business starts |

## The bridge route

A bridge links a number you already use by scanning a QR code, the same mechanism WhatsApp Web uses when you pair a laptop. The phone that owns the number stays the owner; the bridge is registered as another linked device.

**What it gets you.** It works today, in any country, with no Meta account, no business verification and no application to file. Nothing to wait for. If you already run support from a WhatsApp number on someone’s phone, this is the shortest path from that to an assistant answering on it.

**What it costs you.** It is unofficial. WhatsApp can unlink the device at any time, and does, not as punishment, just as a consequence of how linked devices are managed. The phone does not need to stay on, but it does need to be opened at least once every 14 days. If it sits unused for longer, WhatsApp logs the device out and you pair again with a new QR code.

**When it is the right answer.** Smaller operations, and any situation where you need to find out whether WhatsApp support is worth doing before investing in the official route. It is genuinely fine for that. Treat it as a channel you could lose on a Tuesday and you will not be caught out.

## The official Business API route

The official route runs through Meta. You sign in, choose or create your business and WhatsApp Business account, verify the number, and pick the display name customers see.

**What it gets you.** A channel Meta knows about and does not spontaneously disconnect. Your WhatsApp Business account stays yours, inside your own Meta business, not held by a vendor on your behalf, which matters the day you change vendors.

**What it costs you.** Time, and a relationship with Meta’s billing. Meta bills message fees to the card on your own account, so your chatbot vendor is not in the middle of that payment, good for transparency, one more thing to set up.

There is also a limit worth planning around: until Meta verifies your business, you can start only 250 conversations a day yourself. Conversations your customers start are the ones support mostly deals with, so this bites less than it first appears, but if you send proactive order updates, it is the number that will surprise you.

**When it is the right answer.** When WhatsApp is a channel the business cannot afford to lose. If the answer to “what happens if this number stops working for two days” is anything worse than mild inconvenience, take the official route.

## Switching between them

In ProxyAI the two routes are separate cards under **Configurations → Channels**: **WhatsApp (Bridge)** and **WhatsApp (Meta)**. Your bot’s instructions, documents and handover rules are set up on the bot, separately from its channels, so they do not change when you connect a different route. On the Meta route you still connect and manage WhatsApp from ProxyAI: the card is just a different way in, using your own WhatsApp Business account, and the bot answers exactly as it did before.

## What this does not change

Everything above is just how messages get in and out. What the assistant says, what it knows, when it hands over to a person, and what it costs per answer are the same questions on either route. Pick the route based on how much risk you can live with, and spend your actual attention on the answers.

The step-by-step for both routes is in the [WhatsApp Connection Guide](/help/integrations/whatsapp-connection), and the [WhatsApp integration page](/services/channels/whatsapp) summarises what connecting involves.

## FAQ

### Do I need the WhatsApp Business API to use an AI chatbot on WhatsApp?

No. A bridge links a number you already use by scanning a QR code, the same way [WhatsApp](/services/channels/whatsapp) Web pairs a laptop, and works in any country with no Meta account. It is unofficial, so WhatsApp can unlink the device at any time, and the phone that owns the number must be opened at least once every 14 days.

### What is the difference between a WhatsApp bridge and the official Business API?

A bridge registers as a linked device on an existing number and can be disconnected by WhatsApp without notice. The official Business API is a Meta-sanctioned connection that is not spontaneously disconnected, keeps your WhatsApp Business account inside your own Meta business, and bills message fees to your own card.

### How many WhatsApp messages can an unverified business send per day?

Until Meta verifies your business, you can start only 250 conversations a day yourself. Conversations your customers start, which is most of support, are not counted. Completing Meta’s business verification lifts the limit.

### Who pays WhatsApp message fees?

On the official route Meta bills message fees directly to the card on your own WhatsApp Business account, so your chatbot vendor is not in the middle of that payment. The bridge route has no Meta message fees because it is not going through Meta.

### When should I migrate from a WhatsApp bridge to the official API?

When losing the number for two days would be worse than mildly inconvenient. Set that threshold in advance, a share of total contacts, or a revenue figure, and migrate when you cross it, rather than when the link drops during a sale.

### Will I lose my chatbot setup if I switch WhatsApp routes?

No. In ProxyAI, instructions, documents and handover rules are set up on the bot, separately from its channels, so they stay the same when you connect a different WhatsApp route.
