Niches · Phone calling & voice transport

Hand a live call from the agent to a person, warm or cold

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

0companies, full fit
13companies, fit with a limit
32companies carry the tag
16share of the category's work
9first-hand accounts

What counts as done

The agent can start a transfer while its audio stream is open, choose cold (blind) or warm (consult, then bridge), send DTMF to reach an extension, keep or replace the caller ID as documented, and receive a failure reason (busy, no answer, voicemail, declined) when the transfer does not complete.

Measured, for our own tests: on a test call the caller is bridged to the destination with no more than 3 seconds of silence and is not dropped when the agent leg ends. No docs we read state these figures, so they don't count against a listing here.

How agents ask for it: transfer the caller to a manager, put me through to a human, warm transfer with a summary, dial my number when the bot detects X

Does the job, with a limit 13

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

ListingWhy
Bandwidth Voice API + MCP BB
Bandwidth Inc.
StartStream is non-blocking and a POST to /calls/{callId} redirects the live call to a Transfer with transferCallerId and a transferAnswerUrl announcement; Transfer Complete reports failures. Warm consult then bridge is not documented, only an announcement to the callee. Silence bar unpublished. source
didlogic Voice API D
DID Logic PTE. LTD.
The AI gateway page claims native SIP REFER for handoff to staff, but no transfer operation exists in the OpenAPI file, nothing for a WebSocket-streamed call, and no warm mode, DTMF send or failure reason. source
Exotel Voice API + MCP E
Exotel Techcom Private Limited
The stream auto-closes and the flow's next applet runs, so a hand-off happens only after the bot session ends; no warm transfer, caller-ID choice or transfer failure reason in the pages read. The bot receives DTMF but cannot send it. source
Infobip Calls API + MCP B
Infobip Ltd
Because the agent is a separate WEBSOCKET leg, the app can dial a person with a chosen from, join them by connect or conference, send DTMF and read CALL_FAILED causes while the stream runs. No transfer verb: cold and warm are built from dialog and conference calls. source
jambonz D
FirstFive8, Inc.
Update call can redirect with a new call_hook, send dtmf, whisper and change conference state on a live call; sip:refer does a blind transfer and dial bridges a new leg. Warm transfer is assembled from conference verbs, and caller-ID rules on the new leg depend on the carrier. source
LiveKit Telephony BB
LiveKit Incorporated
TransferSIPParticipant sends REFER with caller ID set on the trunk, and the beta WarmTransferTask holds, consults, takes dtmf for extensions and bridges. Not on LiveKit numbers; typed failure reasons are still open (agents 7200), and acc-26 saw REFER hit a reused identity. source
Plivo Voice API B
Plivo Inc.
Docs compare DID forward, SIP auth forward and a Multiparty Call; only the Multiparty Call does warm transfer without waiting for the socket to close, because keepCallAlive makes later XML wait for the stream. sendDTMF exists on the stream; hangup causes give the failure. source
SignalWire Voice API B
SignalWire, Inc.
calling.transfer, calling.refer and calling.collect act on a live call id, SIP REFER reports busy and other results with a bridged fallback, and caller ID is settable. A connect stream holds the call until your server closes it, and warm transfer is not a documented mode. source
Sinch Voice API + MCP B
Sinch AB (publ)
PATCH /calls/{callId} sends SVAML to a live call: dial and bridgeCall run non-blocking beside the stream, and Voice Relay documents DTMF send. No warm-transfer mode, caller-ID rule or typed transfer failure reason in the pages read. source
Telnyx Voice API + MCP BB
Telnyx LLC
The transfer command takes from, AMD and a webhook and reports a failed leg with call.hangup, but it refuses with error 90045 while media streaming is in use, so the agent must stop its stream first; $0.10 a transfer. acc-29 found no queued transfer for the websocket transport. source
Twilio Programmable Voice API + MCP A
Twilio Inc.
Connect Stream runs no further TwiML until the socket closes, so a transfer means updating the call through the REST API, which ends the stream; DTMF cannot be sent on the stream. acc-06, acc-07, acc-10 and acc-15 hit this, and acc-27 lost the caller's ID on the new leg. source
Vonage Voice API + MCP C
Vonage Holdings Corp.
The websocket is a leg in a named conversation, so a person's leg can join with canHear and canSpeak, connect takes from and dtmfAnswer for extensions, and PUT /v1/calls/:uuid transfers or sends DTMF. Warm transfer is built from conversations rather than a mode; failure reasons not checked. source
Voximplant C
Voximplant, Inc.
The scenario holds every leg, so it can dial a person with a chosen callerid and bridge while the WebSocket runs; handleBlindTransfer and notifyBlindTransferFailed(code, reason) cover blind transfers. Warm transfer is left to scenario code. source

Doesn't do this job 2

Listings in the category that do something else, with the reason.

ListingWhy
46elks Voice API E
46elks AB
The websocket protocol has hello, bye, sending, listening, audio, sync and interrupt only, with no transfer or call-update message. Connect is a call action (cold, with callerid) that the streaming session cannot issue. source
DIDWW Voice and Number Management API B
DIDWW Ireland Limited
No call control in the API; a transfer is done by the SIP platform, with DIDWW only carrying the new leg on the outbound trunk. source

What stops agents finishing

  • the bidirectional stream blocks further call instructions until it closes (acc-07, acc-10)
  • transfer not supported on the platform's own numbers (LiveKit Phone Numbers)
  • carrier rejects the original caller ID on the new leg (acc-27)
  • per-transfer fee on top of minutes

Around it

Before: voice-agents.inbound-receptionist, voice-agents.tool-call-mid-call. After: support.handoff-to-person, crm.log-activity.

Where this comes from

Weight 16 of 100 in Phone calling & voice transport: 9 of 49 accounts: two near-identical transfer questions on each Twilio starter repo, Stack Overflow questions on dialling out or conferencing during a bidirectional stream or sending DTMF from one, LiveKit warm-transfer issues (caller ID, IVR extension, failure reason, wrong participant) and a Pipecat request for a Telnyx transfer. Weighted above its count because the category test sentence names a warm transfer on every API

The same as data: /api/v1/use-cases/voice-calling.transfer-to-human.json, or the MCP tool get_use_case with id voice-calling.transfer-to-human. Other jobs in this category: /api/v1/niches?category=voice-calling.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.