Your AI agent works. The telephony layer underneath it adds latency, cost, and failure modes that do not scale.
Sigmond is a voice AI agent running on the SignalWire infrastructure this page is about. Ask him about anything you just read.

Your stack routes audio through a telephony provider, an STT provider, an LLM, and a TTS provider. Each hop adds 100-300ms. Four hops turn a fast LLM into a slow conversation.
When the call drops at 2am, who gets the ticket? The telephony provider, the STT vendor, or the TTS vendor? Debugging across four dashboards is the real cost.
Conversation context lives in webhooks, Redis, and vendor callbacks. Transfers lose context because no single system owns the call state.
Each vendor marks up the layer below it. A four-vendor stack means four margins stacked on top of carrier costs.
from signalwire_agents import AgentBase
from signalwire_agents.core.function_result import SwaigFunctionResult
class SupportAgent(AgentBase):
def __init__(self):
super().__init__(name="Support Agent", route="/support")
self.prompt_add_section("Instructions",
body="You are a customer support agent. "
"Greet the caller and resolve their issue.")
self.add_language("English", "en-US", "rime.spore:mistv2")
@AgentBase.tool(name="check_order")
def check_order(self, order_id: str):
"""Check the status of a customer order.
Args:
order_id: The order ID to look up
"""
return SwaigFunctionResult(f"Order {order_id}: shipped, ETA April 2nd")
agent = SupportAgent()
agent.run()
| Component | Multi-Vendor Stack | SignalWire |
|---|---|---|
| Transport (PSTN/SIP) | $130-220 | Carrier rates (separate) |
| Orchestration middleware | $500-2,000 | Included |
| STT provider | $400-800 | Included |
| LLM provider | $1,000-4,000+ | Included |
| TTS provider | $500-2,000 | Included |
| Total | $2,530-9,020 | $1,600 |
We replaced the telephony layer first. Latency dropped, costs dropped, and we stopped debugging three vendor dashboards at 2am. Six months later we moved everything onto one platform.
Point your existing system at SignalWire for phone numbers and PSTN. Your AI orchestration stays unchanged. Immediate cost savings and lower latency.
Move STT and TTS onto the platform. Eliminate separate provider SDKs and invoices. Reduce network hops and latency.
Move your agent logic to the Python SDK. One stack, one vendor, sub-second latency. Scoped prompts and tools per conversation step.
Yes. Phase 1 replaces only the telephony provider. Your AI logic, agent definitions, and conversation flows stay the same.
Provision new numbers via API or dashboard, or port existing numbers from your current provider. Typical US porting takes 5-10 business days with no downtime.
SignalWire replaces the telephony underneath your orchestration layer. Your agent definitions stay the same. Better latency and lower cost from day one.
AI processing: STT, LLM inference, TTS, and orchestration. Transport (SIP, PSTN) is billed separately at carrier rates. One invoice. Billing counts AI processing time, not total call time.
Yes. Standards-compliant SIP with full codec support, DTMF, and encrypted media. Built on the same engine that powers major carriers and contact center platforms.
Trusted by 2,000+ companies
Better latency, lower cost, and a path to the full platform when you are ready.
SignalWire is a communications infrastructure platform. Voice, video, messaging, conferencing, queuing, recording, and AI all run on the same real-time voice and video substrate.
AI is one capability among many, not the whole business. Customers compose multiple services on a single carrier-billed call; margin expands as the service mix shifts toward higher-margin capabilities stacked on top of the transport layer.
The platform was built by the team that created FreeSWITCH. It processes 2.7 billion minutes and messages annually and is in production at 2,000+ companies, including Apple, Sprinklr, Deutsche Telekom, and T-Mobile.