Lesson objective
Design how an intake automation detects consent revocations and do-not-call requests from any channel, applies them everywhere, and keeps its national registry data within the 31-day window.
Plain-language explanation
Why this matters now
Lesson 1 built the record of who agreed to be contacted. This lesson builds the other half: who has told the brokerage to stop, and who has told the country to stop. An automation that sends faster than a person also fails faster. A revocation missed by one agent affects one consumer; a revocation missed by an automation affects every sequence that consumer is in, on every channel, until someone notices.
The binding rules:
- Law / rule (federal, 47 CFR §64.1200(a)(10)): a called party may revoke consent "to receive calls or text messages" by any reasonable method. Replies such as "stop" or "unsubscribe" are reasonable per se. Revocations must be honoured within ten business days.
- Law / rule (federal, 47 CFR §64.1200(d)): anyone making telemarketing calls to residential subscribers must maintain a written do-not-call policy, train personnel, and record and honour do-not-call requests.
- Law / rule (federal, 47 CFR §64.1200(c)(2)): telephone solicitations to numbers on the national do-not-call registry are barred, and registrations "must be honored indefinitely" unless cancelled or removed. The safe harbour requires, among other things, written procedures, trained personnel, a recorded internal do-not-call list, and use of a registry version obtained no more than 31 days before the call.
- Law / rule (federal, 47 CFR §64.1200(f)(5)): an established business relationship for telephone solicitations is a purchase or transaction within 18 months, or an inquiry or application within three months, not previously terminated. A seller-specific do-not-call request ends it.
- Law / rule (federal, 47 U.S.C. §227(c)(5)): a person who receives more than one call within any 12-month period by or on behalf of the same entity in violation of the do-not-call regulations may sue for up to $500 per violation, up to treble if wilful or knowing. It is an affirmative defence that the defendant "has established and implemented, with due care, reasonable practices and procedures" to prevent such calls.
- Professional guidance (FTC, Q&A for Telemarketers & Sellers About DNC Provisions in the Telemarketing Sales Rule, edited January 2025): sellers and telemarketers required to use the registry "must synchronize your lists with an updated version of the registry at least every 31 days." A consumer's specific do-not-call request must be honoured even if an established business relationship exists. An inquiry-based relationship lasts three months; one based on a purchase, rental, lease or financial transaction lasts 18 months from the last payment, transaction or shipment. The FTC states violators may face fines of up to $53,088 per violation, and each call may be a separate violation; that maximum is adjusted for inflation each year. Registry data for up to five area codes is free; beginning 1 October 2025 the annual fee was $82 per additional area code, up to $22,626, and those fees may change from 1 October 2026.
The FTC's Telemarketing Sales Rule and the FCC's TCPA rules overlap, and both can apply to a brokerage's outbound calls. State do-not-call lists and state calling laws are separate and were not researched here.
A question to sit with
A consumer replies "please stop texting me" to one agent's number. How many of your systems would still contact that consumer tomorrow, and which would be the last to find out?
What goes wrong
Only the keyword counts. The texting platform suppresses "STOP" but not "please stop texting me", "wrong person, remove me" or "I bought already, no more messages". The rule says any reasonable method.
The revocation stays in one system. The texting platform suppresses the number, but the CRM's drip campaign, the dialer and the agent's own sequence still hold it.
A spoken request never reaches the list. A consumer tells an agent on a call to stop calling. The agent means to note it and does not.
The established business relationship is treated as permanent. A consumer enquired about a listing a year ago and the automation still treats them as a warm lead for telephone solicitation.
The registry file goes stale. Someone downloaded the registry data for the brokerage's area codes once, at launch.
The ten-day limit is treated as the target. Ten business days is the outer limit for honouring a revocation. An automation can apply it in seconds, and should.
The practical answer
Keep one suppression list, checked at send time by every system. The CRM, the texting platform, the dialer and any marketing tool read the same brokerage-wide do-not-contact list immediately before sending. A system that cannot check the list at send time does not send. This design is an AI Coalition Network recommendation; the internal do-not-call list and its recording are required by §64.1200(d) for telemarketing to residential subscribers.
Detect revocations from every channel. The automation's job here is to catch and route, never to decide a consumer did not really mean it.
| Channel | What the automation does | Who confirms |
|---|---|---|
| Text reply with "stop", "unsubscribe" or similar | Suppress immediately; these are reasonable per se | No confirmation needed |
| Text or email in other words that may be a revocation | Suppress immediately and flag for review | Licensee reviews; only counsel's policy can reverse |
| Spoken request on a call | Agent records it in one tap from the call screen | The agent, the same day |
| Web or email request to the brokerage | Suppress and acknowledge | Compliance owner |
| Request to a licensee's personal number or app | Licensee forwards to the list the same day | Licensee, under written policy |
Apply the established business relationship as a clock, not a label. Store the date and type of each relationship event. An inquiry opens a three-month window; a transaction opens an 18-month window. A seller-specific do-not-call request closes the window immediately, whatever its type.
Synchronise the registry on a schedule shorter than 31 days. The registry data used for a call must have been obtained no more than 31 days before the call. If the brokerage last downloaded on 20 August, the file can support calls up to and including 20 September, 31 days later. Build a margin: download every 25 days and block every telephone solicitation automatically if the file in use is older than 31 days. Record each download date, which is part of the evidence both the FCC safe harbour and the FTC safe harbour ask for.
Write the policy the rules ask for. §64.1200(d) requires a written do-not-call policy, trained personnel and recorded requests for telemarketing to residential subscribers. The automation helps keep the record, but the policy, the training and the named owner are people's work.
Keep the human in the loop where judgement is needed. When a reply is ambiguous ("not now, maybe in spring"), the automation suppresses and a licensee decides whether and how to follow up under counsel's policy. The automation never infers consent back.
An AI output is never proof. If a tool classifies a reply as "not a revocation", that label is a suggestion; the default is to suppress.
Remember this
- Consumers may revoke by any reasonable method; "stop" and "unsubscribe" are reasonable per se, and ten business days is the outer limit.
- Keep one brokerage-wide suppression list and check it at send time in every system.
- An inquiry-based business relationship lasts three months; a specific do-not-call request ends any relationship.
- Registry data must be no more than 31 days old at the time of the call; download on a shorter cycle and block when stale.
- Test revocation end to end each quarter and record it.
Real estate example
Copperline Properties, a fictional brokerage, runs texting through one platform, a drip campaign through its CRM and a dialer used by its inside sales team. A consumer, Nadia Kerr, enquired about a fictional condominium on 4 March. On 18 March she replies to an agent's text: "Found a place, please take me off your list." The texting platform does not recognise the words, so it keeps her number active. On 2 April the CRM drip sends her a market update, and on 9 April the dialer calls her. She complains. The compliance owner, Ruth Salgado, reviews the design. Three faults emerge: each system kept its own list; only keywords were detected; and the dialer used registry data downloaded on 1 February, which was 67 days old on 9 April (28 days to 1 March, 31 more to 1 April and 8 more to 9 April). Ruth's redesign creates one brokerage-wide suppression list read at send time by all three systems. Any reply that may be a revocation suppresses the number immediately and goes to the assigned licensee to review. Agents record spoken requests with one tap from the call screen. Registry data is downloaded every 25 days, and the dialer blocks all telephone solicitations if its file is older than 31 days. The inquiry-based business relationship is stored as a clock: Nadia's enquiry on 4 March opened a three-month window, but her request on 18 March closed it at once. Ruth writes the do-not-call policy, trains the inside sales team and runs the first end-to-end test from a test number in plain words. All three systems pass. She records the test in the register entry, and the supervising broker signs it.
Responsible-use warning
Do not let each system keep its own do-not-contact list, and do not detect only keywords. A revocation in plain words is still a revocation, and a number suppressed in one tool but live in another will be contacted again. Never let an automation decide an ambiguous reply was not a revocation, never treat ten business days as the target, and never call with registry data older than 31 days, whatever the campaign calendar says.
Human-review requirement
The compliance owner named in the register writes the do-not-call policy, trains staff, and runs and records the quarterly end-to-end test. Counsel confirms the policy and any state do-not-call or calling-law requirements. The supervising broker approves the design and signs the test record. Each licensee records spoken requests the same day and reviews ambiguous replies routed to them, never reversing a suppression without the written policy and a named approver.
Practical exercise
Use fictional systems, consumers and dates only.
- List every system in a fictional brokerage that can call, text or message a consumer, including licensees' own apps.
- Draw how a single suppression list would be read by each system at send time, and mark any system that cannot do so.
- Write ten plain-word replies a consumer might send, and mark which the automation should treat as possible revocations. Explain why the default is to suppress.
- Design the one-tap record for a spoken request, and say where it goes.
- For three fictional consumers, record the relationship events and dates, and show whether an established business relationship is open on a chosen date.
- Given a registry download on a fictional date, calculate the last date that file can support a call, and set a download cycle with a margin.
- Draft the headings of a written do-not-call policy that satisfies the elements in §64.1200(d).
- Design the quarterly end-to-end test and the record it produces.
- Write the questions you will ask counsel about state do-not-call lists and calling laws.
- Name the owner of each step and the supervising broker who approves the design, and set the date of the first end-to-end test.
- Note which of your systems would fail the test today and what must change before launch.
Knowledge check
-
How may a consumer revoke consent under §64.1200(a)(10), and how fast must it be honoured?
Answer guidance: By any reasonable method; replies such as "stop" or "unsubscribe" are reasonable per se. Revocations must be honoured within ten business days, which is the outer limit, not a target.
-
How often must registry data be synchronised, according to the FTC's Q&A and the FCC safe harbour?
Answer guidance: At least every 31 days. The FCC safe harbour requires using a registry version obtained no more than 31 days before the call, and the FTC says sellers must synchronise at least every 31 days.
-
How long does an inquiry-based established business relationship last, and what ends it early?
Answer guidance: Three months from the inquiry. A consumer's seller-specific do-not-call request ends it immediately, and the FTC says such a request must be honoured even where a relationship exists.
-
What affirmative defence does §227(c)(5) offer, and how does this lesson help a brokerage show it?
Answer guidance: That the defendant established and implemented, with due care, reasonable practices and procedures to prevent such calls. A written policy, trained staff and a recorded end-to-end revocation test are evidence of that.
Sources and further reading
- Federal Communications Commission (via eCFR, Office of the Federal Register) — 47 CFR § 64.1200 Delivery restrictions. Accessed 2026-09-15.
- Federal Trade Commission — Q&A for Telemarketers & Sellers About DNC Provisions in TSR. Accessed 2026-09-15.
- United States Congress (via Cornell Legal Information Institute) — Telephone Consumer Protection Act, 47 U.S.C. § 227: Restrictions on use of telephone equipment. Accessed 2026-09-15.
- AI Coalition Network — Certification Educational Standard: Human Review of AI-Assisted Professional Work. Accessed 2026-09-15.