What BNex is
BNex is a single product that covers the four jobs a WhatsApp-driven business usually stitches together from separate tools: answering customers, managing contacts, running campaigns, and automating routine replies.
- Shared inbox — many agents on one WhatsApp number, with shared conversation visibility, internal notes and handover.
- Instagram text DMs — a connected Instagram professional account appears in the same inbox, with text replies and internal notes.
- Contacts and audiences — contact records, groups and segments you can target deliberately.
- Campaigns — scheduled broadcast to a saved audience segment, with delivery reporting and a per-campaign daily cap.
- Automation (paid plans) — trigger-based flows that handle acknowledgement and routing without a human.
- AI Copilot — an assistant inside the workspace that drafts replies and templates, explains Meta rules and pricing, and opens the right screen for the job. It never sends a message on its own.
- Template pre-flight — a draft is checked against Meta’s documented rejection causes before you submit it, and a campaign parked on template approval is released automatically the moment Meta approves the template.
- Message costs you can see — campaign estimates show the Meta rate for the audience before you send, and Meta bills that usage directly to the payment method on your WhatsApp Business Account. BNex adds no per-message charge of its own today.
Built on the official Cloud API, not a workaround
BNex sends through Meta’s official WhatsApp Cloud API. That means conversations run on your own verified business number and your own WhatsApp Business Account, under WhatsApp’s own rules and rate card — not through an unofficial library that automates a personal account.
The distinction matters commercially. Unofficial automation can get a number banned, offers no template approval path for reaching customers outside the service window, and cannot support the volume a real campaign needs. Building on the official API is slower to set up and considerably harder to lose.
Three decisions we made deliberately
- 1
One product instead of four integrations
Most stacks are an inbox, a CRM, a campaign tool and an automation builder held together by webhooks. Each seam is somewhere a message can be lost. BNex treats those as one surface so a conversation and its campaign history live in the same place.
- 2
Cost visible before a campaign runs
Messaging has a real per-message cost, so a campaign estimate shows the Meta rate for the audience before you send it. That number is not a BNex charge today: Meta bills the usage directly to the payment method on your WhatsApp Business Account, and planning against the real cost is what removes the end-of-month surprise.
- 3
Written for operators, not analysts
The people running WhatsApp at most companies are support and marketing staff, not engineers. The product is built so they can build a campaign or a flow without a developer in the loop for every change.
Where BNex fits, and where it does not
BNex fits businesses that have outgrown a single WhatsApp phone and need a real team inbox, repeat campaigns and automation on their own verified number. It is a poor fit for a business with one person answering messages, and for anyone looking for bulk messaging to lists that were never opted in.
| Your situation | Fit |
|---|---|
| One person answers WhatsApp from one phone | Not yet — the free WhatsApp Business App is simpler and costs nothing |
| Several agents share one number | Strong fit |
| You run repeat campaigns to opted-in customers | Strong fit |
| You need WhatsApp in your existing CRM via API | Strong fit — the platform is API-first |
| You want to message a purchased contact list | Wrong fit — this is against WhatsApp policy and we will not help with it |
| You want a general-purpose helpdesk across email and phone too | Consider a dedicated helpdesk with a WhatsApp channel |
Where the product is today
BNex is live and runs as a standalone Meta Tech Provider, not a Business Solution Provider, so the software is billed as a subscription while WhatsApp usage is billed by Meta to your own account. You can start self-serve: the entry plan is free for a single operator, with no credit card. The platform surface — inbox, contacts, campaigns, an AI Copilot, team permissions and API, with visual workflow automation on the paid plans — is built. What still depends on Meta is the WhatsApp connection itself: business verification, display-name review and template approvals, which is why onboarding walks a new workspace through them in order.
We would rather say that plainly than imply a maturity the product does not yet have. If you are evaluating WhatsApp platforms, ask every vendor the same three questions: is it on the official Cloud API, what happens at the 24-hour window boundary, and who is charged when a template is reclassified. The answers will separate the products quickly.
BNex is built by Ziync. If you want the engineering behind it, the honest answer is that the team that builds web platforms for other companies built this one for itself first.
Common questions
Platform rules and pricing on this page are Meta’s and can change. Meta updates WhatsApp pricing only on the first day of a quarter and gives advance notice, but always confirm current rates against Meta’s own documentation before committing a budget. This page was reviewed on 7 November 2026.
Related reading
Shared inbox setup
A WhatsApp shared inbox lets several agents answer one business number from a single view of the conversation, with internal notes and per-message read state — the hard part is not the software but agreeing who answers, who takes over, and when a conversation is finished.
API vs Business App
The WhatsApp Business App is a free phone-based app for a single operator with no API, while the WhatsApp Business Platform (often called the WhatsApp Business API) is a paid, multi-agent, programmable service built for teams, automation and broadcast at scale.