All fields are required
Regulators audit your telephony stack, not your LLM. One platform covers recording, consent, PCI scope, and HIPAA controls.
PHI encryption, access logging, BAAs, and breach notification belong in infrastructure. Your LLM pipeline was never designed to provide them.
The FCC confirmed in February 2024 that AI voice calls are subject to TCPA. Consent tracking, opt-out handling, and time restrictions require infrastructure enforcement.
Each vendor that touches cardholder data needs its own compliance boundary. Five vendors means five breach notification paths and five audit surfaces.
Separate BAAs for SIP trunking, speech-to-text, LLM inference, and text-to-speech. A gap between any two vendors is a compliance gap.
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()
| Regulation | What They Audit | Penalty |
|---|---|---|
| HIPAA | PHI handling, encryption, access controls, BAA coverage | Up to $1.5M per violation category per year |
| TCPA | Consent tracking, opt-out handling, call time restrictions | $500 to $1,500 per violation (AI calls confirmed subject, Feb 2024) |
| PCI DSS | Cardholder data scope, encryption, access logging | Fines plus loss of card processing ability |
| SOC 2 Type II | Security controls, availability, processing integrity | Loss of enterprise deals |
| STIR/SHAKEN | Caller ID attestation, spam prevention | Number blocking, reputation damage |
Sensitive data is available to tool functions but invisible to the LLM context window. The model cannot leak what it cannot see.
Each conversation step grants access to different tools. An intake step cannot access payment data. A billing step can pause recording during card entry.
The platform validates every state transition. The model cannot skip steps or access capabilities outside its current scope.
Obtain consent, start, pause during sensitive data, resume, stop. Every step is logged with timestamps and method documentation.
Every call generates a structured compliance record: consent timestamps, recording events, tool calls executed, and call disposition.
Single BAA covering the entire platform. No separate agreements per service.
PII lives in the hidden data layer, accessible to tool functions but invisible to the LLM.
Two-party consent tracking, encrypted storage, retention policies, and role-based playback access.
Every call produces a compliance-ready record. No retrofit required.
Yes. A single BAA covers the entire platform: telephony, recording, storage, and access control. No separate agreements per service.
Sensitive data (SSNs, account numbers, payment details) lives in the hidden data layer. Tool functions can access it, but the LLM context window never receives it. The model cannot leak what it cannot see.
The platform supports one-party and two-party consent with per-state jurisdiction rules. Consent timestamps, method documentation, and opt-out handling are logged automatically.
Each conversation step defines which tools are available. An identity verification step accesses identity tools. A payment step accesses payment tools and can pause recording. No step has access to tools outside its scope.
Yes. The compliance layer is infrastructure. Your LLM handles conversations. SignalWire handles encryption, recording, consent tracking, audit trails, and access controls regardless of which AI provider you use.
Trusted by 2,000+ companies
One platform, one BAA, one audit surface for your entire voice AI stack.