One queue. Two channels. Delivery you can audit.
Business messaging on the official WhatsApp Business API through a Meta-approved BSP — and person-to-person observation over Baileys. Staged, scheduled and delivered on Axion.
How Sphinx uses WhatsApp
Two channels, on purpose — because Meta’s rules make them different jobs.
What Meta requires before a number can send
Business-initiated WhatsApp is a regulated channel. Every one of these is Meta’s requirement, carried out through the BSP — Sphinx works within it, it does not shortcut it.
Meta Business verification
The business is verified in Meta Business Manager — legal name, website and identity confirmed by Meta.
WhatsApp Business Account
A WABA is created under the BSP (Twilio, Channel360, Infobip), linking the business to WhatsApp’s systems.
Number registered & named
A phone number is registered to the WABA with an approved display name. It cannot also run in the consumer WhatsApp app.
Message templates approved
Every business-initiated message uses a template pre-approved by Meta in a category — utility, marketing or authentication.
User opt-in
The recipient has opted in to hear from the business, captured and auditable, before the first message is sent.
Live — within the rules
The number sends, under an ongoing quality rating and messaging tier, priced per conversation. Break the rules and Meta throttles or blocks it.
The ongoing rules
24‑hour window
Free-form replies only within 24 hours of the user’s last message. Outside it, only an approved template may open the conversation.
Quality & tiers
Meta rates the number’s quality from how people react. Messaging limits scale in tiers — 1K, 10K, 100K, unlimited — and a poor rating drops them.
Conversation pricing
Meta bills per 24‑hour conversation by category, not per message — so campaign economics follow the template category.
Template categories
Utility, marketing and authentication each carry their own approval bar, pricing and opt-in expectation.
Policy compliance
The WhatsApp Business and Commerce policies bind every message — content, frequency and consent are all in scope.
Baileys stays observe‑only
None of the above applies to Baileys because Baileys never sends business traffic. It observes person-to-person conversations; a business line is provisioned through the BSP.
What Sphinx does around it
Outbound
Every message is staged before it sends. A drain pass claims the due batch, sends it, and settles each row as done or failed with the provider’s response attached. Scheduled sends can be cancelled until they leave.
Content
Plain text, or an approved template with ordered parameters, header artwork and call-to-action buttons. Media resolves at send time, so artwork can be generated per recipient.
Providers
Twilio, Channel360 and Infobip run off one queue and share credentials, session handling and retry. Switching provider — or running two — is configuration.
Inbound
Replies are captured and matched back to their conversation, keeping a campaign and its responses on one thread. Leads are scored and handed to an owner.
Reporting
Dashboards for traffic, events, WhatsApp callbacks and short-link activity, plus per-message delivery detail — from the records that did the work.
The rest of Axion
Workflow orchestration, scheduled jobs, forms, imports and exports, webhooks and line-of-business integration are already in the same deployment.
Sends through
- Meta
- Twilio
- Channel360
- Infobip