ConnectWiz for WhatsApp
Premium channelThe whole WhatsApp Business API. Not the brochure version.
Most platforms implement the demo: send a message, receive a message. ConnectWiz ships the entire surface — templates, Flows, catalogs, orders, groups, voice calls, cost analytics and the unglamorous ops layer that keeps a number healthy at scale. This page lists all of it.
Yes — the 6-piece set is in stock at $89. I can send the catalog card or reserve one for you. Which would you like?
Getting on
Two doors in. The number stays yours behind both.
ConnectWiz operates as a Meta Tech Provider: your WhatsApp Business Account, your number, your Meta billing. We connect software to it — we never sit between you and Meta.
Door one — embedded signup (Cloud API)
Meta’s official onboarding flow, clicked through inside ConnectWiz: create or link a WhatsApp Business Account, verify the number, set your payment method with Meta. Minutes, not tickets. This is the front door — full template, Flow, catalog and calling capability from day one.
Door two — QR link for existing numbers
A number already living on the WhatsApp app, with years of history you can’t lose? Scan a QR code and it bridges into ConnectWiz — chat history synced — while you keep using it. Migrate to the Cloud API whenever you’re ready.
Migration, any direction
QR → Cloud, Cloud → QR, between numbers in the same family — one transfer flow, direction-agnostic, with conversation history carried and the next reply always leaving from the right sender.
Twin protection
The same number can never run live on two channels at once — matched digit-by-digit, not string-by-string, so +90 532… and 90532… can’t sneak past as different numbers and split one customer into two conversations.
Start fresh — without burning the past
Migrating to escape years of messy history? Choose a clean inbox: old conversations are archived, never deleted. A tidy queue for the team, intact records for you.
Inbox & AI
One number. A whole team. An AI that knows the rules.
Team inbox, properly
Routing by department and workload, assignment, internal notes with @mentions, supervisor view, full history — on desktop and the native mobile app. The one-phone-in-a-drawer era ends here.
Wiz, window-aware
Your AI agent answers from your own content in 52 languages, books appointments and escalates with context. It also collects rapid-fire customer messages into one reply — better conversations, fewer billable messages.
Interactive replies
Reply buttons, list messages with sections and rows, labeled CTA-URL buttons instead of naked links, and WhatsApp’s native "share location" request — composed from the panel, validated before Meta ever sees them.
Every media type, handled
Images, videos, documents, stickers, reactions, locations, quoted replies and link previews — with download integrity verified, transient failures retried, and attachments stored on your records before Meta’s 7-day links expire.
Edits & deletes, honestly
Customers edit and delete their WhatsApp messages — ConnectWiz shows an edited flag and renders deleted messages as "this message was deleted", so agents never reason about a conversation that silently changed under them.
Ticks you can trust
Delivery and read receipts follow Meta’s real semantics — a late failure never erases a confirmed read, and delivery errors are recorded alongside the message instead of overwriting its state.
WhatsApp groups
Group messages land in the group’s own conversation with per-participant attribution, membership tracked in a group ledger and failed member operations reported honestly. AI stays off in groups until you switch it on — per group.
Security signals surfaced
When a customer taps "I didn’t request this code", it’s flagged as a possible account-takeover signal — a red warning on the conversation plus an alert, never mistaken for a routine button reply.
Contact cards & usernames
Send rich contact cards with the WhatsApp identity filled in server-side, and stay reachable as WhatsApp rolls out usernames — username-adopting customers resolve to the same contact, not a mystery sender.
Voice, done properly
Agent voice notes go out as real WhatsApp voice messages (converted server-side, not generic audio files), incoming voice is transcribed to searchable text, and the "played" blue-microphone moment is tracked as its own status.
Media that always lands
Outbound files are normalized to what WhatsApp actually accepts — iPhone HEVC video re-encoded, exotic image formats flattened — so "unsupported media" errors get fixed by the platform, not by your customer.
Forwarded ≠ asked
Forwarded messages are labeled — and "forwarded many times" chain content automatically suppresses the AI reply, so Wiz doesn’t spend your credits answering a viral meme. Number and identity changes follow the customer to the same contact record.
Templates & broadcasts
Outbound at scale — with brakes engineered in
Everything from writing a template to watching Meta’s verdict on it, without leaving the panel — and campaign machinery that treats opt-outs and country rules as physics, not paperwork.
The template studio
- Create and submit from the panel — body, header, footer, buttons; Meta’s two absolute rules caught in the editor, not minutes later as an API error
- Named parameters —
{{discount_code}}instead of{{1}}, so the send screen reads like language, not algebra - Meta’s real language catalog — regional variants like
pt_BR/pt_PTincluded, invalid codes impossible to submit - Multi-language variants & preview — see the message as the customer will, per language, before submission
- Every button family Meta supports — coupon copy-codes, URL-variable buttons, Android deep links, location headers, OTP autofill and call-permission components, validated in the editor rather than rejected by the API
- Meta’s traps, explained in place — category upgrades that change your bill, the 10-edits-per-30-days quota, the 30-day name lock on deletes — surfaced before they cost you
- Message TTL control — expire time-sensitive sends instead of delivering yesterday’s flash sale tomorrow
- Full lifecycle webhooks — approval status, category changes, quality updates and pacing signals (including "held for quality assessment") land in the panel as they happen
Stop means stop
WhatsApp-level marketing opt-outs and stop signals write straight into the consent ledger and filter every future campaign — including the one currently sending.
Per-user limits respected
When Meta says a recipient hit their personal marketing ceiling, ConnectWiz backs off with a 24-hour cooldown instead of burning retries against a wall.
Direct Send utility
Template-free service messages outside the window — a per-channel opt-in with content checks and an automatic kill-switch, for the "your order shipped" moments that shouldn’t need a template review.
Template analytics
Per-template sent, delivered, read and button-click counts — behind an explicit consent screen, because Meta’s insights switch is one-way and you deserve to know that before flipping it.
Paused template = paused campaign
If Meta pauses a template mid-campaign, the campaign halts instead of burning thousands of one-by-one rejections — with Meta’s escalation ladder explained on the campaign row.
Free windows, badged
Conversations that open from a free entry point (like a Click-to-WhatsApp ad) carry a 72-hour free badge derived from Meta’s own pricing verdict — never guessed, because a wrong "free" creates a bill.
Commerce
From "is this in stock?" to a paid order — inside the chat
WhatsApp is a storefront in every market where it’s the default messenger. ConnectWiz ships the full commerce surface, and turns the raw API responses into things a salesperson can actually read.
- Catalog & cart visibility controlled per number, from the panel
- Single- and multi-product messages, product carousels, catalog templates — created and sent without JSON
- Incoming carts become readable order cards — product names resolved from your catalog (not SKU codes), totals computed per currency, customer note attached
- An order ledger per conversation — what was asked, offered and bought stays on the record
- Click-to-WhatsApp ads carry their referral context into the chat, and Meta’s automatic purchase/lead conversion events are captured for attribution
- Products come from ConnectWiz’s built-in catalog (or synced from WooCommerce) — and the platform generates the product feed Meta Commerce Manager ingests, no App Review required
WhatsApp Flows
Native in-chat forms — from one-click to fully custom
Flows are WhatsApp’s own multi-screen forms: bookings, applications, surveys — completed without leaving the chat. Most platforms make you build them in Meta’s separate tool. ConnectWiz ships them ready, and runs the hard mode too.
Four forms, one click
Appointment booking, order tracking, quote request and satisfaction survey — installed and published in a single step, in the language you choose. Personal fields are marked sensitive by default so answers don’t sit as plain text in chat summaries. No Meta Flow Builder account, no separate tool, no JSON.
Endpoint Flows for the ambitious
Dynamic Flows backed by a live data endpoint: encryption with per-WABA keys and overlap-free rotation, Meta’s data-exchange protocol v4.0, encrypted media, screen navigation — the infrastructure most vendors call "roadmap" is running here.
Flow health, watched
Meta’s four error buckets tracked per Flow with honest sample-size handling — eleven requests don’t get dressed up as a verdict. Problems reach you before customers do.
Blocked? You’ll know first.
When Meta throttles or blocks a Flow, it’s a badge in your picker and a critical alert — never a silently vanished form. Recovery follows Meta’s real ladder: blocked → throttled → published.
Answers become data
Flow responses attribute back to the exact Flow that produced them, multi-select answers are summarized readably, and uploaded files are downloaded server-side into real, validated attachments.
WhatsApp Calling
The call button on your profile — answered like a call center
Customers tap to call your WhatsApp number; your team answers in the browser or the mobile app. Behind it: the same call engine as our PSTN and Messenger lines.
- Inbound and outbound calls with IVR and business-hours greetings
- Hold, resume and consultative transfer — server-authoritative, with live captions during the call
- Recording, policy-aware with announcements; searchable transcripts stored on the conversation, language detected
- Call-permission requests done right: free-form inside an open window, an approved permission template outside it — the server picks the path, in the customer’s language
- Permission state and quota read live from Meta — "pending" and "denied" are different answers, and agents see which one they have
- Voicemail on reject or timeout — a missed call becomes a message, played back inside the conversation
- A customer’s incoming call refreshes your service window — even if nobody picks up
- Ghost-ring protection: stale call webhooks can’t ring the whole team for a call that ended ten minutes ago
Reliability & ops
The features nobody demos — and everybody eventually needs
A WhatsApp number at scale is a living system: tokens expire, WABAs move, names change, quality tiers slip. ConnectWiz treats "the channel just works" as an engineered outcome, not a hope.
Channel health, by exception
Number status, name approval, verification and official-account state — synced from Meta and shown as a problem list. A healthy number shows nothing, so a shown row actually means something.
Quality & limits, side by side
Your messaging tier, quality rating and remaining capacity in one screen — answering the only question that matters: can tomorrow’s campaign actually send? Pacing follows these numbers automatically.
Daily token health
Validity, both expiry dates and granted scopes checked every day. If Meta invalidates credentials, the channel locks with a clear "reconnect" path — agents never learn about a dead token from failed sends.
WABA watchdog
A daily check that your number still lives in the WABA we think it does. If it moved, ConnectWiz rebinds, re-subscribes webhooks on the new WABA and keeps the old one in history — migrations stop being silent outages.
Errors that explain themselves
50+ Meta error codes mapped to plain-language causes and the right retry behavior — cooldown, never-retry, needs-action — translated into 52 languages, with Meta’s own documentation linked.
Name changes, survived
Display-name approval triggers the re-registration Meta quietly requires within 14 days — automatically, key re-upload included. A footnote in Meta’s docs that has silently killed numbers elsewhere.
QR & wa.me link manager
Create and label the QR codes and short links you print on menus and flyers — with a local label registry, because Meta doesn’t keep one and twenty unlabeled codes are twenty mysteries.
Ice breakers & commands
Manage conversation starters and command menus from the panel — including the warning nobody else gives you: prefilled wa.me links hide ice breakers, and ConnectWiz tells you when you’re stacking the two.
Official Business Account
Apply for the OBA badge and manage search visibility and username discoverability from ConnectWiz — with the minimum-requirements check done before you burn an application.
Blocking that reaches Meta
Block abusive senders at Meta’s level, not just locally — partial failures logged honestly, local blocks never corrupted by a Graph hiccup.
30 webhook signals, zero dropped
Account events, quality updates, capability changes, pricing-tier moves, flow status, security events — 30 fields subscribed with named readers, audited so a subscribed field nobody reads can’t exist, and unknown events logged rather than discarded.
Self-diagnosis built in
A read-only diagnostic verifies subscriptions, webhook overrides and system-user assignments against Meta’s live answers — so "is the channel healthy?" is a command, not an archaeology project.
Business profile, from the panel
Description, address, website, hours and profile photo edited in ConnectWiz — with Meta’s full industry list, including the sectors most platforms forget to offer.
Number blips, absorbed
When a linked phone re-registers and the number drops offline for a few minutes, queued messages wait instead of failing — no burned retries, no error-flooded agents, delivery resumes on reconnect.
Premium channel
What WhatsApp costs — both bills, no fog
WhatsApp is a premium channel with usage fees. There are exactly two bills, they come from two different companies, and here is each one in plain terms.
Bill one — ConnectWiz (the platform)
Flat and predictable. The channel itself:
- Business plan: WhatsApp included
- Pro plan: a channel pick or +$19/month add-on — included on Business
- Free & Starter: not available — premium channels start at Pro
- Per-message fee from us: $0. No markup, no template surcharge, no percentage of your Meta bill — ever
Bill two — Meta (the usage)
Billed by Meta, directly to your payment method, at Meta’s published rates. In broad strokes under current pricing:
| Message type | Typical case | Meta’s fee |
|---|---|---|
| Service replies | Customer messages you; you reply within the 24-hour window | Free |
| Utility templates | Order updates, reminders — sent inside an open service window | Free |
| Everything, 72h | Conversation starts from a Click-to-WhatsApp ad or Facebook CTA and you reply within 24h — all messages, templates included | Free |
| Utility templates | Same messages, sent outside the window | Per message* |
| Marketing templates | Promotions, offers, re-engagement | Per message* |
| Authentication | One-time passcodes | Per message* |
* Rates vary by template category and the recipient’s country code, and you’re charged only when a template is actually delivered. Meta changes rates at most quarterly (with 1–6 months' notice) — their rate card is the source of truth, not this table. WhatsApp calling has its own separate Meta pricing, also billed directly to you.
And you can watch bill two from inside ConnectWiz
The Usage & Cost screen pulls Meta’s own conversation and pricing analytics into the panel — cost by category, direction and message type — so "what did WhatsApp cost this month?" is a glance, not a WhatsApp Manager expedition. Campaigns show a billable-count preview before sending, broadcast reports carry a separate line for messages Meta didn’t charge, and conversations opened from free entry points wear a 72-hour free badge.
Sending at scale? Meta’s rates come down — and you’ll see it happen
Utility and authentication messages have volume tiers: the more you deliver to a market in a month, the lower Meta’s per-message rate for that market — counted across your whole business portfolio, reset monthly. When your account crosses into a cheaper tier, Meta’s tier-change signal lands in your channel timeline like every other pricing event — you learn about the discount from the panel, not from the invoice.
You just read the whole API.
Connecting it takes minutes.
Embedded signup or QR — your number, your WABA, zero markup. Everything on this page is live in the product today.