When Repeated Prospect Calls Become Harassment Is Not a Number

TL;DR: There is no call count that turns prospect calls into harassment, and chasing one is why sales teams get this wrong. For business-to-business calls the single federal provision that uses the words annoy, abuse, or harass, 16 CFR 310.4(b)(1)(i), does not apply at all, because 16 CFR 310.6(b)(7) exempts calls between a telemarketer and a business to induce that business to buy. Only two carve-outs survive that exemption, 310.3(a)(2) and 310.3(a)(4), and both are about misrepresentation, so the FTC’s concern with your outbound calling is whether you lied, not how often you dialed. What does bind you is the FCC side, which is keyed to the line rather than to the conversation. 47 CFR 64.1200(c)(1) bars telephone solicitation to a residential subscriber before 8 a.m. or after 9 p.m. local time at the called party’s location, not yours. 47 CFR 64.1200(d) requires a written do-not-call policy available on demand, trained personnel, caller identification including a real callback number that is not a 900 number, a recorded request honored within a reasonable time not to exceed ten business days, and retention of that request for five years. 47 CFR 64.1200(e) extends both paragraphs to wireless numbers, and a prospect’s mobile is the number most outbound teams dial. 47 CFR 64.1200(a)(10) adds that consent can be revoked by any reasonable method and that you may not designate an exclusive means of revocation, so a verbal stop on a live call counts and a compliance web form is not a gate you get to install. The practical answer: the line is not attempt number seven, it is the moment someone says stop, plus an hour boundary set by a clock you do not control.

Persistence is the job, and every sales leader has at some point told a rep that the deal was lost at attempt three because the rep quit at attempt two. That advice is fine until someone asks the obvious follow-up question. Where does it stop?

Most teams answer with a number. Six attempts, eight, twelve over a quarter. The number is reassuring because it is countable and because it fits in a cadence builder, which is the same reason it keeps getting written into policy. It is also the wrong shape of answer. Why? Because not one of the rules that could reach your outbound calling measures attempts.

This article is general business information about how those rules are written, not legal advice. Scope depends on your markets, your call types, and who you are calling, and a lawyer should decide what applies to you.

No call count turns prospect calls into harassment

Ask ten sales managers how many calls is too many and you will get ten numbers and zero citations. Where do those numbers come from? Not from the rules, because the rules do not contain them.

Think about what a count would have to ignore to work. One call that misrepresents what your product costs is a problem on the first dial. Nine well spaced calls to a prospect who keeps answering and keeps engaging are not. A count treats those the same. So a count cannot be the test.

So what do the rules actually measure? Something narrower, and more awkward for a cadence builder. Intent in one place, the hour of the day in another, and whether a request was honored in a third. None of those is a quantity. They are conditions, and a condition either holds on this call or it does not.

So the useful question is not how many. It is which of the three regimes reaches this call, and what each one is actually counting.

The federal harassment rule does not reach most B2B prospect calls

Here is the part that surprises people, including people who have sat through compliance training. The Telemarketing Sales Rule contains the only federal provision that talks about harassment in these terms. 16 CFR 310.4(b)(1)(i) makes it an abusive practice to cause “any telephone to ring, or engaging any person in telephone conversation, repeatedly or continuously with intent to annoy, abuse, or harass any person at the called number.” That is the rule. Now watch who it covers.

You can see why teams anchor on it, because it is the rule the question is reaching for and it uses the exact words people have in mind. It also does not apply to a normal business-to-business sale.

16 CFR 310.6(b)(7) exempts “telephone calls between a telemarketer and any business to induce the purchase of goods or services or a charitable contribution by the business.” The exemption is broad, and it carries exactly two carve-outs, both of them narrow: the requirements of 310.3(a)(2) and 310.3(a)(4) still apply, and calls inducing the retail sale of nondurable office or cleaning supplies are not exempt.

So what survives? 310.3(a)(2) prohibits misrepresenting material information in the sale of goods or services, including total cost and any material restriction or condition. 310.3(a)(4) prohibits making a false or misleading statement to induce any person to pay for goods or services. Both are about lying, and neither is about volume.

That is the whole shape of the FTC’s interest in your outbound team. The exemption lets you call a business repeatedly, but it does not let you lie to it. A rep who dials a prospect nine times is outside the pattern-of-calls rule; a rep who dials once and invents a discount that expires tonight is not.

Two cautions before anyone relaxes. The exemption is defined by the call, so it covers calls to a business to induce that business to buy, and selling to a sole proprietor’s personal line is a fact question rather than a label you assign yourself. And an exemption from the FTC’s rule is not an exemption from the FCC’s, which is where the rules that actually constrain your dialer live.

What binds repeated prospect calls is the clock, not the count

