Virtual numbers
A local number can be the front door to a distributed team.
Use virtual numbers to create a familiar customer-facing presence, then route every inbound call to the destination you choose — no matter where the people answering actually sit.
Diagram: three market-facing numbers feed one inbound routing layer, which delivers calls to your team.
What it solves
Presence in one place. Operations in another.
Customers call numbers they recognise. Teams work where the work is. A virtual number closes that gap: the number belongs to the market you are selling into, while the call is delivered wherever your people answer.
- Present a number that matches the market you are serving.
- Answer from anywhere the route can deliver to.
- Separate customer-facing identity from internal phone infrastructure.
- Add or retire numbers as markets and campaigns change.
How it works
Three things happen to every call.
Choose the number
We confirm which number types are available for the destination you need.
Point it at a route
The number is attached to the destination or routing setup you want behind it.
Answer from anywhere
Calls are delivered to the endpoint your team actually uses.
Capabilities
What you can build with it.
Availability of individual capabilities depends on your setup and destinations. We confirm what applies before anything is configured.
- Worldwide availability
- Numbers across international destinations. We confirm the exact formats available for the countries on your list.
- Inbound routing
- Every number can sit in front of forwarding, a rule set, an IVR menu or a team.
- Multiple numbers, one route
- Run several customer-facing numbers into the same destination when that is simpler to operate.
- Separate lines by purpose
- Use distinct numbers for sales, support or a specific campaign and keep the call paths apart.
- Geographic and non-geographic options
- Number types differ by country. We confirm which formats are available where you need them.
- Porting
- Where porting is supported for a destination, we will tell you what the process involves.
Example call flow
A route you could read out loud.
Three market-facing numbers, one shared destination, and separate handling where it matters.
Route definition
Illustrative- Numbers
- New York, London and a support line
- Behind
- One shared inbound routing layer
- Sales
- Routed to the market team on duty
- Support
- Routed to the support ring group
- Otherwise
- Out-of-hours message, then callback path
An illustrative example. Your route is written with you before anything is configured.
Use cases
Where it earns its place.
Entering a new market
Publish a number customers recognise before you have an office there.
Campaign lines
Give a campaign its own number so the calls it generates are easy to identify.
Consolidating regions
Several regional numbers deliver into one team without customers noticing the change.
Coverage & compatibility
Will it work where you need it?
Destinations, number types and endpoint compatibility vary. Send us the specifics and we'll confirm what is available rather than publish a list that may not hold for your case.
FAQ
Common questions
Anything specific to your destinations, numbers or endpoints is confirmed directly rather than answered generically.
Which countries are available?
We provide numbers internationally. Number types, formats and documentation requirements vary by destination, so send us the countries you need and we will confirm exactly what can be issued.
Is registration paperwork required?
Some destinations require address or business documentation before a number can be issued. We will tell you what applies to the specific numbers you are requesting.
Can I keep a number I already have?
Porting depends on the destination and the losing provider. Tell us the number and we will confirm whether it can be moved.
Next step
Ready to set up virtual numbers?
Tell us how your calls work today and where they need to go. We'll map the route with you before anything is configured.