For contact centers and BPOs

Every department or client in its own lane. All of them in one account.

Whether you run an in-house contact center with several departments or a BPO with several clients, give each one a team with its own agents, caller IDs, campaigns, scripts and reports. Managers see their own team's work and nothing else, seat caps keep each team to the size you agreed, and you run the whole floor from one login.

Sound familiar?

What gets in the way today

  • 01

    Every new client or department means a new setup

    New numbers, new scripts, new campaigns, new logins. Setting up a team takes weeks of copying settings by hand, and something always gets missed.

  • 02

    I can't risk one team seeing another's data

    Team leads need access to their own campaigns, contacts and recordings. Giving them that without exposing the client or department next door is hard when the system was built for one team.

  • 03

    Everyone wants their own report, every week

    Each client and each department head asks for results filtered to their own campaigns, in their own format. Someone on your team spends Monday morning building them by hand.

permissions in 16 groups
59
visibility scopes: own, team and account
3
ready-made reports
32
public API endpoints
26
how OVOKY fits

Run each department or each client as its own team, with its own campaigns, caller IDs, scripts, permissions and reports, inside one account.

  1. Teams

    Create a team per client, department or language and assign it campaigns, contact lists and the caller IDs it may use. Group teams by department and project, and keep each project's offer, objections and compliance notes for the AI live coach. Assign a whole team to a campaign and new members follow automatically.

    • Campaigns and contact lists assigned per team
    • Allowed caller IDs per team or per agent
    • Agent and manager seat caps per team, set by the account owner
    • Departments and projects to group teams by client or line of business
  2. Permissions

    Permissions decide what each person can do, from listening to recordings to exporting contacts. Visibility scopes decide how much they can see: their own records, their team's or the whole account. Save the combinations you use as templates and apply them to new hires in one step.

    • Three roles: admin, manager and agent
    • 59 permissions in 16 groups
    • Visibility scopes: own, team or account
    • Permission templates you define once and reuse
  3. Reporting

    Reports follow the same scopes, so a team manager only sees their own agents. Save a report filtered on a client's or a department's campaigns and email it daily, weekly or monthly in PDF, XLSX, CSV or JSON. When you need the data in your own systems, the public API returns calls, recordings, KPIs and reports.

    • 32 ready-made reports, filtered by campaign, list or agent
    • Scheduled email delivery to the recipients you choose
    • Threshold alerts when a KPI crosses a limit
    • Public API with 26 endpoints, 15 scopes and IP allowlists

Contact centers & BPOs: questions

Short answers to what teams ask us most. Something else on your mind? Talk to us

  • No. In-house contact centers use the same structure: a team per department, line of business or language, each with its own queues, campaigns and reports. BPOs usually go one step further and create a team per client.

  • Yes. BPOs typically create one team per client inside a single account. Each team gets its own campaigns, contact lists, caller IDs and seat caps, and managers scoped to their team only see that team's work.

  • Yes. Company verification can be sent through a signed link to the person at your client who holds the paperwork. They complete the checks online and sign a three-party number agreement between OVOKY, your company and theirs. OVOKY reviews and approves the file.

  • Most BPOs send each client a scheduled report filtered on its campaigns, by email in PDF, XLSX, CSV or JSON. White-label portals and custom domains are not offered.

  • Yes. The public REST API has 26 endpoints and 15 scopes covering calls, recordings, numbers, SMS, KPIs and reports, with key expiry, IP and domain allowlists, and samples in cURL, JavaScript and Python. Outbound webhooks are not available.

  • No. Agents work in the browser with a headset, so staffing a new team is a matter of sending invitations. The interface is available in English, French and Dutch.

Bring every customer conversation into one place

Calls, SMS, WhatsApp, email and chat in one inbox, on one invoice. Start with one team, then grow.