Official Cloud API connection
Connect through Meta's official onboarding and Meta Embedded Signup. Greenbubble does not depend on scanning a QR code or keeping a device session active.
Meta's browser view explained — and why business messaging at team scale runs on the official WhatsApp Business Cloud API, with a shared inbox instead of QR or device sessions.
At a glance
What you get
Connect through Meta's official onboarding and Meta Embedded Signup. Greenbubble does not depend on scanning a QR code or keeping a device session active.
An entire team works the same WhatsApp number with roles, assignments, and SLAs — not a single-account browser view.
Decide who sees what and who can do what, and prove who said what with a timestamped audit trail.
WhatsApp sits alongside Instagram, Facebook Messenger, Telegram, web chat, and Click-to-WhatsApp Ads.
Templates, bulk sends, branching flows, and MCP-native AI agents that draft replies and act with approval.
Signed outbound webhooks and an open REST API across contacts, conversations, templates, and analytics.
How it works
Complete Meta Embedded Signup and link your WhatsApp Business number to Greenbubble.
Add agents and set roles — admin, agent, viewer, or billing-only.
Use round-robin, load-balanced, or skill-based assignment with SLA timers.
Bring Instagram, Facebook, Telegram, web chat, and Click-to-WhatsApp Ads into the same inbox.
Deep dive
Most teams reach a point where a browser tab and a personal phone stop being enough. This page explains how WhatsApp works for a business team at scale — through the official WhatsApp Business Cloud API — and what a shared inbox adds.
If you have searched for "WhatsApp Web", you have met the consumer feature: a browser view that mirrors a phone account. That model was built for one person and one device. It is not how business messaging is meant to run at scale.
Business WhatsApp connects through the official WhatsApp Business Cloud API. You link your business number through Meta's official onboarding flow and Meta Embedded Signup, and from then on messages are delivered by Meta to your platform's endpoint. There is no phone that has to stay awake, no browser tab that can drop, and no per-device ceiling. Greenbubble does not depend on QR scanning or a linked phone session to keep your connection active — the API is the connection.
That single architectural choice is what makes everything else on this page possible: multiple agents, automation, analytics, and multi-channel.
| Layer | How it works |
|---|---|
| Message transport | Official WhatsApp Business Cloud API via Meta |
| Number ownership | Your Meta Business Manager, not the vendor |
| Agent workspace | Greenbubble shared inbox |
| Channels | WhatsApp, Instagram, Facebook Messenger, Telegram, web chat |
| Automation | Greenbubble flows, MCP-native AI agents, webhooks |
Connecting the API gives you transport. Greenbubble gives your team a place to work:
| Capability | Browser/device workflow | Greenbubble shared inbox |
|---|---|---|
| Message transport | Mirrors a single account | Official Cloud API |
| Simultaneous agents | Limited | Unlimited, with roles |
| Assignments and round-robin | No | Yes |
| Internal notes | No | Yes |
| SLA tracking and reporting | No | Yes |
| Templates and bulk sends | No | Yes |
| Multi-channel (Instagram, FB, Telegram, web chat) | No | Yes |
| Audit log | No | Yes |
| CRM hooks | No | Yes |
When work happens through a single mirrored account, there is no way to hide a conversation from an agent, restrict who can export a contact, or prove who sent a message. For a two-person team that is tolerable. For a ten-person team with contractors, it is a problem. The moment you need to answer "who handled this and what did they promise?", a mirrored session has no answer. A shared inbox does.
If you answer yes to any of these, a device-mirroring workflow has stopped fitting:
The move is light: connect your number to Greenbubble through Meta Embedded Signup, keep your existing phone number, and let your team work from the browser. Your customers notice nothing.
Your phone number, your customers, your business profile, and the green badge. The switch is invisible to customers, which is the point.
Removing the device ceiling is the headline, but the daily wins are subtler. An agent starts the day with a queue instead of a phone. They can see which conversations are unassigned, which are breaching SLA, and which have a note from a colleague. They can hand a conversation to a specialist without asking the customer to repeat themselves. Managers can pull a report instead of sampling by memory. None of this is exotic; all of it is missing from a mirrored single-account workflow.
Meta also offers a desktop client. It behaves like the browser view and is fine for a solo operator. It is still a window onto one account, so it does not solve the team problem. For teams, the API plus a shared inbox is the model that scales.
Through the official WhatsApp Business Cloud API, using Meta's official onboarding flow and Meta Embedded Signup. Greenbubble does not depend on scanning a QR code from a phone or keeping a device session active.
WhatsApp Web is Meta's consumer feature that mirrors a phone account in a browser. It was designed for one person. It is separate from the WhatsApp Business Cloud API that powers business messaging at scale.
Yes. With the API and a shared inbox like Greenbubble, an unlimited number of agents work the same number with role-based access, assignments, and a full audit log.
No. With the Cloud API, Meta delivers messages to your platform's endpoint. There is no phone that has to remain online and no session that can drop.
Messages are encrypted in transit and the Cloud API is Meta's official, policy-compliant channel. On top of that, Greenbubble adds role-based access, audit logs, and configurable retention for governance.
Yes. The API supports approved templates and bulk campaigns. Greenbubble's bulk sender adds opt-in handling, segmentation, and rate-limit pacing.
Yes. Greenbubble unifies WhatsApp, Instagram, Facebook Messenger, Telegram, and website chat in one inbox, so an agent never switches tools when a customer does.
You can begin with a trial of Greenbubble and connect through Meta's official onboarding. Meta charges per-conversation fees, which Greenbubble passes through at cost.
Start free trial → · See the shared inbox → · Compare Wati vs Greenbubble →
FAQ
Through the official WhatsApp Business Cloud API, using Meta's official onboarding flow and Meta Embedded Signup. Greenbubble does not depend on scanning a QR code from a phone or keeping a device session active.
It is Meta's browser view that mirrors a WhatsApp Business account from a phone. It is built for one person, and it is separate from the WhatsApp Business Cloud API that powers business messaging at scale.
Yes. With the official Cloud API and a shared inbox, an unlimited number of agents work the same WhatsApp number with roles, assignments, and a full audit log.
No. With the Cloud API, Meta delivers messages to your platform's endpoint. There is no phone that has to remain online and no session that can drop.
You can begin with a trial of Greenbubble and connect through Meta's official onboarding. Meta charges per-conversation fees, which Greenbubble passes through at cost.
Keep reading
Connect the official way
Unlimited agents, roles, SLAs, and an audit log — over the official Cloud API, on the same WhatsApp number.