Service providers & resellers

Run voice for your customers without becoming a carrier.

Hold numbers in one account, route each customer's numbers to that customer's system, send their outbound traffic through one interconnect and bill them yourself from OBSID's per-call detail.

One account, many customer endpointsPer-number routingPer-call detail for your own billing
Provider account · “Northgate IT” · illustrativeOne wallet · one invoice
01The operational problem

Manage voice across your customers.

A service provider needs to provision numbers and trunks for many end customers quickly, keep each customer's traffic separate, and reconcile costs against what it charges — without maintaining a dozen carrier relationships.

Numbers for your customers

Buy from one inventory and route each number to the relevant customer's PBX or platform. Release and re-route as customers change.

Global numbers

An endpoint per customer

Each customer system is its own SIP endpoint with its own allow-listed IPs, channel limit and caller-ID policy.

SIP connectivity

Termination you can resell

Outbound routes quoted for your traffic mix; per-call logs show the destination, duration and presented CLI you need for your own invoices.

Voice termination

One wallet, one invoice

All customers' numbers and minutes are charged to your prepaid wallet with itemised usage.

Billing on the platform
Illustrative deployment

Example: hosted voice for 20 businesses.

An IT services company providing phone numbers and trunks to twenty small-business clients on hosted 3CX instances — each instance registered as its own endpoint (see the comparison below). The deployment-specific details:

Example values, not a customer case study.
ScaleTwenty endpoints, one per hosted 3CX instance, each with its own public IP and a channel limit sized to that client.
VerificationUK geographic numbers per client; documents collected once per client and uploaded against that client's order.
Provider billingThe provider's wallet carries every charge; call logs filtered by endpoint feed the provider's own client invoices.
02Customer separation

One account, distinct customers.

Separation is done at the endpoint. Everything that matters per customer — routing, limits, caller ID and the call log — is attached to that customer's endpoint.

Per customer endpointShared across your account
ConnectivityTheir PBX host and allow-listed IPsThe OBSID SIP hosts and signalling IPs
NumbersRouted to that endpoint only; re-routed when the customer changesBought from one inventory
CapacityChannel limit sized to that customer—
Caller IDFixed number or pool for that customer—
RecordsCall log filtered by endpoint for their invoiceOne wallet, one OBSID invoice, itemised usage
03Prerequisites

What you need in place.

1

Business account

Your company details on the OBSID account; the dashboard and wallet are yours.

2

Customer connectivity

For each client, a SIP system with a fixed public IP to register as its own endpoint.

3

Verification process

A way to collect the documents a client's numbers require in regulated countries.

4

Customer billing

Your own invoicing to clients, built from the per-call detail OBSID provides.

04Questions

Asked by teams like yours.

Not today — the dashboard is your account. Customers using the optional call-centre portal get their own agent and supervisor logins for that workspace.
Ready when you are

Bring your customers onto one relationship.

Tell us how many endpoints and which countries. We set up the account and confirm pricing for your mix.

Prepaid walletPer-call logVerification per order