QR vs Coexistence vs WABA — pick the right WhatsApp transport for your sales stack

---

Overview

How do the three transports compare at a glance?

Two layers, two tables. The first table is what Meta's API technically allows for each transport — that's the ceiling, the same for every app in the ecosystem. The second table is what TimelinesAI ships today on top of those transports — that's your reality if you use us. They are different questions, and conflating them is how most of these comparison articles mislead readers.

What Meta's API technically allows

^{¹ WABA does have a Groups API in restricted beta for very large customers with heavy approval requirements. Not practically available for most teams. ² Group history, view-once, disappearing, and live-location messages are not included in the backfill. ³ Meta doesn't publish exact anti-spam thresholds. Operationally what we see: a 12-hour freeze becomes likely around 10+ unanswered new chats per day, and account bans become likely after 20–30 templated mass messages from a personal number. The late-2025 anti-spam rollout also added monthly caps on messages to non-saved contacts. ⁴ The protocol is Meta-sanctioned. Third-party libraries our category uses to script that protocol for automation (TimelinesAI's own infrastructure included) sit outside Meta's blessed BSP list.}

What a typical app on a major CRM marketplace ships today

---

The three transports

When should you pick QR-linked devices?

Pick QR when the features your reps depend on live in the WhatsApp app itself — groups, calls, the desktop client — and your CRM has to see what they do there.

• You have group chats in the workflow. Solar installers run a group chat per install — homeowner, foreman, electrician, inspector. Korean clinics coordinate staff in group threads (one of the most consistent vertical-specific requests we hear). Travel agencies share booking details in a group with the tour supplier. Coexistence does not sync group chats into the API; they stay on the Business App. If groups matter to your team, QR is the only path that brings them into your CRM and shared inbox.
• You run WhatsApp calls as a sales tool. Voice and video calls — and call recording — work on the personal app and the desktop client. Calls under Coexistence ring on the rep's phone but don't reach your CRM. (WABA can now do voice calls via Meta's Cloud API Calling, GA since July 2025, but it needs BSP integration and most CRM-sync apps don't expose it yet.) I have seen reps qualify and close on WhatsApp voice in markets where WhatsApp is the main channel — Turkey, the Gulf, parts of LatAm — though it varies by buyer, not by country.
• Reps work on the WhatsApp Windows desktop client. Coexistence supports WhatsApp Web and WhatsApp for Mac, but not Windows desktop and not WearOS. A message a rep sends from Windows under Coexistence won't reach your CRM.
• More than one person needs to see a thread. Sales engineer pulled into a deal, manager looped in for a discount, finance answering an invoice question. On QR each of them can see the same thread on their own linked device. Coexistence is 1-to-1 on the API side; a second person can't join.

Use QR to bring rep numbers into the CRM. It is the base layer almost every team starts with.

---

When should you pick WhatsApp Coexistence?

Pick Coexistence on top of QR — not instead of QR — when one of these is true.

• You want past chat history in the CRM on day one. When Coexistence is enabled on a number, Meta backfills the last six months of one-to-one chats into the Cloud API as a one-time event. Group history, view-once messages, disappearing messages, and live-location are not included. QR has no equivalent Meta backfill — Linked Devices only streams new messages going forward. (Some QR-extension apps replay whatever sits in the local WhatsApp Web cache, usually a few weeks of recent chats, but it is not the same as the six-month Meta backfill.)