47 CFR 64.1200(c)(1) prohibits initiating a telephone solicitation to a residential telephone subscriber “before the hour of 8 a.m. or after 9 p.m. (local time at the called party’s location).”

Read the parenthetical twice. Local time at the called party’s location. Not your rep’s local time, not your office’s time zone, and not the time zone your CRM defaulted to when the record was imported. So whose clock is your dialer using right now?

Walk the queue and ask where this breaks. The failure mode appears immediately. A rep in Los Angeles runs a late block and starts dialing at 6:15 p.m. Pacific to clear the list before the end of the day. That is 9:15 p.m. in New York. The list was sorted by lead score, by account tier, or by whatever the sequencer decided, and the dialer advanced through it without ever asking what hour it was where the phone was ringing.

Nobody made a decision to call that prospect late, and that is exactly the point. The dialer advanced, the record happened to be East Coast, and the rule is written about the recipient’s clock rather than about anyone’s intent.

This is a routing problem with a routing fix. The time zone has to be a field on the record, it has to be populated, and the dialer has to refuse. If the enforcement lives in a rep remembering to check, it is not enforcement. So what does your system do at 6:15 p.m. Pacific with an East Coast record in the queue? If the answer is that it dials, you already know what to fix.

The stop request is the real line for repeated calls

47 CFR 64.1200(d) is the paragraph that does the most work. Almost nobody quotes it. It requires anyone making calls for telemarketing purposes to a residential subscriber to maintain an internal do-not-call list, and it sets minimum standards for that list. Those standards are where most teams actually fail.

So what does the paragraph actually require? A written policy available on demand under (d)(1), and trained personnel under (d)(2). Then (d)(3) does the real work. The request is recorded and the number placed on the list at the time the request is made, and honoring it has to happen within a reasonable time that “may not exceed ten (10) business days from the receipt of such request.” Under (d)(4), the called party gets three things: the name of the individual caller, the name of the entity, and a telephone number or address, and that number may not be a 900 number or any other number charged above normal transmission rates. Under (d)(6), the record is kept and the request honored for five years.

Four of those six are not about the call at all. They are about whether your organization has a system. A written policy available on demand means available when someone asks, not written after someone asks. And five years? That outlives the rep, the sequence, the vendor contract, and usually the CRM migration.

Ten business days is the one people misread as generous. It is a ceiling with “reasonable time” sitting in front of it, and a ceiling is not a target. It also spans two weekends. That sounds like room until you notice what has to happen inside it. The request has to reach every system capable of starting a call. A note in the CRM does not stop a sequencer, an imported list does not read the CRM, and a partner calling on your behalf is calling on your behalf whether or not anyone told them.

Then there is 47 CFR 64.1200(a)(10), which governs revocation of consent. It says a called party may revoke “by using any reasonable method.” Requests made in any reasonable manner “must be honored within a reasonable time not to exceed ten business days.” And then the sentence that should change how your team is trained: callers “may not designate an exclusive means to request revocation of consent.” Read that one again, because it quietly removes an option most compliance processes assume they have. You do not get to pick the channel.

So the prospect can say stop on the call. Out loud, to a rep, mid sentence. That counts. You do not get to answer that requests have to go to a compliance address. The suppression path begins at the rep’s ear. Which means the rep needs somewhere to put it that reaches everything, during the call rather than at the end of the day.

That is the answer to the question in the title. Repeated prospect calls become a legal problem at a boundary and at an hour rather than at a number, and both of those are things your systems can check on every single dial. The boundary is the stop request. The clock belongs to the person you called.

Your prospect’s cell phone is why this reaches your team

An obvious objection runs through everything above, and it is a fair one. Paragraphs (c) and (d) are written about a residential telephone subscriber, and a B2B rep is calling a business. So why does any of it apply?

Because of 47 CFR 64.1200(e). It states that the rules in paragraphs (c) and (d) “are applicable to any person or entity making telephone solicitations or telemarketing calls or text messages to wireless telephone numbers to the extent described in the Commission’s Report and Order, CG Docket No. 02-278, FCC 03-153.” Wireless numbers. For most outbound teams, that is the entire list.

Now look at what your reps actually dial. Direct mobile numbers, sourced from a data vendor, for people who have not sat at a desk phone in years. Do those ten digits tell you whose line it is? They do not, and the prospect uses that phone for work and for their family with nothing in the record distinguishing the two.

This is where “we are B2B, that does not apply to us” stops being a compliance position and becomes a guess, because it is a claim about the line rather than about your business model and most teams have no evidence for it either way. A team that applies the hour rule and the internal list only to records it has classified as residential is relying on a classification it never made.

The operationally honest move is to stop sorting. Apply the hour window and the internal do-not-call list to the whole outbound motion. What does that cost you? Calls before 8 a.m. and after 9 p.m. in the recipient’s time zone. Those are not your good calls anyway.

Where state law and criminal harassment sit

