How Many Times Should an AI Voice Agent Call a Dormant Lead?
Published ยท Last updated
For insurance agencies working under Farmers Insurance and Allstate branding, Aidan's database reactivation, lead qualification and Ricochet 360 sync workflows are built to turn a dormant book into a measurable pipeline, but only when the cadence policy behind the dialer is sound. The fastest way to damage a book is to let an automated system keep dialing people who have already answered, booked, or asked to stop.
Your dialer is not the problem. The policy behind it is. Compliance gets a dormant contact legally callable, but it says nothing about whether calling them is wise. That decision belongs to cadence: how many attempts a contact receives, how far apart those attempts sit, when during the day your AI voice agent is allowed to dial, and which signals trigger an immediate stop.
This guide walks through the policy in order: why cadence, not compliance, decides whether a dormant contact is worth calling, what the TCPA requires before your agent dials, then four steps covering a fixed attempt ceiling, widening gaps, a defined daily calling window, and automatic suppression triggers. We close with re-engagement handling, common cadence mistakes, how Aidan runs this on your book, and answers to frequent questions.
Why Cadence, Not Compliance, Decides Whether a Dormant Contact Is Worth Calling
Compliance and cadence answer different questions. Compliance asks whether a contact is legally callable; the FCC has confirmed the TCPA covers AI-generated voices. Cadence asks whether calling now is wise. An agency can pass the first test and still burn goodwill with a pattern that reads as pursuit.
Define your segments before choosing numbers. A dormant contact has not been reached in a defined period. A lapsed contact has cancelled or stopped paying. Different messages, often different ceilings. Our AI voice reactivation workflow maps one full cycle.
Automation raises the stakes. An AI agent can work an entire book in a week, which is exactly how an unattended sequence keeps dialing people who already answered, already booked, or already asked to stop.
Four decisions carry the policy: how many attempts, how far apart, inside which hours, and what triggers an immediate stop. Everything else follows. Decide up front that the record, not the dialer, is the source of truth. Every attempt and disposition writes back to your CRM so the policy can be audited later.
What the TCPA Requires Before Your Agent Dials a Dormant Contact
Consent first. 47 CFR 64.1200 requires prior express consent for autodialed calls or artificial/prerecorded voice, unless emergency/exemption applies. AI outbound voice agents generally fall in scope.
Revocation ends calls. Under the FCC's TCPA Consent Order, if a called party revokes by any reasonable method, the caller may not place more robocalls or robotexts (TCPA Consent Order DA-25-312A1). The one-campaign-to-all-campaigns rule was delayed by waiver, first to April 11, 2026 and then, under a January 2026 FCC order, to January 31, 2027 (FCC extends limited waiver); verify the operative date before relying on either, as subsequent FCC orders may affect the timeline. Run one cross-campaign suppression list either way.
Federal rules set no general attempt limit for dormant-contact outreach.
Confirm permitted hours in 47 CFR 64.1200 before writing calling times. Covers federal TCPA only; state insurance rules vary.
Before configuring outbound agents, verify consent handling and CRM write-back practices with your compliance counsel.
Step 1: Set a Fixed Attempt Ceiling per Contact
Set one number and enforce it everywhere. Treat the ceiling as total attempts per contact per sequence, not per campaign. A contact on the win-back, cross-sell and annual review lists should not receive three separate ceilings.
For dormant book outreach, six to eight attempts across a defined cycle is a reasonable starting range to consider. Frame it as agency and Aidan policy grounded in intrusion risk and call capacity, not as a regulatory limit, because no federal regulation sets a general attempt cap.
Count every dial. A no-answer, busy signal and voicemail drop are all attempts. Excluding them makes the ceiling meaningless.
When the ceiling is hit, send the contact to a cool-off period. Re-entry then requires a deliberate human decision, never an automatic restart.
Log the attempt count where the next campaign can see it. If attempts live only in a vendor dashboard, the next sequence starts from zero. Treat attempts as campaign data and measure their ROI against booked appointments instead of letting a dashboard hide them. With that ceiling fixed, the next decision is spacing.
Step 2: Widen the Gaps as Attempts Accumulate
Your attempt ceiling only holds if the spacing between dials holds too.
Consider opening tight and widening, for example, day 1, day 3, day 7, day 14, then day 30. That front-loads reachability, then pulls back before the contact feels pursued. Treat that spacing as your policy choice, not an industry standard, and explain the rationale to your team. Early attempts test whether the number reaches a live person; widening gaps keep the contact inside a live re-contact window without spending capacity on someone who has ignored several dials.
Vary the time of day across attempts. Dialing at the same time on every attempt is unlikely to improve answer rates and trains people to recognize your number. Rotate across your approved calling window instead.
Ban same-day double dialing: one attempt per contact per day keeps the sequence legible and removes a common complaint trigger in practice.
Bake the schedule into the agent build. A gap pattern that depends on someone remembering it will not survive a busy week, nor will the questions that decide whether a contact counts as qualified.
Step 3: Define a Daily Calling Window

