Contact Sales

All fields are required

Your AI Handles Conversations. Your Infrastructure Handles the Audit. | SignalWire
Compliance and Governance

Infrastructure Handles the Audit, Not Prompts

Regulators audit your telephony stack, not your LLM. One platform covers recording, consent, PCI scope, and HIPAA controls.

$1,500
per TCPA violation, no cap
5→2
compliance boundaries eliminated
Day 1
HIPAA, PCI, SOC 2 readiness
20 yrs
telecom compliance heritage
The Compliance Surface Problem

Five Vendors Means Five Audit Surfaces

HIPAA requires platform-level controls

PHI encryption, access logging, BAAs, and breach notification belong in infrastructure. Your LLM pipeline was never designed to provide them.

TCPA applies to AI-generated calls

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.

PCI scope grows with every vendor

Each vendor that touches cardholder data needs its own compliance boundary. Five vendors means five breach notification paths and five audit surfaces.

Multi-vendor stacks multiply risk

Separate BAAs for SIP trunking, speech-to-text, LLM inference, and text-to-speech. A gap between any two vendors is a compliance gap.

Build a Voice AI Agent

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()

Five Compliance Boundaries vs. Two

Multi-Vendor Stack (5 BAAs)

  • SIP trunking provider: separate BAA
  • Speech-to-text provider: separate BAA
  • LLM inference provider: separate BAA
  • Text-to-speech provider: separate BAA
  • Your app: orchestration and everything else
  • Five breach notification paths, five audit surfaces

SignalWire + Your AI (2 boundaries)

  • SignalWire: telephony, compliance infrastructure (one BAA)
  • Your AI provider: LLM inference (your arrangement)
  • One vendor to audit for voice transport, recording, and access control
  • Compliance surface shrinks from five boundaries to two

What Regulators Audit

RegulationWhat They AuditPenalty
HIPAAPHI handling, encryption, access controls, BAA coverageUp to $1.5M per violation category per year
TCPAConsent tracking, opt-out handling, call time restrictions$500 to $1,500 per violation (AI calls confirmed subject, Feb 2024)
PCI DSSCardholder data scope, encryption, access loggingFines plus loss of card processing ability
SOC 2 Type IISecurity controls, availability, processing integrityLoss of enterprise deals
STIR/SHAKENCaller ID attestation, spam preventionNumber blocking, reputation damage

Architecture Enforces Compliance, Not Prompts

Hidden data layer

Sensitive data is available to tool functions but invisible to the LLM context window. The model cannot leak what it cannot see.

Scoped tool access per step

Each conversation step grants access to different tools. An intake step cannot access payment data. A billing step can pause recording during card entry.

Enforced state transitions

The platform validates every state transition. The model cannot skip steps or access capabilities outside its current scope.

Native recording with consent management

Obtain consent, start, pause during sensitive data, resume, stop. Every step is logged with timestamps and method documentation.

Complete audit trails

Every call generates a structured compliance record: consent timestamps, recording events, tool calls executed, and call disposition.

Compliant from Day One

1

Sign up for a SignalWire Space

Single BAA covering the entire platform. No separate agreements per service.

2

Define your agent with the hidden data layer

PII lives in the hidden data layer, accessible to tool functions but invisible to the LLM.

3

Configure recording and consent policies

Two-party consent tracking, encrypted storage, retention policies, and role-based playback access.

4

Ship to production with audit readiness

Every call produces a compliance-ready record. No retrofit required.

At $500 to $1,500 per violation with no cap, a 10,000-call campaign creates up to $15M in exposure. A misconfigured bot makes the same violation on every concurrent call simultaneously.

FAQ

Does SignalWire provide a BAA for HIPAA compliance?

Yes. A single BAA covers the entire platform: telephony, recording, storage, and access control. No separate agreements per service.

How does the hidden data layer prevent PII leaks?

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.

What recording consent models are supported?

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.

How does scoped tool access work?

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.

Can I bring my own LLM and still get compliance controls?

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

Compliance by Architecture, Not by Prompt

One platform, one BAA, one audit surface for your entire voice AI stack.