Everything above is federal, and federal is the floor. States regulate telemarketing on their own terms, with their own registries, their own hours, and their own definitions, and several are stricter than the federal baseline. If you call into a state, you inherit that state’s rules, which is a separate exercise from this one and is covered in the overview of telemarketing laws by state.

Criminal harassment statutes are a different body of law again. They turn on conduct and intent toward a person rather than on a commercial calling pattern, and they are not scaled-up versions of a telemarketing rule. A rep who threatens a prospect has left the subject of this article entirely. Stop the contact, preserve the records, and route it through whatever your organization uses for incidents, because that is a conduct problem and coaching is not the response to it.

Here is what is worth saying plainly to a sales floor. None of these regimes line up with each other. Your team cannot hold all three in their heads during a call block, and expecting them to is the mistake. That is an argument for building the constraints into the system, not for a longer training deck.

Build a prospect call cadence that cannot drift into harassment

The useful design goal is not a compliant cadence. It is a cadence where the non-compliant action is unavailable. There is a difference, and it is the whole difference.

• Put the time zone on the record and let the dialer refuse. Derive it from the number and the account, populate it on import, and block the dial outside 8 a.m. to 9 p.m. at the recipient’s location. A warning banner is not a block.
• Give the rep a one-click stop that fires during the call. If logging an opt-out takes four fields and a dropdown, it will happen after the block, or not at all.
• Make suppression propagate, then prove it. List every system that can start a call: CRM, dialer, sequencer, imported lists, marketing automation, partners and agencies. Suppress in one, then check the others.
• Test it with a live record. Pick a number, run the opt-out, and try to call it from each system. Revenue operations should own this and run it quarterly. A suppression record nobody has tested is a belief.
• Prevent duplicate enrollment and shared ownership. Two sequences and two reps on one prospect produce a contact pattern nobody designed and nobody can defend.
• Identify the caller properly on every call. Individual name, entity name, and a working callback number that is not premium rate. This is 64.1200(d)(4), and it is also just how a real company behaves.
• Retain the record for five years. That outlasts your current stack, so retention cannot live only inside a tool you might replace.
• Give each follow-up a reason that is new. Repeating the same pitch with a different voicemail is the pattern that reads as pressure, and it does not work either.

Notice how little of that is about restraint and how much of it is plumbing. Asking reps to be judicious is the control that fails first, because it fails exactly when the quarter is tight. A documented TCPA compliance workflow is worth more than a stricter cadence policy. And what should you judge a sales engagement platform on here? Not line count. Whether it can enforce a time window and propagate a suppression, which is the bar Kixie and everything else in business calling and texting should be held to.

Repeated prospect calls FAQ

Is calling a prospect every day harassment?

Not by count. No federal rule sets a daily limit on calls to a business prospect, and for B2B calls the pattern-of-calls provision at 310.4(b)(1)(i) is exempt under 310.6(b)(7). Daily calling can still break the hour window. It still has to stop on request. And it is still usually bad prospecting. Frequency is a strategy question here, not a legal threshold.

Can a salesperson call after a prospect says no?

Separate the two things being said. “No, we are not buying” declines an offer. “Do not call me again” is a request to stop contact, and under 64.1200(d)(3) that one is recorded at the time it is made and honored within no more than ten business days. Cannot tell which you heard? Treat it as the second one. The downside of suppressing a prospect who was only declining this quarter is one lost record.

Does blocking a number count as an opt-out?

Blocking is not a notice to you, because you never receive it and you just stop connecting. But 64.1200(a)(10) says revocation can be made by any reasonable method and that you may not designate an exclusive means, so the absence of a formal request does not mean no request was made. And dialing from a different number to get around a block? That is indefensible regardless of what the rule technically requires.

Are B2B calls covered by do-not-call rules?

Partly, and the split is the thing to understand. The FTC’s Telemarketing Sales Rule exempts B2B calls under 310.6(b)(7) except for the two misrepresentation provisions, while the FCC’s rules at 64.1200(c) and (d) are written about residential subscribers but extended to wireless numbers by 64.1200(e). Which set reaches your list? Both, in practice, because B2B prospecting runs on mobile numbers. Treating B2B as a blanket exemption is the specific mistake.

Do automated or prerecorded calls change the answer?

Yes, and they raise the stakes considerably. Prerecorded and artificial voice calls carry their own consent requirements under 64.1200(a), and 64.1200(d) reaches artificial and prerecorded-voice calls made under the exemptions at (a)(3)(ii) through (v) as well as telemarketing calls. Automated calling is a different risk profile from a rep dialing a list, and the current consent and opt-out rules should be reviewed before deployment rather than after.

How long do we have to honor a stop request?