Before writing policy hours, pull the current text of 47 CFR 64.1200 and confirm the federally permitted calling times. Then set your own window comfortably inside that limit; a legal call at an awkward hour still costs you the contact.
Narrow it further. Two blocks, typically mid-morning and early afternoon, when prospects are more likely to be reachable, beat dialing every permitted hour.
Dial in the contact's local time, not your agency's. Store and verify each contact's time zone; area codes do not reliably reflect where a mobile user is located.
Block the days that invite complaints. Sundays and major holidays are generally low-yield for dormant-book outreach and belong in the policy as exclusions.
Keep the window and the ceiling working together. A wide window combined with a high attempt ceiling is the fastest way to look like a nuisance, even when every individual call is legal. Fix the window before you build the triggers that stop it.
Step 4: Build Automatic Suppression Triggers
A daily window still leaves one gap: contacts who already answered, booked, or asked to stop. Suppression triggers close it.
Stop on any revocation. Under the FCC's consent-revocation rule, any reasonable method of revocation ends the caller's right to place further robocalls. As a practical matter, this means your system should be configured to treat voice requests, text replies and written requests as triggers, but confirm the specific methods with your compliance counsel. The stop must fire automatically, not sit as a note waiting for someone to action it. A revocation in one campaign should silence the contact everywhere, so run one cross-campaign suppression list every caller checks.
Stop on a live answer. Once a human picks up, the contact is engaged. Remove them from the automated sequence so it cannot keep dialing in parallel.
Stop on a booked appointment. Suppress the contact the moment a meeting is set, and hold that suppression until the appointment outcome is recorded.
Add operational triggers too: wrong number, disconnected line, deceased or estate, do-not-call requests, and any national or state do-not-call match. Write every suppression back to Ricochet 360 so every other caller sees it.
What to Do When a Dormant Contact Re-Engages Mid-Campaign
Suppression handles the contacts who asked you to stop. Re-engagement is the opposite event.
Move them out of the sequence immediately. A returned call, a reply, an inbound agency call, or a website enquiry means the contact is live, and live contacts do not belong in a dormant cadence.
Re-verify consent and channel before the next automated call. Consent given for the original transaction may not cover a new purpose, so check the record.
Hand the context to a person. The producer should receive the attempt history, the call disposition, and any call summary, so the human conversation does not start at zero.
Treat the re-engaged then quiet case deliberately. If a contact engages and disappears, start a new cycle at the top of the schedule with a fresh ceiling, not the old count.
Record the reason for re-engagement in the CRM. A renewal-driven return behaves differently from a claim-driven one, so the next sequence should reflect it.
Common Cadence Mistakes That Damage the Book
A solid re-engagement path still fails if the cadence around it repeats five common errors.
Compliance as strategy. Legally callable is not the same as welcome. Agencies that stop at the legal box keep dialing people who no longer want to hear from them.
Per-campaign attempt counts. As Step 1 established, count attempts per contact across all lists, not per campaign.
Suppression trapped in one campaign. As Step 4 established, one shared suppression list checked by every caller is the only way to ensure an opt-out in one sequence silences the contact everywhere.
Identical call times. As Step 2 established, rotate attempts across the approved window rather than dialing at the same time every day.
No write-back. As Step 1 established, attempts, opt-outs and outcomes belong in Ricochet 360, where the next sequence sees them rather than restarting from zero.
Clean up these five, and the policy holds at scale.
How Aidan Runs This Cadence Policy on Your Book
Those mistakes share one root cause: a cadence policy that lives in a document rather than in the dialer. Aidan builds the policy into the agent itself.
Aidan's AI voice agent calls contacts in the agency's database, qualifies leads and reactivates dormant and lapsed contacts. That reach is precisely why the attempt ceiling, gap schedule, calling window and suppression triggers are configured for each client instead of left at defaults.
Results sync straight back to Ricochet 360, so attempt counts, dispositions and suppressions sit in the same system your producers already open every day. After every successful call, Aidan provides a call summary, giving the producer context before the follow-up. Aidan connects to your CRM to pull contacts in and write results back, so the ceiling counts dials across the whole database rather than one exported list. Each agent is built out with the specifics of each client, so the sequence reflects your compliance requirements and state-level rules alongside the federal baseline.
Farmers and Allstate agency owners can use Aidan to work the database they already own.
Frequently Asked Questions on Attempts, Gaps and Stop Rules
Four questions recur.
Does a dormant contact's old consent cover an AI voice call? Consent must cover calls using an autodialer or artificial or prerecorded voice. Confirm the original consent captured autodialer and prerecorded-voice calls, and that state rules allow them.
Is there a legal limit on how many times I can call? No federal rule sets a general attempt cap for dormant outreach; set your ceiling as policy and frame it as an agency decision grounded in intrusion risk and call capacity.
What if a contact revokes consent in one campaign? As Step 4 established, any reasonable revocation method must end robocalls and one suppression list should apply across all campaigns; verify the current operative date for the cross-campaign revocation rule with your compliance counsel.
How does the daily window interact with the attempt ceiling? They are separate limits; both apply. A contact can be inside the window and still suppressed for hitting the ceiling or opting out.
Conclusion: Put the Ceiling, Window and Stop Rules in Writing
A cadence policy only works if it is written down and enforced by your systems. Start with the ceiling: set a fixed number of attempts per contact, not per campaign, and count every dial, including no answers and voicemails.
As Steps 2 and 4 established, widen gaps as attempts accumulate, rotate the time of day within your approved window, and run suppression automatically from one cross-campaign list.
Write every attempt and disposition back to Ricochet 360. Policy enforced by memory fails during a busy week; policy enforced by your CRM holds.
Before you rely on any specific revocation deadline, verify it, the April 11, 2026 date was the prior deadline, which, as of a January 2026 FCC order, has been further extended to January 31, 2027; verify the current date before relying on either, and confirm your state insurance rules too. Federal guidance does not cover state-specific requirements.
Aidan's AI voice agent can run this cadence across your agency database, qualify the leads it reaches and sync the results straight back to Ricochet 360, turning the rules you just wrote into the default behavior of every call.
Frequently asked questions
Is a dormant contact legally callable just because the contact was once compliant?
Compliance and cadence answer different questions. Compliance asks whether a contact is legally callable, while cadence asks whether calling now is wise. An agency can pass the compliance test and still burn goodwill with a pattern that reads as pursuit.
Is there a federal limit on how many times I can call a dormant contact?
No. The post says federal rules set no general attempt limit for dormant-contact outreach. The attempt ceiling is a policy choice; the post suggests six to eight attempts across a defined cycle as a reasonable starting range to consider, grounded in intrusion risk and call capacity rather than regulation.
What counts as an attempt toward the ceiling?
Every dial counts. A no-answer, busy signal and voicemail drop are all attempts, and excluding them makes the ceiling meaningless. Attempts should be counted per contact across all campaigns, not per campaign.
How should the gaps between attempts be spaced?
The post suggests opening tight and widening, for example day 1, day 3, day 7, day 14, then day 30. This front-loads reachability and then pulls back before the contact feels pursued. The post presents this as a policy choice rather than an industry standard. It also recommends varying the time of day across attempts and banning same-day double dialing.
What should trigger an automatic stop on a dormant contact?
Stop on any revocation, a live answer, or a booked appointment. Operational triggers include wrong number, disconnected line, deceased or estate, do-not-call requests, and any national or state do-not-call match. Every suppression should be written back to Ricochet 360 and applied across all campaigns through one cross-campaign suppression list.