By industry
By team role
By company size
For teams choosing a specific module rather than "the whole platform"
Customer writes → flow or agent guides → Inbox and CRM record the step → broadcast or calendar slot only by rule. The header has a concise menu. Below is the full catalog, including TikTok, Mini Apps, voice, video widgets, inventory, and multicurrency.
Catalog
Eight clusters as in the header, plus voice and video—this hub isn’t in the megamenu. Don’t roll out everything at once: one entry point, one shift window, one action.
Knowledge base → draft or agent → API. Not an ungoverned public chat.
Branches, events, scoring. A strict step beats a script; natural conversation goes to the agent.
One flow, multiple entry points. Customers shouldn't repeat their order when switching channels.
Consent, segment, auto-stop on reply. Never a scraped list.
Contact, deal, task. Otherwise BANT lives only in chat.
Inspect your own numbers, not someone else’s "N companies".
SKUs, invoices, discounts. Plain text without stock levels turns back into a support ticket.
The shift sees the feed, permissions, and knowledge base. Otherwise handoff means "start over from the top".
Not in the megamenu. Surfaces where text isn’t the only input.
First Workflow
Don’t deploy everything at once. Choose one channel, one shift window, and one action. Add the rest only when exceptions already cost you money.
Telegram, WhatsApp, Instagram, widget—the entry point customers choose naturally. Otherwise your pilot starts with an empty messenger.
One shared window, queue rules, and ACL. Without this, handoffs sound like "please describe your issue again".
Order status, appointment booking, or qualification. Once that runs reliably, introduce CRM, broadcasts, or AI agents.
FAQ
The features page in volbor is a catalog of modules: channels, Inbox, flows, AI, CRM, broadcasts, commerce, and analytics. It is a product directory, not a single monolithic "super-bot".
The megamenu in the header is concise. The full list—including TikTok, Mini Apps, voice, video widgets, inventory, and multicurrency—lives right on this page.
No. One channel entry point, one shift window, and one automated action are enough to start. Additional modules can be connected as real operational exceptions arise.
A chatbot handles conversational turns inside a channel. Automation performs actions based on events: updating statuses, lead scoring, or dispatching webhooks. They connect into a single workflow rather than competing with each other.
Inbox is needed as soon as a human teammate joins the conversation: shared history, assignment, and handoff. Without it, the shift cannot see what the bot has already communicated.
Not for pricing, inventory, or contracts. The knowledge base comes first as the single source of truth, followed by the model. Otherwise responses sound confident while conflicting with actual pricing.
Events and APIs are on the webhooks page. Data access for AI agents is handled via MCP connectors, never raw SQL.
With a quick start and a single test conversation in your chosen channel. Read the catalog to pick your entry point, not to deploy every module in a single day.
