Contact centres & BPOs

Numbers and minutes for teams that live on the phone.

Present a local number in each market you call, land inbound on the dialler or PBX you already run, and keep spend inside a prepaid wallet with a per-call record.

Inbound to your diallerCaller-ID pools for campaignsOptional hosted agent workspace
Contact-centre routing · illustrative

Caller

Incoming callto your local number+44 20 •••• ••••London geographic · held with OBSID

OBSID voice service

OBSIDnumber → endpoint · limits
  • Number resolved to your endpoint
  • Channel limit 24 · 6 in use
  • Backup: sip:backup.example.com

Your dialler

Configured PBX destinationsip:dialler.example.com:5060
  • In-group “Sales UK” · 4 agents ready
  • Ringing agent 2 · 00:03
Your system, your queues

Inbound: the caller reaches your dialler on a local number; OBSID applies the route, channel limit and backup you configured.

01The operational problem

Voice services for busy contact centres.

A contact centre needs numbers people will answer, capacity that matches its seats, and a bill it can reconcile against campaign results — usually across several countries and often with a dialler that is already in place.

Local and toll-free numbers

UK, US and Canadian numbers routed to your dialler; further markets on request. Call-backs land on your team, not a dead line.

Global numbers

Termination with your CLI

Campaign calls leave through OBSID presenting numbers you hold — fixed or a rotating pool with cooldowns and daily caps.

Voice termination

Channel limits that match seats

Concurrency per endpoint sized to your agents and dial ratio, so the dialler is declined cleanly rather than overrun.

SIP connectivity

Hosted agent workspace (optional)

If you would rather not run a dialler: browser softphone, campaigns, lead lists, recording and QA scoring, provisioned by OBSID.

Call-centre portal
Illustrative deployment

Example: a 12-seat contact centre.

An outbound team calling the UK and Canada from VICIdial, with inbound call-backs answered by the same agents. The specifics that a deployment like this settles on:

Example values, not a customer case study.
NumbersOne UK geographic and two Canadian local numbers; the same three numbers form the outbound caller-ID pool, with per-number daily caps.
EndpointThe dialler's public IP allow-listed, UDP transport, channel limit 24 for 12 seats at a 2.0 dial ratio.
BillingPrepaid wallet topped up weekly; the per-call log is exported for campaign reconciliation.
02Call handling

What happens to an inbound and an outbound call.

Both directions use the same endpoint. The lanes below follow one call each way: where it starts, what OBSID checks, where it lands and what the record shows.

Inbound call

  1. StartsA customer dials one of your local numbers.
  2. OBSID checksThe route for that number, its channel limit and whether a backup destination applies.
  3. LandsYour dialler's in-group or queue; the caller's own number is shown as received from the carrier.
  4. RecordTime, number, endpoint, result and duration in the activity log.

If it cannot connect: If the primary endpoint is unavailable, new attempts go to the backup destination; above the channel limit, the attempt is declined with the reason logged.

Outbound campaign call

  1. StartsYour dialler originates the call over the SIP endpoint.
  2. OBSID checksSource IP, wallet balance, channel limit and the caller-ID policy — a fixed number, or the next number from your pool.
  3. LandsThe called party, via a carrier route for that destination, seeing a number you hold.
  4. RecordDestination, presented caller ID, result, duration and cost in the log and usage.

If it cannot connect: If the balance is empty, the limit is reached or there is no route, the call is declined and the reason appears in the log.

03Prerequisites

What you need in place.

1

Dialler or PBX

A SIP system with a fixed public IP that OBSID can allow-list and reach.

2

Business account

Company details for the account; documents for any regulated numbers.

3

Compliant calling

Lead lists and calling practices that follow each destination's rules.

4

Funded wallet

Balance in place before campaigns start; minutes are deducted per call.

04Questions

Asked by teams like yours.

Yes — VICIdial, GoAutoDial, 3CX, FreePBX and any SIP system with a fixed public IP connect as an endpoint. The hosted workspace is optional.
Ready when you are

Tell us your markets and seat count.

We come back with numbers, routes and the connection details for your dialler.

Prepaid walletPer-call logVerification per order