How often should you call the same person?

Every outbound team discovers the same thing: most people do not answer the first time. Call once and discard, and you throw away a list you paid for. So you retry. And then the question becomes how much retrying is diligence and how much is harassment, because there is a line and it is not marked.

Most conversations about this focus on the retry logic itself, on delays and schedules. That is the easy half. The half that matters is the stopping logic. Eager retries plus vague limits is how a business calls one person eleven times in a week. Nobody decided to do that. It just happened.

Not every miss means the same thing

The first mistake is treating every unsuccessful call as one category. It is not. A busy signal, a ring-out and a failed connection are three different pieces of information about the person you are trying to reach.

A busy signal means someone is there, on the phone, right now. That is the most promising outcome on the list, and it deserves a short delay: minutes, not days. A ring-out means they are away from the phone, or ignoring an unknown number. Waiting a few hours and trying a different time of day beats calling straight back. A carrier failure often means the number itself is wrong, and repeating it quickly just repeats the failure.

So retry policy should be set per outcome, each with its own delay and its own attempt cap. In TelVox each outcome is its own record with its own rules. A busy signal can come back in fifteen minutes. A failed call can wait much longer, or retire for good.

What stops it

Here is the part to interrogate in any system you are evaluating, including ours. Retry rules are trivially easy to write. Guarantees that they terminate are not.

TelVox handles this by being safe when nobody has decided otherwise. If a lead's outcome or disposition has no matching retry rule, that lead retires. It does not fall through to a default that keeps calling. It does not loop forever because someone forgot a rule. The absence of an instruction means stop, not continue.

Attempt caps are also checked twice. Once when the calling queue is filled, and again when the call is claimed for dialling. Two checks sounds like one too many. But leads can be revived in bulk, moved between campaigns, or re-queued by a rule. Every one of those paths has to respect the same limit. Checking only at queue-fill leaves gaps that revival paths can walk through.

There is also a global kill switch. It stops all recycling at once, for the day you need everything to stand still while you work out what a rule is doing.

A retry system should be judged by its stopping conditions, not its scheduling. Anyone can build something that calls again. The engineering is in the guarantee that it eventually will not.

Setting a policy you can defend

There is no universal correct number of attempts. It depends on your sector, your relationship with the person, and what you are calling about. A missed delivery is a different conversation from a cold sales call. The rules that apply to you may be stricter than anything a dialer enforces by default.

What does generalise is the shape of a defensible policy:

• Write a maximum attempts figure per campaign, and be able to say why that number.
• Vary delay by outcome, so a busy signal and a dead number are not treated alike.
• Spread attempts across different times of day rather than repeating the same slot.
• Cap attempts per week as well as in total, so six tries are not compressed into one afternoon.
• Make a request to stop take effect immediately, on calls already queued.
• Review the policy against complaints, not just against connect rates.

That last point is the one teams skip. Connect rate tells you whether the policy is working for you. Complaints and opt-outs tell you whether it is working for the person you called. That signal comes first. Then your number gets labelled, your brand gets reported, and your regulator takes an interest.

Reviving a list, carefully

Eventually someone asks whether the retired leads from three months ago can be brought back. Sometimes they should be: circumstances change and an old no is not a permanent one. But bulk revival is the easiest way to blow through a contact policy. It re-queues thousands of records that already carry attempt history.

Two safeguards make it survivable. Attempt caps have to apply to revived leads exactly as they applied the first time, which is why the dial-time check matters. And a dry run should show you exactly which leads would come back, before anything changes. Then you decide on a list you have seen, not a number you assumed.

Work a list properly and it will produce far more than one pass ever does. The difference between working it and wearing it out is not effort. It is the limits you set before you start, and whether the system enforces them when nobody is watching.