• You want a verified badge on a rep's number. Two badges exist, and they are not the same:

  • The free Official Business Account (OBA, blue tick — renamed from green in Meta's 2025 unified branding) is only available on full WABA numbers.
  • The paid Meta Verified for Business subscription is available on both Coexistence and WABA.

  QR-linked personal numbers cannot get either. If your buyer treats the badge as a trust signal, Coexistence with a Meta Verified subscription is the only path that keeps the rep's actual number.

• You want to broadcast from the rep's own number. This is the new value Coexistence actually brings, and the reason teams adopt it. When a rep sends a large templated follow-up from a regular QR-linked personal number, WhatsApp's anti-spam system tends to freeze the number first and ban it shortly after. (See footnote 3 in the table above for the operational thresholds we see.) On a Coexistence number, the same broadcast goes out through the official Cloud API template path. The rep stays connected on their Business App, and the customer still sees a message from the rep they know — not from a no-name marketing alias.

  One caveat: under Coexistence, the Business App's own broadcast-list feature becomes read-only. Broadcasts have to go through the Cloud API.

  For large multi-rep teams — Turkish dealerships, clinics, real-estate operators in the Gulf — where reps send templated follow-ups in bulk from personal numbers every week, this is the single biggest risk Coexistence removes.

• You want to qualify leads with WhatsApp Flows. Flows are Meta's in-chat multi-screen mini-forms (lead intake, booking, qualification questionnaire). They ride on top of the template message path on the Cloud API side, so any Coexistence or WABA number can launch them. QR-linked numbers cannot.

• You need the "official integration" answer when procurement asks. Coexistence is registered through Meta's official onboarding into the Cloud API. It's a Meta-sanctioned business path. QR-linked Devices is Meta-sanctioned too at the protocol level — it's the same multi-device feature your laptop uses for WhatsApp Web — but the third-party libraries our category uses to script that protocol (ours included) are not on Meta's official BSP list. In practice, a competitor sales rep put it like this to me recently: the difference doesn't matter unless you're sending templated follow-ups in bulk. Bans on QR-linked numbers happen because of what the rep does, not because of the protocol. The compliance answer is real if procurement has "Meta-compliant integration?" on its checklist. For day-to-day rep operations the practical difference is small.

---

When should you pick the WhatsApp Business API?

Pick WABA, on a separate marketing number distinct from your rep numbers, when the use case is high-volume opt-in template marketing.

• Template campaigns to opted-in lists — sale announcement, delivery delay, appointment reminder, drip flow.
• You need throughput that personal numbers cannot safely reach. WABA starts at 80 messages per second by default and can scale to 1,000 MPS for upgraded accounts. QR-linked personal numbers are bound by WhatsApp's anti-spam enforcement — well below either of those numbers. (See footnote 3 in the table above for the operational thresholds we see in practice.)
• You need a dedicated marketing identity — Acme Bakery as the sender name on every campaign, not the personal number of an individual rep.
• You are running click-to-WhatsApp ads. Both WABA and Coexistence work as destinations for these ads, but WABA is the default for the high-volume marketing motion the ads usually feed.

WABA is the marketing-throughput layer. It does not replace QR or Coexistence on rep numbers — it sits next to them, on a different number.

---

Reality + caveats

Most teams end up running two of the three

The way a working WhatsApp sales stack actually looks in 2026:

1. QR-linked devices on each rep's number. This is what brings WhatsApp into the CRM — contact creation, deal linkage, message timeline, manager visibility, groups, calls, and the desktop app. It is the base layer almost every team starts with.
2. Coexistence layered on top of the same rep numbers. This adds rep-level broadcasting, the six-month backfill of past 1-to-1 chats, the paid Meta Verified for Business badge, and Flows for lead qualification. None of the QR features go away.
3. WABA on a separate marketing number. This carries push campaigns, template flows, and click-to-WhatsApp ad replies at template throughput.

A team running e-commerce or D2C with high-volume marketing usually has all three. A team running pure B2B sales with no marketing campaigns runs QR + Coexistence. A pure marketing-API setup with no reps and no CRM runs WABA alone.

The point to take away: QR and Coexistence are not competitors. They are layers on the same rep number. If a vendor sells you Coexistence as a "QR replacement," you are getting one of two things. Either you get only the 1-to-1 chat subset, with groups, calls, and desktop quietly out of scope. Or — more often — they are still running QR for the CRM integration and adding Coexistence on top for broadcasting. Either way, the right mental model is "add a layer," not "switch transports."

---

The Coexistence number limit nobody talks about

There is one Coexistence constraint worth knowing before onboarding, because it has cost teams the deal they were about to close.

Every Coexistence-enabled number registers as a Cloud API number on the Meta Business portfolio that owns it. Portfolios get two phone-number slots by default and up to twenty once the business is verified. So the practical cap is twenty Coexistence numbers per portfolio.

Meta's own Coexistence documentation does not state this cap explicitly. 360dialog's public Coexistence page says there is no stated limit. I heard the "twenty" figure first on a competitor sales call, then walked through the underlying portfolio limits with the BSP I work with. I believe it is real. If you have production experience that says otherwise, I want to hear.

For a team running twenty or fewer reps per portfolio, this never comes up. For a 50-rep clinic in Turkey or a 200-number real-estate operator in Dubai, it is a stopping point. The workaround is splitting numbers across multiple Meta Business portfolios, which is annoying to run.

---

A few things the Coexistence pitch leaves out

Vendor decks usually skip these. They should be on the table before you commit your team's plan to Coexistence-first.

• Coexistence does not cover groups, calls, or the Windows desktop client. This is the operational ceiling. If your reps live in groups, on WhatsApp calls, or on WhatsApp for Windows specifically, Coexistence-only loses those interactions. (WhatsApp Web and WhatsApp for Mac are fine.)
• The OBA badge does not transfer to Coexistence. The free blue tick is only available on full WABA numbers. Coexistence numbers can still get a verified badge — via the paid Meta Verified for Business subscription — but if "we want the free badge" is on the requirements list, Coexistence does not deliver it.
• Setting up Coexistence needs full admin permissions on the Meta Business portfolio and on the connected Facebook Page. For a small team where one person owns the Meta Business setup, that is fine. For a 30-rep org where IT does not have hands-on time, getting both permissions propagated for every number is the real implementation cost.
• Historical sync into a CRM is a separate problem from Coexistence itself. Meta backfills six months of 1-to-1 chats on connection. Most CRM integrations are not built to absorb fifty thousand messages arriving in minutes. (HubSpot's own native WhatsApp app on the marketplace is rated 2.2 stars partly for sync-depth complaints — even on the platform's own integration, this is hard.) If your vendor promises "Coexistence plus full historical CRM sync on day one," ask them to demo it on a real account with real volume.
• "Official ToS" is not a free pass. Coexistence numbers can still be flagged if the account is doing things Meta does not allow — mostly templated outreach to people who did not opt in. The compliance is in the connection, not in what the rep sends afterwards.
• A WABA-only marketing setup is not a substitute for CRM sync. WABA gives you template throughput, not a synced rep conversation history. If your motion needs both — most do — WABA alone is not the answer.

---

Verdict

Three questions to pick your transport

A quick way to choose for your team:

1. Do your reps run group chats or WhatsApp calls in their workflow? If yes, QR has to be there. Coexistence alone will lose those interactions.
2. Do you need rep-level broadcasting (templated follow-ups from the rep's own number), the six-month past-chat backfill, or a verified badge on rep numbers? If yes, layer Coexistence on top of QR for those numbers — on the same rep number, not as a replacement.
3. Are you running opt-in template marketing campaigns or click-to-WhatsApp ads at volume? If yes, add a WABA marketing number alongside, distinct from rep numbers.

Most B2B sales teams answer yes to 1 and 2, no to 3 — so they run QR + Coexistence with no marketing API. D2C and e-commerce teams answer yes to all three. Pure marketing setups answer yes only to 3. There is no version of this where one transport is the right pick for every job.

For the next layer of the same architectural choices, see Personal numbers vs WhatsApp Business API — pick personal if you sell and Personal vs company numbers — pick company. The cluster index is at /perspectives/topic/personal-numbers-privacy-waba/.