Illustrative example
Hosted VICIdial Cluster for a Multi-Client BPO
Illustrative project — how we would design a hosted VICIdial cluster for a BPO running separate outbound and inbound programmes for several clients.
This is an illustrative scenario showing how we would approach this type of project. It does not describe a specific customer, and the results listed are intended outcomes, not measured results.
Project overview
A sample scenario showing how we approach a multi-client BPO deployment. It is not a description of a specific customer.
Customer requirement
A BPO runs outbound sales for two clients and inbound support for a third, with agents shared across programmes. Each client needs separate data, numbers, caller IDs and reports.
Technical challenge
Client data must not leak between programmes, inbound callers must be prioritised over outbound dialing, and the platform must grow as new contracts are added without re-architecture.
Proposed solution & implementation
A clustered VICIdial deployment with a dedicated database server and separate telephony servers. Each client is modelled as a user group with its own campaigns, in-groups, DIDs and caller IDs. Blended campaigns give inbound queues priority. Scheduled client-specific reports are emailed daily, and restricted admin logins let client managers view only their programmes.
Intended outcomes
- Intended outcome: client data and reporting separated by permissions
- Intended outcome: shared agents productive across inbound and outbound
- Intended outcome: new clients onboarded from a campaign template
Why this architecture
Separating the database from telephony keeps real-time reporting responsive while calls are processed elsewhere. Adding a telephony server increases call capacity without touching client configuration.
What we would measure after launch
- Drop rate per outbound campaign
- Inbound service level and abandon rate per client
- Agent occupancy across blended campaigns
Have a similar project?
Describe your requirement and we’ll explain how we’d approach it.