Omnichannel Contact Centers for MENA BPOs

A BPO is not one contact center. It is a dozen of them sharing a floor, a payroll and a platform, each with its own client, its own rules and its own idea of what good looks like. The platform question is therefore not which features exist, but which of them can be set differently for every client without a second installation. This guide looks at omnichannel from that angle.

One Inbox, Four Channels

The practical definition of omnichannel is narrow: a customer who calls, then messages on WhatsApp, then gets an SMS reminder is one conversation, not three. In DialerBee, voice, WhatsApp, SMS and email threads sit in the same conversation list. Every conversation carries a state, which is new, queued, assigned, in progress or waiting on customer, and can be assigned to a named agent or handed back to a queue at any point.

Those two mechanics do most of the work. States mean nothing sits in a thread nobody owns, and a conversation parked on the customer is visibly different from one waiting on you. Assignment means a thread can move between people without leaving the record behind.

One honest limit is worth stating up front. Per-tenant SMTP sends outbound notifications and reminders from your own server today, and inbound email into the inbox is planned. If a client's workflow depends on inbound email today, plan around that rather than around a roadmap.

Customer 360 and the Screen Pop

Customer 360 is keyed on the phone number, which is the only identifier every channel in the region shares. The profile, the history, the notes and the CRM tab are assembled together for whoever is on the other end, and an inbound call screen-pops that record, so the agent is reading it while the phone is still ringing.

The link to BroadNet CRM runs both ways. It enriches the customer record, creates a contact that does not exist yet, and pushes the disposition back when the call is closed. An agent can also add the customer to the CRM straight from the disposition popup, at the moment they are already deciding what happened, which is the only moment they will reliably do it. Where a client insists on their own data capture, a tenant webform loads in an iframe beside the conversation, so your existing form is the form the agent fills in.

What Multi-Tenant Isolation Buys You

Every platform vendor says multi-tenant. The question to ask is what is isolated and where the isolation is enforced. In DialerBee each client gets its own data, users, campaigns and settings, and isolation is enforced by row-level security at the database layer rather than by application code remembering to filter.

That matters because the things a BPO has to keep apart per client are not only records.

Team structure follows the same logic. Agents are organised into teams with supervisors, visibility is scoped per client, and agents can be assigned to specific campaigns or float across clients as demand moves. Seven role levels run from platform admin down to agent, so a client-side user can be given exactly the view you intend and nothing else.

White-Label: Your Brand, Your Domain

For most regional BPOs the platform is part of the offer, not a tool behind it. White-label here is thirty branding fields rather than a logo slot: colours, type, names and the details that give a platform away. A colour scale carries contrast validation, which catches the brand palette that looks right on a slide and makes small text unreadable across an eight-hour shift. Logo, favicon and background are uploads, and a live preview settles the palette argument by looking rather than by publishing and hoping.

Two pieces make it credible rather than cosmetic. The platform runs on your own domain, verified by a DNS TXT record you place, which is proof of control rather than a claim. And a public branding endpoint serves the branding before anyone signs in, so the login screen, the first thing every one of your customers sees, is already yours.

Ownership follows the brand. Tenants created by a partner admin belong to that partner admin, so you provision, configure and support your own customers, and the relationship stays with you.

Onboarding a New Client Tenant

The fastest way to lose money on a new client is a slow, inconsistent setup. A six-step wizard takes a tenant from nothing to working in the same order every time, so onboarding does not depend on who happened to do it.

Two of those steps carry more weight than the rest. Every tenant gets its own extension range, because platform defaults collide the moment two tenants share them. And every tenant gets its own caller IDs, because a shared trunk is not a caller ID and presenting one client's calls under another client's number is the kind of mistake that ends a contract. Campaign-level controls then cover pacing, DID assignment, compliance rules, scheduling and retry logic per campaign inside the tenant.

Reporting, Billing and What the Client Sees

Client-facing reporting is where a BPO either earns renewal or spends its month building spreadsheets. Per-client dashboards, CDR exports and campaign analytics are scoped to the client, and a partner portal can give your client read-only access to their own campaigns, reports and recordings. Recordings play back through signed URLs, with retention configurable per client and legal hold for disputed accounts.

On the commercial side, usage exports track minutes, calls, seats and storage per client for invoicing, and AI usage is metered and billed per tenant. That last point is what makes reselling AI features possible at all: you can see which client consumed what, rather than receiving one total you have no fair way to split.

Language is the last piece, and in this region it is not a detail. The platform runs in 11 languages including Arabic with right-to-left rendering, so a floor serving a Gulf bank, a Levantine telecom and a European client is running one platform rather than three.

Frequently Asked Questions

What does the omnichannel inbox actually contain?

One conversation list covering voice, WhatsApp, SMS and email threads. Each conversation carries a state, which is new, queued, assigned, in progress or waiting on customer, and can be assigned to a named agent or handed back to a queue. Per-tenant SMTP sends outbound email today, and inbound email into the inbox is planned.

How is one client's data kept separate from another's?

Each client is a tenant with its own data, users, campaigns and settings, and isolation is enforced by row-level security at the database layer rather than by application filtering. Reports, dashboards and exports are scoped to the client, so a client-facing report contains only that client's data.

Can each client use its own carrier and its own numbers?

Yes. BYOC means each client can route through its preferred SIP trunk, and every tenant gets its own extension range and its own caller IDs during onboarding. Platform defaults collide when two tenants share them, and a shared trunk is not a caller ID, so the wizard sets both.

How much of the interface can we brand?

Thirty branding fields, plus uploads for the logo, favicon and background, and a full colour scale with contrast validation. The platform runs on your own domain verified by a DNS TXT record, and a public branding endpoint serves the branding before sign-in, so the login page already carries your brand.

What can we show a client directly?

A partner portal can give the client read-only access to their own campaigns, reports and recordings, alongside per-client dashboards, CDR exports and SLA and performance reports. Recordings play through signed URLs, with retention configured per client and legal hold available for disputed accounts.

How do we bill clients for AI features?

AI usage is metered and billed per tenant, and usage exports track minutes, calls, seats and storage per client for invoicing. Per-tenant attribution is what makes reselling AI possible, because you can see which client consumed what instead of receiving one total you cannot split fairly.