Phony.ai cover art

Phony.ai

Phony.ai

By: Phony.ai
Listen for free

This Season's Biggest Deal | $0.99/mo for 3 months + $20 Audible bonus

Auto-renews at $8.99/mo. after 3 months - terms apply.
Summary
AI phone and voice agents, explained through the constraints that actually decide whether one works: end-to-end latency and where it comes from, interruption and barge-in handling, telephony plumbing and call control, transfer design, and the disclosure and recording rules around automated calls. Each episode takes one design decision and works through it concretely — provider-neutral, comparing approaches rather than selling one. Written for teams evaluating, buying or building voice AI who need to know what breaks before it breaks in production. Five or six minutes an episode. Topics include end-to-end latency and where it comes from, barge-in and interruption handling, telephony and call control, transfer and escalation design, prompt and turn design, evaluation and call review, and disclosure, consent and recording rules. Produced by Phony.ai, provider-neutral AI phone and voice agents. Full details, services and further reading at https://phony.ai2026 Phony.ai Economics Management Management & Leadership
Episodes
  • Card Payments on AI Phone Calls and PCI Scope
    Nov 20 2026

    Taking a credit card payment over an AI phone call seems straightforward — until you map out every component the audio touches. This episode of Phony.ai works through the PCI DSS 4.0.1 scope problem in detail, examining how cardholder data can silently flow through a voice stack and what operators must do to contain it. The discussion draws on the Phony.ai deep-dive on card payments and PCI scope to give builders a practical compliance framework.

    The episode covers the full landscape of risk and mitigation, including:

    • What "scope" actually means for a voice call — a typical AI phone call routes audio through at least five components (carrier, speech-to-text, language model, text-to-speech, and recording storage), and a spoken card number brings all of them into the cardholder data environment.
    • The CVV storage trap — PCI DSS 4.0.1 prohibits storing card verification codes after authorisation, and a call recording or transcript that captures a spoken CVV counts as storage, regardless of how briefly the file was intended to be kept.
    • DTMF masking — intercepting keypad tones at the carrier level and replacing them with a neutral beep before they reach downstream systems; the most effective single step for reducing scope, keeping card digits confined to the carrier-to-processor path.
    • Pause-and-resume recording — a fallback layer that closes the storage window during the payment moment but does not address the transmission path; best treated as a complement to tone masking, not a substitute.
    • Tokenised payment link handoff — the agent sends the caller a text or email link to the processor's own hosted payment page, so the card number never crosses the operator's carrier; this approach can reduce a compliance self-assessment from roughly 300 controls (SAQ D) down to 13 (SAQ A).
    • Fraud risk and agent guardrails — with fraud attempts hitting approximately one in every 599 contact-centre calls and knowledge-based authentication failing more than half the time, payment flows on AI agents need bounded, structured transaction logic rather than open-ended model improvisation.

    The episode closes with a practical diagnostic: track the ratio of payments completed through the tokenised handoff against those that end up being finished by a human reading digits off a callback note. A rising second number is an early warning that the payment flow is routing around the design — and the fix usually lives in SMS deliverability, the handoff page, or the resume logic inside the call data security layer, not in the agent prompt. For teams thinking about how actions an agent can take intersect with regulated data, this episode offers a concrete starting point.

    For more on building compliant AI voice experiences, listen to What Your AI Voice Agent Must Say Before the Second Ring — a companion episode on disclosure obligations.

    AI phone software

    Show More Show Less
    5 mins
  • What Your AI Voice Agent Must Say Before the Second Ring
    Nov 17 2026

    AI voice agents have quietly stepped into a third legal layer that most businesses never see coming. Beyond call-recording consent and TCPA dialing rules sits a separate and fast-growing body of law: the right of a caller to know they are speaking with a machine. This episode of Phony.ai walks through the current state-by-state disclosure landscape, drawing on this in-depth guide to bot disclosure laws for AI phone calls, and shows exactly how to craft an opening line that satisfies all of them at once.

    Here's what the episode covers:

    • California's two-track framework: The 2019 BOT Act set the original commercial disclosure floor, while AB 2905 — effective January 2025 — specifically targets synthetic and AI-altered voice in outbound calls, with civil penalties up to $2,500 per violation.
    • Utah's on-request trap: Utah doesn't require upfront disclosure for most callers — but the moment anyone asks "am I talking to a real person?", an agent that deflects or answers in the first person triggers a per-call fine. Regulated professions like law firm intake calls and healthcare face an even stricter proactive duty.
    • Colorado and Texas heading for proactive defaults: Colorado's law (effective June 2026) requires disclosure unless it would be "obvious to a reasonable person" — a carve-out that doesn't protect a natural-sounding voice agent. Texas healthcare providers face a similar proactive requirement from January 2026.
    • The EU AI Act's Article 50: Enforceable from August 2026, it mandates that any user interacting with an AI system be informed of that fact — a global consideration for any business taking calls from EU numbers.
    • What a compliant opening line actually sounds like: A single first-turn phrase using a recognizable non-human noun ("AI assistant" or "automated assistant") satisfies California, Utah, Colorado, and Texas healthcare rules simultaneously — no lengthy script required.
    • The four compliance fundamentals: Disclose in the first turn, use a noun callers recognize, ensure the agent can handle the follow-up question gracefully, and log the exact opening line per call for every conversation.

    The pace of legislation is accelerating — 99 AI-related laws passed in 2024, 144 in 2025, with active disclosure bills moving through Illinois, New York, and New Jersey. Getting the opening line right today is far cheaper than retrofitting it after a complaint. If you're building or refining a voice agent, it's worth reviewing how call handling and transcripts can help you log and audit exactly what your agent says on every call. For more on recording obligations that often travel alongside disclosure rules, listen to What Your AI Voice Agent Must Say Before It Records the Call.

    Phony.ai

    Show More Show Less
    5 mins
  • What Your AI Voice Agent Must Say Before It Records the Call
    Nov 15 2026

    Most businesses deploying AI phone agents have heard of the TCPA. Far fewer have mapped the parallel legal regime that governs whether a call can be recorded at all — and that gap is where serious liability quietly accumulates. This episode uses a 2025 federal court ruling against an AI voice assistant handling Domino's franchise calls as a jumping-off point to unpack what AI agents must disclose before recording begins, and why getting it wrong carries consequences far heavier than most operators realize.

    The episode works through the full landscape of recording consent law — from the federal baseline to the state statutes that override it — and lands on concrete, implementation-ready guidance for anyone building or deploying a voice agent today. Key ground covered includes:

    • One-party vs. all-party consent: Federal wiretap law lets a party to the call consent on its own behalf, but roughly thirteen states reject that standard entirely — requiring every participant's consent before a recording is lawful.
    • Criminal exposure, not just civil fines: Illinois treats a first-offense business recording violation as a Class 4 felony; Pennsylvania classifies it as a third-degree felony with fines up to $15,000; California's statutory floor is $5,000 per call.
    • Extraterritorial reach: The caller's state controls, not the business's. A dental practice in Texas answering a call from a California number must deliver the California disclosure — the business's physical location is irrelevant.
    • The disclosure script itself: Say "recorded," not "monitored." Combine the AI identity disclosure and the recording notice in a single breath. And critically — any offered opt-out must be technically real; an opt-out the voice agent cannot actually honor is legally worse than no opt-out at all.
    • Washington's recording-order rule: The recording track must start before the disclosure plays — not after. If the opening greeting is trimmed for storage efficiency, the consent evidence is gone with it, and call logs alone are not a substitute for the audio record.
    • State-aware routing: The caller's state is knowable from the number before the agent says a word. That signal should drive which disclosure script fires. Unknown or spoofed numbers should default to the strictest applicable standard, not a guess — and calls where consent cannot be evidenced end-to-end simply should not be recorded. Reviewing how your platform handles call handling and transcripts is a sensible first audit step.

    For more on the regulatory side of AI-powered outbound calling, the episode TCPA and AI Calls in 2026: What Every Outbound Campaign Must Know covers the companion framework that governs whether an AI agent can dial in the first place. Together, the two episodes map both sides of the legal picture every voice-agent operator needs to understand.

    Phony.ai

    Show More Show Less
    5 mins
No reviews yet
In the spirit of reconciliation, Audible acknowledges the Traditional Custodians of country throughout Australia and their connections to land, sea and community. We pay our respect to their elders past and present and extend that respect to all Aboriginal and Torres Strait Islander peoples today.