One Physical Device
Shifts hand over a single phone. Customers wait while someone «picks up» WhatsApp.
WhatsApp Cloud API
One Corporate Number. Not One Shared Smartphone for the Team
Customers message on WhatsApp because it's convenient. When the channel runs on personal phones, threads get mixed up, numbers get banned, and client history leaves when reps resign. volbor connects the official Cloud API: your entire team collaborates in one shared inbox, the bot automates routine queries, and deals live in CRM rather than a salesperson's personal chat.
Gray Channels
QR Scanners and Emulators Don't Scale — They Get Numbers Banned
Unofficial scripts promise «messaging just like personal chat». That is not how Meta operates. An unrecoverable number ban costs far more than any SaaS builder.
Siloed Chat History
A sales rep quits — your chat history leaves with them. Reconstructing your CRM later is impossible.
Gray Mass Blasts
Emulators trip anti-spam limits instantly. Official Meta outbound broadcast templates are covered on our campaigns page.
Cloud API
Official Gateway. Green Verification Badge Upon Meta Approval
Connect your phone number via Meta Business Manager, not by scanning a phone app QR code. Route multiple queues on a single WABA account. Message limits and templates are managed directly by Meta, not through fragile «gray bridges».
You can migrate an existing phone number by releasing it from standard WhatsApp, or register a fresh dedicated business number.
24 Hours
Free-Form Messaging Inside the Window. Approved Templates Outside
A 24-hour service window opens with each inbound message from a customer: your bot and human reps reply with free-form text just like standard chat.[1] To initiate a conversation outside that window, you must use a pre-approved Meta message template.
Inside Window
Interactive buttons, catalog, free-form text
Outside Window
Pre-approved Meta templates only
Native Messages
Buttons and Lists — Never «Type 1 or 2 to Continue»
Quick replies, list messages, and CTA links. These are native WhatsApp UI elements, not clunky web forms squeezed into chat. (Mini Apps live in Telegram, not this channel).
- Dimensions & Fabrics
- Calculate Shipping
- Check Stock
- Talk to a Specialist
Sofa in Chat
From Product Card to Checkout — Without Passing a Phone Around
Anna taps WhatsApp on the «Nordic» product card. The bot instantly detects the SKU. Next comes fabric selection, city entry, $45 carrier shipping calculation, payment link, and automated CRM stage update to «Paid».[2]
- SKU-aware greeting, not a generic «Hello how can I help».
- Interactive list: fabrics, shipping, inventory, human specialist.
- City input → live rate calculation via carrier API.
- Checkout. Deal advances without copy-pasting phone numbers into spreadsheets.
After-Hours & Escalation
The Bot Never Sleeps. Agents Join the Same Thread Seamlessly
After hours, the bot qualifies leads, takes orders, or shares opening hours for the morning shift. When a user taps «Talk to agent» or an unexpected edge case occurs, the conversation queues into Unified Inbox — not a disconnected new chat.
If your CRM is temporarily unreachable, events queue in an automated retry buffer and dispatch as soon as connectivity restores.
FAQ
Numbers, Teams, and Broadcasts
Can we keep our existing phone number?
Yes, by unlinking it from standard WhatsApp, or you can activate a new dedicated number.
How many reps can share a single phone number?
The Cloud API is not limited to a single physical device. Your entire team works simultaneously inside Unified Inbox.
What happens when a customer messages at night?
The bot handles inquiries 24/7. It can take orders or set expectations for when human reps come online in the morning.
Can we run mass marketing broadcasts?
Only through Meta-approved message templates with opt-out mechanisms. Mass blasting from a phone app is the fastest way to get banned.
How do customers reach a human agent?
Via an interactive button or fallback escalation. The conversation queues into Unified Inbox with full context preserved.
Ecosystem
WhatsApp Doesn't Live in a Vacuum
The Cloud API is your messaging pipe. Flows, shared inbox, and outbound templates live across interconnected volbor modules.
Chatbot Hub
Why You Need ItRun the same logic across Telegram and your website without a second builder.
Without ItAn isolated WhatsApp silo where customer context is lost upon channel switching.
Flow Builder
Why You Need ItBuild interactive buttons and list menus without engineering releases.
Without ItEvery single copy change becomes a development backlog ticket.
Unified Inbox
Why You Need ItMultiple agents collaborating simultaneously on one WABA number.
Without ItYour team is back to queuing up for a single physical phone.
Broadcasts
Why You Need ItSend outbound campaigns outside the 24h window using approved templates.
Without ItHomegrown mass blasts get your corporate WhatsApp number banned.
Deals & Pipelines
Why You Need ItCompleted payments advance pipeline stages automatically instead of sticky notes.
Without ItDeals and leads remain trapped inside WhatsApp chats.
Telegram Bot
Why You Need ItReach a different customer audience within the exact same workspace.
Without ItAnyone preferring Telegram over WhatsApp is completely ignored.
Get Started
Connect Cloud API and Launch an In-Chat Funnel on Your Product Pages
Meta phone verification, service window templates, and interactive chat flows. Stop running risky phone emulators «temporarily».
Open DashboardData & Methodology
Sources Behind the Numbers on This Page
- [1]24-hour service window starting from the customer's last message
Official WhatsApp Business Platform (Cloud API) policy: free-form session messaging is permitted inside the 24h window; outbound messaging outside the window requires pre-approved templates. This is channel policy, not a volbor metric.
- [2]Sofa purchase walkthrough completed in minutes, shipping calculated at $45 / 3 days
Illustrative workflow featured on this page: SKU detected from card, interactive list selection, carrier rate calculation at $45 / 3 days, checkout link, CRM stage progression. Not an average across all storefronts.