Yes. Under 47 CFR 64.1200(a)(10) a person may revoke consent by using any reasonable method to clearly express a desire not to receive further calls, and you have ten business days to honor it. Saying it out loud to your AI agent qualifies, and the same paragraph bars you from making a keypress or a text reply the only way out. But the automatic opt-out machinery in almost every calling stack lives on the text channel. The voice channel has a microphone and no destination.
Your agent is configured to read out the opt-out. Nothing downstream is configured to catch the answer.
The mistake: treating STOP keyword handling as opt-out coverage
Almost every operator I speak to believes the platform has this covered, because they have watched it work. It does work, on SMS. Twilio's Advanced Opt-Out catches eight keywords, adds the number to a blocked list and, in Twilio's own words, "checks this list before sending any future outgoing messages." Messages. Twilio's Voice Services Policy hands the same job straight back: you must "provide mechanisms for a callee to opt out of receiving those voice calls" and honor them, and "it is your responsibility to cross-check any phone numbers" against the do-not-call registry.
Our platform already handles opt-outs. We watched a STOP come in and the contact went quiet.
That is the text channel. On voice the same platforms hand the obligation back to you in a policy document and ship no equivalent feature.
Ask one question: when a person says stop calling me out loud, what row in what table changes?
If the honest answer is none, every later call in that campaign is a separate violation and your own recording is the evidence.
GoHighLevel's Do Not Disturb help article makes the split visible in its own headings. Email has an Automatic DND Activation bullet. So does SMS, listing the keywords and carrier error codes that trigger it. Calls has neither, only an instruction to adjust the setting inside the contact's profile. The page then summarises the feature as automating opt-outs for SMS and email.
So the channel where the request arrives as a machine-readable keyword is automated end to end. The channel where it arrives as a sentence from an irritated human is a manual task nobody has been assigned.
What the rule says, and the one piece of it that is suspended
Three things are true here, and all three are usually reported wrong.
First, 47 CFR 64.1200(a)(10) does list a voice route, but a narrow one: "an automated, interactive voice or key press-activated opt-out mechanism on a call" is reasonable per se. A spoken sentence is not on that list. It falls to the catch-all, and paragraph (a)(11) says an unlisted method "creates a rebuttable presumption that the consumer has revoked consent" once the consumer produces evidence the request was made.
Read that against your own architecture. Your AI agent records and transcribes every call by default, so you are generating the evidence that triggers the presumption, and paying to store it. On an ordinary call this is one person's word against another. On yours it is a timestamped transcript in your own account.
Second, the deadline is ten business days from receipt, not calendar days, and callers "may not designate an exclusive means to request revocation of consent." Pointing everyone at a web form does not close the spoken channel.
Third, the part people quote most is the part that is not in force. The requirement that an opt-out on one type of message applies to all future robocalls and robotexts from that caller on unrelated matters has been waived twice: pushed to April 11, 2026 by an order released on April 7, 2025, then extended again on January 6, 2026, this time to January 31, 2027, while the FCC considers modifying it. Everything else in that paragraph has been binding since April 11, 2025. Read only the Code of Federal Regulations and you would never know, because the waiver narrows how far a sentence reaches rather than striking it out.
The missing wire, in five stacks I read this week
Retell has the destination: a built-in Do Not Call contact flag you can "set, filter on, and sync with your CRM." Every documented way of setting it is manual, a CRM sync, or a post-call extraction field you define yourself. The four built-in post-call analysis fields are call summary, user sentiment, call successful and in voicemail. Opt-out is not among them.
Vapi has the checkpoint: a pre-dial webhook documented for "suppression lists, consent checks" that returns an eligibility decision before the number is dialled. Its end-call-phrases page also carries the most quotable sentence in this area: "the customer's words do not trigger the match directly." The matcher reads the assistant's transcript, not the human's.
Bland is the exception, and it proves the point rather than closing it. It documents a real tcpa:opt_out guard rail that "monitors the entire conversation to detect if the agent continues to engage after the user opts out." Its three documented actions are end the call, transfer, and jump to a node. All three stop this call. None writes the number anywhere.
So Retell has the field, Vapi has the gate, Bland has the detector, and nobody documents the wire between them. The ten-business-day deadline appears in exactly one place across everything I read: Retell's marketing blog, updated on September 7, 2026, which says the agent "must classify revocation intent independent of keyword matching" and write the result "to suppression in real time." That sentence is not in Retell's product documentation. It is not in anyone's.
The sharpest version sits in GoHighLevel's own Voice AI compliance article. It confirms in a plain question and answer that the platform does not verify consent before outbound AI calls, then explains that the AI disclaimer setting controls how the agent communicates opt-out language at the start of the call. The agent is configured to read out how to opt out. Nothing is configured to catch the reply.
Four moves before your next outbound campaign
None of this needs a new vendor. All four are configuration in the stack you already pay for.
The bottom line
A spoken revocation is effective the moment it is said, whether or not your stack noticed. The gap between someone saying take me off your list and your dialler learning about it is not a paperwork detail. It is the interval in which every further call is a separate violation carrying $500 in statutory damages, which a court may raise to as much as $1,500 for willful conduct, and your own recording is the evidence.
The fix is one extraction field and one lookup. I have built AI calling for 200+ businesses and have yet to find it wired by default in any of them. Nobody ships it because it is the only feature in an AI calling stack whose job is to make the stack call fewer people.
My earlier piece on what GoHighLevel checks before an AI call covers the consent side, and the disclosure rules your script must satisfy covers the opening. This is the other end: what happens after somebody says no.