No Answer Isn't a Plan: Write a Redial Rule Before You Recycle the List

By Dan Hanna, founder · November 8, 2026 · About us

I watch the same two mistakes on calling floors, sometimes in the same week.

On one team, a no-answer means the lead is dead. Two or three attempts, then the list gets dumped and somebody buys a new one. On the next team, the same names get hammered every morning until the prospect blocks the number. Neither floor wrote down what should happen after the phone doesn't get picked up.

A no-answer is not a strategy. It's an outcome. What you do next is the strategy, and if that next step lives in each agent's head, you don't have a rule. You have vibes.

What a redial rule actually is

A redial rule is a written answer to four questions, before anybody starts dialing:

What counts as an attempt?
How many attempts does this contact get in this cycle?
How much time has to pass before we try again?
What happens when we hit the cap: rest the record, re-verify it, or take it off the list?

If you can't answer those without a meeting, you don't have a cadence. Habits drift the minute two agents disagree. I'm not going to hand you a magic attempt count. Pick a number, write why, watch it for two weeks, and change it if your own results say so.

First: define the attempt

This is where floors quietly lie to themselves. A no-answer, a voicemail, a receptionist who said the person wasn't in, and a live “call me Thursday” are not the same event. Lump them together and your “we tried them six times” report is mush.

Here's the split I use:

A dial attempt is any outbound call that rang or reached something: no answer, busy, voicemail, gatekeeper, or a live conversation.
A conversation is a live talk with a human who could actually move the sale. Gatekeepers and wrong numbers are information, not conversations.
A promised callback is a commitment, not another try on the cadence. If they asked you to call Thursday at 2:00, that time outranks the schedule. Label it with an owner, date, time, time zone and reason. We covered that in Call Dispositions.

This post is about everyone else: the people who didn't pick up and didn't ask for a time.

The testFrom the floor
Write the definitions so two agents would score the same call the same way.

Then: cap it, space it, and say what happens after

Set a cap per cycle. A cycle is one pass through the list before the record needs a rest or a cleanup. Write the maximum dial attempts a contact gets in that cycle. A fresh inbound lead may deserve more tries than a year-old purchased list, but everybody should work from the same written number.

Set the spacing. Back-to-back no-answers on the same number in the same hour are usually noise, not persistence. Decide the minimum gap after a no-answer, a voicemail and a gatekeeper.

Write the after-cap action. When a contact hits the limit with no conversation, rest it and bring it back after a written cooling period, re-verify the number, name and fit before another cycle, or remove it. “We'll just keep them in the hopper” is how dead names clog a good list.

If you already sort lists by freshness, verification and fit, let that ranking change the cap and the spacing. Your filler list should not get the same treatment as someone who raised their hand this week.

Put the history on the contact, not in somebody's memory

A redial rule fails the minute the next agent can't see what already happened. Every attempt should leave the outcome, a short note if needed, the attempt count for this cycle, and the next allowed date, or a scheduled callback if they asked for one. If that lives in a notepad or “I think Sarah called them yesterday,” the next agent will skip a good lead or redial someone who was just tried.

Non-negotiableCompliance
A cadence never overrides a do-not-contact request. If they ask you to stop, you stop, you record it, and they come out of the campaign. Same for numbers you've flagged as wrong. None of this is legal advice. The calling and messaging rules that apply to your business are still yours to follow.

Watch the numbers you're dialing from, too. Overworking a caller ID is a different problem from overworking a lead. We walked through that in Protect Your Caller ID.

A 15-minute write-up you can finish today

Answer the four questions, write who can override the rule (promised callbacks always win), and name the fields you'll look at on the contact: last outcome, attempt count, next date. Then test it for two weeks without changing anything else. Track attempts, conversations and next steps booked. If the cap is too tight, you'll see conversations you never reached. If it's too loose, the same names will chew hours and numbers. Adjust one piece at a time.

Where Straton fits

I built Straton for teams that live on the phone, so I'll be direct about what the product does here.

When an agent makes a call, the outcome, notes, callback and next task save to the same contact record they called from. Campaigns stay tied to their lists, so a recycle decision can mean taking someone out of this campaign instead of losing them in a pile. Agents call from the same workspace where you manage lists, scripts, dispositions and outcomes, which is what makes a written cadence usable instead of theoretical.

What Straton won't do is invent your redial rule. You decide what an attempt is, how many you allow, and what happens after the cap. We'll help you set that up around your real lists, but the judgment is yours.

If you want the CRM side, Straton Genesis starts at $49.99/mo with unlimited contacts. For the dialer side (campaigns, outcomes and how we'd wire your recycle rules into a live calling setup) the honest next step is a walkthrough where we look at your floor together.

Grab the Redial & Recycle Rules Worksheet

I put the four questions, the attempt definitions, spacing, after-cap actions and a two-week test log on one page. Print it, fill it in with whoever owns your campaigns, and run it before you load tomorrow's list.

Download the Redial & Recycle Rules Worksheet

Do this before tomorrow's first campaign

Write what counts as an attempt. Cap the cycle. Set the spacing. Say what happens when a name hits the limit.

Want help turning that into a working setup? Book a walkthrough and bring one list you're about to recycle. We'll map outcomes, next dates and campaign rules with you.