Ten business days is the outer limit under both 64.1200(d)(3) and 64.1200(a)(10), and both phrase it as a reasonable time not to exceed that. Build for same day anyway. Why? Because the gap between ten days and same day is exactly where a sequencer gets one more attempt out the door, and that attempt is the one that generates the complaint.

What to inspect this week

Three checks, and none of them needs a lawyer to start.

First, open your dialer and try to call an East Coast record at 6:15 p.m. Pacific. Does anything stop you? Second, take a number that was opted out last month and try to reach it from every system that can originate contact, including any agency calling on your behalf. How many of them still let the call through? Third, ask whoever owns compliance to produce the written do-not-call policy on the spot, because that is the standard 64.1200(d)(1) sets.

If all three pass, your exposure on repeated prospect calls is a cadence design question, and you can go argue about attempt counts with a clear conscience. If any of them fails, you found something a call limit would never have caught. Teams that also scrub against the National Do Not Call Registry on a schedule should fold that check into the same review.

The question “how many calls can we make” has no answer worth having. Ask a different one. “Can this call still happen, to this person, on this line, at this hour, after what they last told us?” That has an answer every time. Your systems can hold it so your reps do not have to.

Sources

How this article was built: every legal statement below is taken from current primary regulatory text read directly on the review date and linked, and the quoted language is quoted rather than paraphrased so the scope travels with it. No statistic about call volumes, complaint rates, or harassment findings is cited, because no published figure would transfer to your markets, your call types, or your lists, and a borrowed one would read as precision that is not there. The cadence controls and the three inspections proposed above are operating recommendations from this article, not regulatory requirements, and they are deliberately stricter than the rules in places. The Telemarketing Sales Rule governs telemarketing as that rule defines it and its business-to-business exemption carries only the carve-outs quoted above; the FCC rules at 47 CFR 64.1200 apply as written to the subscribers and numbers those paragraphs describe. State telemarketing statutes, state registries, and criminal harassment law are separate bodies of law that are not analyzed here. Scope depends on your markets, call types, and corporate structure, and nothing here is legal advice. Kixie publishes this article and sells sales engagement software for business calling and texting.

• 16 CFR 310.4, Abusive telemarketing acts or practices, Federal Trade Commission, primary regulatory text via the Electronic Code of Federal Regulations, for the prohibition at paragraph (b)(1)(i) on causing any telephone to ring, or engaging any person in telephone conversation, repeatedly or continuously with intent to annoy, abuse, or harass any person at the called number, for the prohibition at (b)(1)(iii)(A) on calling a person who has previously stated that they do not wish to receive calls from or on behalf of that seller, and for the calling time restriction at paragraph (c) limiting outbound telephone calls to a person’s residence to the hours between 8:00 a.m. and 9:00 p.m. local time at the called person’s location.
• 16 CFR 310.6, Exemptions, Federal Trade Commission, primary regulatory text via the Electronic Code of Federal Regulations, for the exemption at paragraph (b)(7) covering telephone calls between a telemarketer and any business to induce the purchase of goods or services or a charitable contribution by the business, and for the two carve-outs to that exemption, namely the requirements of 310.3(a)(2) and (4) and calls to induce the retail sale of nondurable office or cleaning supplies.
• 16 CFR 310.3, Deceptive telemarketing acts or practices, Federal Trade Commission, primary regulatory text via the Electronic Code of Federal Regulations, for the two provisions that survive the business-to-business exemption, namely paragraph (a)(2) prohibiting misrepresenting, directly or by implication, material information in the sale of goods or services including total cost and any material restriction, limitation, or condition, and paragraph (a)(4) prohibiting making a false or misleading statement to induce any person to pay for goods or services or to induce a charitable contribution.
• 47 CFR 64.1200, Delivery restrictions, Federal Communications Commission, primary regulatory text via the Electronic Code of Federal Regulations, for the revocation provision at paragraph (a)(10) permitting revocation by any reasonable method, requiring that requests be honored within a reasonable time not to exceed ten business days from receipt, and barring callers from designating an exclusive means to request revocation; for the time-of-day restriction at paragraph (c)(1) prohibiting telephone solicitation to a residential telephone subscriber before 8 a.m. or after 9 p.m. local time at the called party’s location; for the internal do-not-call list standards at paragraph (d), including the written policy available upon demand at (d)(1), training of personnel at (d)(2), recording the request at the time it is made and honoring it within a period that may not exceed ten business days at (d)(3), identification of the individual caller, the entity, and a contact telephone number that may not be a 900 number at (d)(4), and maintenance of the request for five years at (d)(6); and for paragraph (e) making the rules in paragraphs (c) and (d) applicable to telephone solicitations and telemarketing calls or text messages to wireless telephone numbers to the extent described in the Commission’s Report and Order, CG Docket No. 02-278, FCC 03-153.

Sources verified and content reviewed by the Kixie Research Team on October 2, 2026. All source links checked on October 2, 2026.