The contact center your security team can actually read.

using Verbara.Platform.Api;
using Verbara.Sdk.Pro.Licensing;
using Verbara.Sdk.Pro.MultiTenant;

var builder = WebApplication.CreateBuilder(args);
builder.Services
  .AddVerbaraPlatform()
  .AddPro(opts => {
    opts.LicenseFile = "/etc/verbara/license.lic";
    opts.EnableMultiTenant();
    opts.EnableCallAnalytics();
    opts.EnableAgentAssist();
  });

var app = builder.Build();
app.MapVerbaraPlatform();
await app.RunAsync();

Verbara.Platform — CC API bootstrap with multi-tenant + Pro features →

• How many agents does it support, and how are they counted?
  We count licensed agents, not connections: every enabled agent identity of every client, whether or not they log in, and anyone who serves; the deployment pays for the day of the month with the most counting at once, across all of its clients. Tier 1 self-host caps at 25; Tier 2 goes to 500 per deployment with multi-cluster, and beyond that only by contract after a load test. SaaS Business (Tier 3) and Enterprise (Tier 4) scale per contract. The cap is licensing, not technical — the engine scales horizontally with Pro clustering.
• Multi-tenant for BPOs?
  Yes, from Tier 2 self-host. Strict per-tenant isolation, per-tenant skill routing, cross-tenant admin impersonation. Each BPO client sees only their data and their agents.
• Compatibility with my existing PBX?
  If your PBX is Asterisk (any version 16+), Verbara connects to your dialplan via AMI/ARI. If your PBX is Cisco/Avaya, you need a SIP gateway to Asterisk; the most common ones are documented.
• Do my agents need a desk phone or an installed softphone?
  No. Verbara ships a WebRTC softphone inside the agent workspace: they take and make calls straight from the browser, with no desk phone and no softphone software to install and maintain. The agent opens the URL, registers their extension, and they are on the line — ideal for remote teams and BPOs that would rather not manage hardware or per-seat softphone profiles.
• Do I have to edit the Asterisk dialplan to connect trunks and numbers?
  No. SIP trunks and DIDs are configured from the admin UI with a guided wizard, including a connectivity test that validates trunk registration before you put production traffic on it. No hand-editing dialplan files, no Asterisk restart for each change. If you prefer raw dialplan, it is still your Asterisk — but most day-to-day operation no longer requires it.
• What happens if an agent loses internet or closes the tab mid-shift?
  Verbara detects it. A liveness heartbeat identifies the disconnected or "zombie" agent and reacts: orphaned digital work (chats, WhatsApp, email) is automatically re-queued to the front of its queue for the next live agent, and if a voice call drops with the customer still on the line, the customer gets a priority callback to the next available agent in their origin queue. On top of that, you set concurrent capacity limits per channel plus a MaxTotal across async channels, with a per-tenant default and per-agent override — so no one gets over-assigned.