Solution · Omnichannel

Eleven channels, one inbox.

WhatsApp Meta direct (no intermediate BSP), SMS, email, WebChat, Telegram, IG, Messenger, and more. Multi-tenant, with Flows DAG and LLM nodes.

Developer license → See the code

What you replace

Eleven channels without per-message fees.

Messaging CPaaS platforms charge per message + per provider + per channel. Verbara unifies them.

	Verbara	Twilio Conv.	Sinch · MessageBird	Chatwoot (OSS)
Open-core	✓ MIT + Apache	✗ closed cloud	✗ closed cloud	✓ MIT
Self-host	✓	✗	✗	✓
11 out-of-box connectors	✓ 11 channels	~5	~7	~5
WhatsApp Meta direct	✓ direct	via BSP	via BSP	via BSP
Flows DAG with LLM nodes	✓ DAG	✗	~ flows	basic flows
Multi-tenant white-label	✓ Pro	✓ enterprise	✓ enterprise	✗
Native voice integrated	✓ native	✓ separate API	✓ separate API	✗

Read the code

One queue for everything.

OmnichannelRouter.cs

using Verbara.Platform.Routing;
using Verbara.Platform.Channels.WhatsApp;
using Verbara.Platform.Channels.Sms;
using Verbara.Platform.Channels.WebChat;
using Verbara.Platform.Flows;

routing.UseChannel<WhatsAppChannel>("whatsapp", opts => {
  opts.WhatsAppBusinessAccountId = Env("WABA_ID");
  opts.AccessToken = Env("WA_TOKEN");
});
routing.UseChannel<SmsChannel>("sms");
routing.UseChannel<WebChatChannel>("web");

routing.MapInbound("support", flow => flow
  .Llm("classify", opts => {
    opts.Model = "gpt-4o-mini";
    opts.SystemPrompt = "Route to billing, technical, or general queue.";
  })
  .Switch("classify.label", route => route
    .Case("billing",   q => q.ToQueue("billing"))
    .Case("technical", q => q.ToQueue("technical"))
    .Default(q => q.ToQueue("general"))));

Verbara.Platform — WhatsApp + SMS + WebChat in a Flow DAG with 1 LLM node →

FAQ · Omnichannel

Messaging questions.

Direct to Meta. Verbara implements the WhatsApp Business Cloud API with HMAC verification and 24h window handling. You get your own Business Account, no BSP between you and Meta. Approved templates are managed via Flows.
Yes. The SMS connector is provider-agnostic with a Twilio provider included by default, plus segment calculation. For LATAM, regional providers (Infobip, Movile, etc.) connect by implementing an IProvider — a few hours of work.
The Conversations module correlates by contact: if a customer writes via WhatsApp and then via email, both hits land in the same conversation with a unified timeline. Routing is by skill/queue/team, not by channel — the operator sees the full history.
You decide. Concurrent capacity is configurable per channel (chat, email, SMS, voice) plus a MaxTotal across async channels, with a per-tenant default and per-agent override — a senior can carry more chats than a junior without touching anyone else. And if an agent disconnects, their in-flight digital work is re-queued to the front of its queue for the next live agent, so load does not get stuck in a dead tab.

Omnichannel pricing

Which tier do you need?

Tier 0 community for self-host evaluation. Tier 2 ($30-50k/yr) for multi-tenant in your own SaaS. Tier 3+ ($99/agent/mo) if you prefer hosted with SLA.

See full pricing →

Eleven channels, no per-message fees.

30-day signed developer license, free. WhatsApp Meta direct, no middlemen.

Get a developer license →