ConnectWiz WhatsApp QR

Intermediate channel

Start on WhatsApp today. Go official when you’re ready. Lose nothing in between.

The official Business API needs verification most businesses don’t have on day one. The QR bridge is the honest middle path: scan a code, keep answering your customers — with your entire history imported — and migrate to the official API whenever you’re ready, conversations intact.

Full history rescue Number protection built in Migrate anytime, both ways
History crossing the bridge
Paired in 2 min
2024 · kitchen photos
2025 · quote thread
Imported silently — no AI wake-ups
Migrate to the official API anytime — nothing lost
2 min
To connect — scan a QR like WhatsApp Web, and the inbox starts filling
10 yrs
How deep the history import can reach — your years of conversations, kept
4
Guardrail families protecting your number — cold-outreach block, warm-up, pacing, ceilings
0
Conversations lost at migration — history lives in your database, not in the connection method

Getting on

A QR scan — and your number has a team behind it

Pair like WhatsApp Web

Scan the code with the phone that owns the number — the same gesture as linking a browser. No Meta business verification, no waiting queue, no templates required to simply answer your customers.

The full inbox treatment

Routing, assignment, notes, tags, Wiz AI answers and the mobile agent app — a QR-connected number gets the same operational machinery as every official channel.

A bridge, not a dead end

This channel exists to get you to the official Business API without losing your customer relationships on the way — and it’s safe to stand on for as long as the crossing takes.

History rescue

Your years of WhatsApp are an asset. We import them like one.

Most tools start your "customer history" the day you install them. The QR bridge requests WhatsApp’s deep history sync and carries your past with you.

Abstract 3D illustration: an abstract mosaic tile beaming a stream of message cards across a glass bridge toward an emerald shield

The deep sync

Pairing requests full history — the same mode WhatsApp Desktop uses — reaching back years and gigabytes, streamed in batches until it’s all in.

Original timestamps

Imported messages keep their real dates — last March’s conversation files under last March, and the customer record reads like the relationship actually happened.

Silent by design

History lands without waking anything: no AI replies fired at three-year-old questions, no notifications, no broadcast triggers, no usage billing. An import is an import, not an incident.

History becomes CRM

Every imported thread ties to a contact — so the moment you connect, your "new" CRM already knows who your regulars are.

Number protection

The guardrails that keep a QR number alive

QR-connected numbers get banned for specific, known behaviors. ConnectWiz blocks those behaviors at the platform level — protection you can tighten, loosen per channel, but never accidentally forget.

No cold outreach

First messages to numbers that never wrote to you are blocked — the single fastest way to lose a QR number, made structurally impossible by default.

Warm-up after pairing

A freshly paired (or re-paired) number sends gently for its first stretch — sudden full-volume sending right after connect is exactly what detection systems look for.

Pacing & ceilings

Minimum gaps between sends and hourly outbound caps keep the number’s behavior human-shaped — enforced by the queue, not by hoping agents remember.

No bulk number-checking

Mass "is this number on WhatsApp?" lookups — the classic list-cleaning move that gets accounts flagged — are throttled at the platform level.

Migration

When you’re ready for official: one move, nothing lost

Re-bind, don’t restart

Migration re-binds your conversations to the official Cloud API channel — the next reply leaves through the official sender, and every past message stays on the same customer record. Meta’s side may lose history at the switch; yours doesn’t, because it lives in your database.

Both directions, plus Coexistence

QR to Cloud, Cloud to QR, and Meta’s Coexistence mode all work — because the connection method is a property of the channel, not of your customer relationships.

The one manual rule

The same number can’t live on the consumer app and the Cloud API at once — switching sides is a deliberate step you take, and the migration dialog walks you through it honestly.

The honest fine print

What the QR bridge is not — in writing

Not official

The bridge speaks the WhatsApp Web protocol and is not a Meta-supported product. That’s the same for every QR tool on the market — we’re the one that says it above the fold.

Not risk-free

Ban risk exists and no vendor can wave it away. What we can do — and did — is make the risky behaviors structurally hard and the safe path the default one.

Not for broadcasts

Marketing campaigns belong on the official API with its templates and quality system. The QR bridge is for conversations — the guardrails enforce that on purpose.

Not the destination

Usable indefinitely if the rules are followed — but the destination is the official Business API, and this channel’s proudest feature is how little you lose crossing over.

WhatsApp QR FAQ

Straight answers

More in the full FAQ, or ask us directly.

No — and we say so in the first paragraph, not the footnotes. The QR bridge speaks the WhatsApp Web protocol, the same one your browser uses, and it is not Meta-supported. Used carelessly it carries ban risk; used within the guardrails ConnectWiz enforces, businesses run it safely as their bridge to the official Business API.

They come with you. Pairing requests WhatsApp’s full history sync — the deep one, up to years of conversations — and imports it silently: original timestamps kept, no AI replies fired at old customers, no notifications, no usage billing. Your inbox starts with your history, not from zero.

One action re-binds your conversations to a Cloud API channel, so the next reply leaves through the official sender while every past message stays on the same customer record. It also works in the other direction, and alongside Meta’s Coexistence mode. One manual rule applies: the same number can’t be live on the consumer app and the Cloud API simultaneously.

A set of enforced guardrails that keep a QR-connected number out of trouble: no cold first-messages to strangers, a warm-up period after pairing, minimum gaps between sends, hourly ceilings, and a throttle that blocks bulk number-checking — the exact behaviors that get QR accounts banned. Defaults are platform-set and tunable per channel.

Your customers are on WhatsApp today. So is your history.

Bridge now, go official when you’re ready — and carry everything with you.