Cloud telephony

Keep your carrier. Keep your numbers. Add AI agents on top.

Most voice AI projects stall on plumbing: a new carrier, ported numbers, a rebuilt IVR. Ours plug into the telephony you already run, through a carrier API, a SIP trunk or your contact center platform, and send calls back to your human queues with everything the customer has said.

spine·voice
rule v3
Spine gateway · inbound call #40217live
Your carrier or CCaaSSIP INVITE
Session normalizedcaller, campaign, language
Routing rule matchedconfig, no code
VoiceAI resolvesmost calls
Back to your queuewith context
same numbers · same queues · audit chainedTrace call
invite received · tenant resolved · route matched · agent answered · handoff context stored · transfer to queue 12 · audit:chained ✓ ·
Inbound call path through the Spine gateway, simulated · rendered by spine·voice
No rip and replace Your numbers Your carrier Your human queues Routing by configuration
Three ways in

Connect the way your telephony already works.

We meet your stack where it is. Pick the path that fits and change it later without touching the agents themselves.

01 · Carrier API

Cloud carriers

Point a number or a campaign at our agents through your cloud carrier account. Inbound and outbound, with recording and consent handled on our side. Why it matters: the fastest path to a live pilot.

02 · SIP trunk

Any SIP source

Our session border controller accepts standard SIP from your carrier, PBX or dialer and passes context in SIP headers. Why it matters: works with almost any enterprise voice setup, cloud or on premises.

03 · CCaaS

Your contact center platform

The AI agent sits inside your existing flows and transfers back to your platform’s queues when a person should take over. Why it matters: your routing, reporting and workforce tools stay as they are.

Connectors

Live today, and what is next.

Each connector plugs into one gateway and one session model, so a new provider is a connector, not a new product. We only list a connector as live once calls run through it.

  • Cloud carriers, liveTwilio and Telnyx for North America and beyond, and Exotel for India, inbound and outbound.
  • Dialers over SIP, liveTCN outbound campaigns connect over SIP with call context in the headers and a handoff back to the TCN agent desktop.
  • Any standard SIP trunk, liveCarriers, PBXs and dialers that speak SIP connect through our session border controller.
  • Minutes if you need themWhere we own the phone leg, we supply US and Canadian PSTN minutes through our carrier partner.
  • Amazon Connect, Five9 and Genesys Cloud In buildDesigned on the same connector seam and available for pilots on request.
spine·voice // connector registrygateway v1_
Telephony · connectorsstatus
ConnectorPathStatus
Twiliocarrier API✓ live
Telnyxcarrier API✓ live
Exotel (India)carrier API✓ live
TCNSIP + handoff API✓ live
Standard SIP trunkSBC✓ live
Amazon ConnectCCaaSin build
Five9CCaaSin build
Genesys CloudCCaaSin build
new provider = new connectorRequest one
Connector registry, September 2026 · rendered by spine·voice
Why it is easy

Configuration, not a custom integration project.

Every call, whatever it came in on, becomes the same session inside Spine. That is what keeps adding a carrier, a client or a campaign small.

01

One session model

Voice from any carrier or platform is normalized into one record of caller, campaign, language and intent. Agents never care where the call came from.

02

Routing by configuration

Rules per client, campaign, language and time of day live in configuration. Two clients can route completely differently with no code change.

03

Warm or cold transfer back

When a person should take over, the call returns to your queue with the transcript, verified identity and reason for the call attached.

04

Context in, context out

Account and campaign data arrive with the call in SIP headers or over API, so the agent greets the customer already knowing why they are there.

05

Compliance on the line

Recording disclosure, consent and do-not-call checks run before a call connects, whichever carrier places it.

06

Switch providers later

Change carrier or add a region without rebuilding agents, scripts or reports. Your AI investment is not tied to one phone company.

spine·voice // dialer handoff · call #7712001:48_
VoiceAI · outbound campaign over SIPlive
sip · INVITE from dialer ✓ campaign and account in headers
Agent

Hi, this is the servicing team calling about your account. Is now a good time?

Customer

I’d rather speak to someone about the late fee.

handoff · reason stored, call returned to dialer queue
context sentqueue · fee disputes
dialer agent sees the reason on pickupTransfer
Outbound dialer call handed back to a person, simulated · rendered by spine·voice
Your people stay in the loop

The AI answers inside your platform, not beside it.

Your human agents keep working in the desktop they know. When the AI hands a call back, the reason and the conversation so far arrive with it, so nobody asks the customer to start again.

  • No second desktopHandoffs land in your existing queues and agent screens.
  • Your reporting still worksCall records stay in your platform, and every AI turn is also on the Spine audit record.
Book a demo

Tell us your carrier and your platform.

In the demo we trace one call from your kind of phone setup through a VoiceAI agent and back to a human queue, and show what it takes to go live on your numbers.

Carrier API live SIP live CCaaS in build Transfers with context