Home · Solutions · Contact centres

Voice for contact centres that need calls answered

Inbound queues, outbound campaigns and blended operations run on the same routes the carriers use, with capacity sized to your peaks and your caller ID delivered exactly as you send it.

Calls that get answered

Answer rates live and die on the route. Every call carries your calling number end to end, so the destination network sees a real number, more calls are picked up and fewer are flagged.

Capacity sized to your peaks

Each account has its own call-rate and channel allowance, set for your operation and raised on request ahead of a campaign. It is never shared with another customer's traffic.

Numbers where your customers are

Local and national numbers in 96 countries for inbound queues and local presence on outbound, delivered into your platform over SIP and moved between campaigns from the portal.

Connects to the platforms contact centres run

Standard SIP, IP authentication by default, and a single endpoint that stays stable while routing decisions are made per call behind it.

  • Asterisk and FreeSWITCH based platforms, including custom-built operations
  • Genesys, Cisco UCCX and Avaya over a SIP trunk
  • Cloud contact-centre platforms with SIP connect, one trunk per site or per campaign
  • Microsoft Teams voice through a certified SBC, TLS and SRTP
  • Multiple sites on one account with separate limits and reporting per site
# Account view · contact centre, 3 sites Endpoint: sip.callivex.com (active/active) Channels: 212 / 400 in use Call rate: within allowance Caller ID: delivered end to end Numbers: 46 across 9 countries Sub-accounts: site-lon · site-mad · client-b Blocked list: 1,204 numbers, per account NOC: no open incidents
# What one sub-account carries Name: client-b (retention team) Balance: own prepaid balance Limits: own call-rate and channels Numbers: 12 UK · 4 ES · 2 DE Lists: do-not-call 3,180 · blocked 96 Records: per call, CSV export Access: portal login for the team lead

Control that ops managers ask for

The tools an operation needs to stay compliant and in control, without a ticket to us for every change.

  • Per-campaign or per-client sub-accounts with their own balance and call records
  • Do-not-call and blocked-number lists applied at the trunk, per account
  • Call records for every call, exportable for audit and for your own reporting
  • Attestation on calls into the United States and Canada, so your numbers are signed
  • Network operations centre staffed 24 hours a day for live faults, engineers on the line
Questions

Frequently asked

Can you handle our campaign peaks?
Yes. Each account has its own call-rate and channel allowance sized to your operation. Tell us the peak hours and the destinations before a campaign starts and we raise the allowance ahead of it. It is never shared with another customer's traffic.
Is our caller ID delivered as we send it?
Yes. Every route carries your calling number end to end. It is not stripped or substituted, so the destination network and the person answering see the number you present.
Can each campaign or client have its own account?
Yes. Sub-accounts each carry their own balance, limits, call records and number lists, so a campaign or an end client can be reported and controlled on its own.
Which platforms can connect?
Anything that speaks standard SIP: Asterisk and FreeSWITCH based platforms, Genesys and Cisco contact-centre suites over a SIP trunk, cloud contact-centre platforms with SIP connect, and Microsoft Teams voice through a certified SBC. IP authentication is the default, registration is available.
How do you treat outbound campaign traffic?
It is welcome on routes built for it. We ask for the destination mix and expected volumes up front so that capacity and routes are right from day one, and the acceptable-use policy sets out what stays within the rules.

Send us your destination mix and peak hours.

We come back with routes, an allowance sized to your operation and a test trunk.

Test a route →