Outbound Call Connection Delay and the Two Second Rule

TL;DR: Outbound call connection delay is two different problems wearing one name, and the split happens the moment the buyer says hello. Before the answer, the delay is a network number and the published targets are generous. The ITU-T grade of service recommendation for circuit-switched services sets mean post-selection delay targets of 3 seconds on a local connection, 5 seconds on a toll connection and 8 seconds on an international one, with 95th percentile targets of 6, 8 and 11 seconds under normal load. Nobody is listening during that stretch, so it costs you patience and nothing else. After the answer, the budget collapses to two seconds. Both regulators define it the same way. Under 47 CFR 64.1200(a)(7) and 16 CFR Part 310, a call is abandoned if it is not connected to a live sales representative within two seconds of the called person’s completed greeting. The clock starts at the end of their greeting, not at answer, which is the same window your answering machine detection wants in order to classify that greeting. If no rep is there at second two, the FCC asks more of you than the FTC does. The FCC rule requires an identification and opt-out message plus an automated keypress opt-out that records the number to your do-not-call list and immediately ends the call, while the FTC safe harbor asks only for the seller’s name and telephone number. You also cannot buy time by hanging up sooner, because both rules require at least 15 seconds or four rings before you disconnect an unanswered call. Measure five checkpoints on every test call, starting with dial to first provisional response, first response to alerting, alerting to answer, answer to two-way audio, and answer to rep. And stop treating ringback as evidence, because 47 CFR 64.2201 forbids a long distance provider from conveying a ringing indication before the terminating provider signals that the called party is being alerted, and forbids intermediate providers from generating that signal at all.

Your reps are not filing tickets about milliseconds. They are telling you that they click a name, sit through a long nothing, and then hear a buyer say hello twice before anyone is there to answer back. Those are two separate failures. Which one are they describing? Most of the time the rep cannot say, because nothing in the workflow records the difference, so the two arrive as one complaint, get escalated as one ticket, and land on a team that cannot fix either of them.

Outbound call connection delay is the umbrella term for both. Why bother splitting it? Because the two halves have different owners, different measurements, and tolerances that are not even the same order of magnitude. One of them has a published network target measured in whole seconds. The other has a legal ceiling of two.

So before you open a carrier ticket, ask one question. Which half are you in?

What Outbound Call Connection Delay Actually Measures

Outbound call connection delay is the elapsed time between one call event and the next. Between which events? That depends on your workflow, and nobody says which one they mean. It could be the gap from clicking the call button to hearing ringback, the gap from the buyer answering to two-way audio, or the gap from an answered call to a rep actually being on it.

Four labels get used interchangeably, and they are not the same thing:

• Post-dial delay. The interval between sending the call and getting a meaningful response back from the network, such as alerting, busy, or an error. This is the pre-answer half.
• Dialer latency. A loose catch-all for delay introduced anywhere in a dialer’s initiation, routing, connection, or agent-assignment path. Useful in conversation, useless in a ticket, because it names no interval anyone can go and measure.
• Post-answer dead air. Silence after the buyer has answered but before audio or a rep arrives. This is the half with the legal ceiling.
• Delayed connect. A contact center term for the gap between the buyer answering and reaching an available rep. Same half as dead air, different vantage point.

So which one is your team actually arguing about? Precision here is not pedantry, because a carrier routing problem and a missing media path produce the identical rep complaint, sit on opposite sides of the answer event, and share no fix at all. Name the interval or you will spend a week on the wrong leg.

Outbound Call Connection Delay Splits at the Answer

Draw one line through the call at the moment the buyer picks up, and the confusion resolves itself. Everything to the left of that line is a network and routing question. Everything to the right is a workflow and compliance question. The budgets on either side of the line are not remotely the same size, and that asymmetry is the whole reason teams misdiagnose this.

Left of the line, the only cost is your rep’s attention. The buyer does not know the call exists yet. Seconds spent here are seconds spent waiting, which is irritating and expensive at volume but harms nothing in the conversation itself, because there is no conversation yet to harm.

Right of the line, everything changes. The buyer is holding a phone to their head, saying hello into silence, and deciding in real time whether this is a robocall. Every tenth of a second is a conversation you are losing. Past two seconds, you are not just losing the conversation. You have created an abandoned call under federal rules.

So which half are your complaints coming from? If reps say the call takes forever to ring, that is the left. If buyers answer and nobody is there, that is the right. If reps cannot tell you which, that is your first finding, and the fix is instrumentation rather than a carrier ticket.

Before the Answer, the Delay Budget Is Measured in Seconds

Here is the part most teams get wrong. The pre-answer leg is allowed to be slow, and the published targets are far more generous than the escalation emails assume. So how slow is too slow?

The ITU-T recommendation on network grade of service parameters defines post-selection delay as the interval from the calling terminal passing the last selection digit until the first message indicating call disposition comes back, which on a successful call is the alerting message, and it then publishes target values for that interval by connection type and network load. Its target values under normal load are a mean of 3 seconds for a local connection, 5 seconds for a toll connection and 8 seconds for an international one. At the 95th percentile those targets run 6, 8 and 11 seconds. Under high load those means stretch to four and a half, seven and a half, and twelve seconds.

Read that again with your last escalation in mind. A rep who waits five seconds for an international call to ring is sitting inside a published target rather than inside an incident, and the ticket you opened on their behalf described normal network behavior as a fault.

Does that make the pre-answer leg unaccountable? No, and two caveats keep this honest. It is a 1999 recommendation written for the evolving ISDN in Q-series and Signalling System No. 7 terms, so it is a reference point for the network leg rather than a service level you can hold a modern SIP provider to. It also states explicitly that delays inside customer premises equipment and the subscriber terminal are not part of these definitions. Your browser, your headset and your laptop are your problem, not the network’s, which is a useful boundary when a provider and an internal team are each certain the other one owns the delay.

What the pre-answer leg does give you is a rule you can actually enforce. Under 47 CFR 64.2201, a long distance voice service provider may not convey a ringing indication to the calling party until the terminating provider has signaled that the called party is being alerted. If the terminating provider supplies its own tone or announcement, the originating provider must stop any locally generated tone and pass the real one through. Intermediate providers get a harder version: they may not generate alerting signaling at all, and must return it unaltered.

Why does that matter operationally? Because it converts a vague complaint into a provable one. If your rep hears ringback at one second and the buyer’s phone starts ringing at four, the ringback was manufactured somewhere in the path, and a rule says it should not have been. Your logs, not your rep’s ears, are the record. That is a carrier conversation with a rule attached, which is a very different email from asking a vendor why calls feel slow.

After the Answer, the Delay Budget Is Two Seconds

Now the right side of the line, where the number is small and written down. How small? Two seconds, and both regulators say so in almost the same words.

47 CFR 64.1200(a)(7) says a call is abandoned if it is not connected to a live sales representative within two seconds of the called person’s completed greeting. The FTC says the same thing in 16 CFR Part 310: an outbound telephone call is abandoned if a person answers it and the telemarketer does not connect the call to a sales representative within two seconds of that person’s completed greeting.

Two details in that sentence do the work. Why does the exact wording matter so much? Because both of them hand you something your dialer configuration almost certainly ignores.

First, the clock starts at the completed greeting, not at answer. The buyer’s “Hello, this is Dana speaking” belongs to them. You are allowed to wait through it. That is a real allowance, it is written into the definition rather than inferred from it, and most dialer configurations never account for it because they start counting the moment the carrier reports an answer.

Second, the requirement is a live sales representative. Media being up is not the same as a human being there. What does your dashboard say about that? Almost certainly nothing, because a call where audio connects instantly and a rep arrives at second four is still an abandoned call while every media quality metric on it reads as perfectly healthy.

You also cannot recover time by cutting the front of the call short. Both rules set a floor on ringing: 47 CFR 64.1200(a)(6) prohibits disconnecting an unanswered telemarketing call before at least 15 seconds or four rings, and the FTC safe harbor carries the same 15 second or four ring condition. The pre-answer leg is not a place to make up budget.

If you want the arithmetic of how abandoned calls are counted and capped across a campaign, that belongs in the question of whether parallel dialers affect answer rates. This article is about where the two seconds go.

What Eats the Two Seconds and How to Get Them Back

So where do the two seconds actually go? Three things consume them, and the uncomfortable part is that the three compete with each other rather than adding up neatly.

Answer detection. Answering machine detection has to hear the greeting to classify it. A human “hello” and a voicemail greeting both start with speech, and the cheapest signal separating them is how long the speech runs before it stops. So the classifier wants more greeting, and the rule gives you two seconds after the greeting ends. Tune detection toward confidence and you spend the budget. Tune it toward speed and you hand more machines to live reps. There is no setting where both are free, which is why answer detection is a trade you make deliberately rather than a feature you switch on and stop thinking about.

Rep assignment. In any workflow that dials ahead of its reps, somebody has to be available at the exact instant a buyer answers, and availability is a state your system either records or guesses at. When the pacing logic is calling more numbers than there are reps in the right state, the gap is not technical. It is a staffing and pacing arithmetic problem wearing a technical costume, and it will keep producing dead air no matter how clean the network looks. Check rep state transitions against answer timestamps before you check anything else.

Media setup. Signaling can complete long before audio finishes negotiating, and the two are not reported together on most platforms. NAT traversal, firewall rules, codec negotiation, browser microphone permission and a headset waking up all land here. This is the one that produces one-way audio, and one-way audio should be logged separately from two-way silence because they point in different directions.

So what actually removes the problem rather than tuning around it? The structural fix is the unglamorous one. A single-line dial where the rep is already on the call has no post-answer handoff, because there is nothing to hand off. The two second problem is created by dialing ahead of your people. That does not make multi-line dialing wrong, and the reasons power dialers can reduce connect rates are worth reading before you change modes. It does mean the compliance exposure and the dead air both belong to the decision to dial ahead, not to the carrier.

Kixie’s PowerDialer runs in single-line or multi-line mode, and AI Human Voice Detection identifies when a live person answers so reps skip machines and dead air. Pick the mode deliberately, with the two second rule in front of you, rather than defaulting to whichever one produces the bigger dial count.

What You Owe the Buyer When No Rep Is Available

Sometimes nobody is there at second two. What are you supposed to do then? The rules do not let you sit in silence, and the two regulators do not agree on what you owe instead.

Under 47 CFR 64.1200(a)(7)(i), whenever a live sales representative is not available within two seconds of the completed greeting, you must provide two things. One is a prerecorded identification and opt-out message. It is limited to disclosing that the call was for telemarketing purposes, naming the business on whose behalf the call was placed, and giving a telephone number that lets the person make a do-not-call request during business hours for the duration of the campaign. That number cannot be a 900 number or any other line charging more than normal transmission charges. The other is an automated interactive voice or keypress opt-out mechanism with brief instructions, which must automatically record the number to the seller’s do-not-call list and immediately terminate the call.

The FTC safe harbor rule is lighter. Under 16 CFR Part 310, whenever a sales representative is not available within two seconds of the completed greeting, the seller or telemarketer promptly plays a recorded message stating the name and telephone number of the seller on whose behalf the call was placed.

Notice the gap. One regulator wants a working keypress that writes to your suppression list and hangs up, and the other wants a name and a number read aloud. Build to the lighter one and you are short. A footnote in the FTC rule says as much, noting that its safe harbor does not affect your obligation to comply with the TCPA and 47 CFR Part 64.1200.

The FCC rule also requires that the seller or telemarketer maintain records establishing compliance. Can your dialer produce, per call, the answer timestamp, the greeting end, the rep join, and whether the opt-out message played? If not, you do not have those records, and the time to find that out is before somebody asks you for them.

How to Measure Outbound Call Connection Delay on Real Calls

Stop asking reps whether calls feel slow. Feel is not a measurement and it cannot be escalated. Place controlled test calls instead and write down five intervals.

• Dial to first provisional response. A long gap here points at local processing, name resolution, trunk selection, or an upstream provider that is slow to answer your request.
• First response to alerting. Dial plan decisions, route attempts and fallback behavior live here. A route that is tried, fails and is retried shows up as a clean step in this interval.
• Alerting to answer. This is the buyer deciding to pick up, plus any forwarding, screening or sequential ringing on their side. It is almost never your dialer, and a long interval here is a list quality signal rather than a technical one.
• Answer to two-way audio. Media negotiation, NAT, firewall, browser permission and endpoint readiness.
• Answer to rep join. Pacing, rep state, bridge creation. This is the interval the two second rule is written about, and it is the one most teams never record.

For each test call, capture the time with its time zone, the originating and destination numbers, the user, the device, the network, the dialing mode and the call identifier. Then compare an affected call against a clean one placed the same minute. What does a useful comparison look like? One bad call tells you nothing. A pair placed back to back, one slow and one clean, tells you exactly which of the five intervals moved and by how much, which is the only sentence a carrier or a vendor can act on.

Change one variable at a time. Why is that worth the extra round of testing? Because a test that swaps the browser, the headset, the network and the dialing mode at once produces a result you cannot attribute to any of them, which means you ran four tests and learned nothing. And restrict access to signaling and media records, because they carry phone numbers and other business information you did not intend to circulate.

Also pull packet loss, jitter and round-trip latency if your platform exposes them. They explain audio quality well. They do not by themselves explain call setup delay, and treating a single jitter reading as the cause is how teams end up paying to replace a network that was never the problem while the pacing configuration that actually caused the dead air goes untouched.

Match the Call Delay Symptom to the Team That Owns It

• Long pause before any response at all. Check reachability, name resolution, PBX processing, trunk selection and provider response timing. Owners: your voice or network team and the calling provider.
• Only certain destinations are slow. Compare number formats, routes, destination carriers, regions and time of day. Owner: the carrier, and they will want representative call identifiers.
• Ringback starts well before the buyer’s phone rings. That is the ring signaling integrity rule. Owner: the long distance or intermediate provider in the path.
• Buyer answers and hears silence. Compare answer, media and rep-join timestamps. Owners: your dialer configuration and your pacing, not the carrier.
• One rep affected, everyone else fine. Test that rep’s browser, endpoint, headset, permissions and local network. Owner: the rep’s setup.
• Delay only on bridged or forwarded calls. Compare a direct test against a bridged one, then inspect forwarding, screening and the intermediate phone provider. Owner: whoever configured the bridge.
• Intermittent across many users. Correlate by route, provider, destination and release or configuration change. Owner: whoever shipped the change.

One symptom does not belong in this table at all. Caller ID reputation sits in a different column. If your numbers are being flagged, buyers decline rather than wait, which reads as a connect rate problem rather than a delay problem. That is the subject of local presence and scam likely labels, and it is worth ruling out before you chase milliseconds.

When to Escalate Outbound Call Connection Delay

When is it actually worth escalating? Escalate when the delay reproduces on demand, affects more than one rep or destination, follows a route pattern, or survives your own endpoint and network tests. Anything short of that is still yours. Send an evidence package, not a complaint:

• Call identifiers and exact timestamps with time zones
• Originating and destination numbers in the format the provider asks for
• Which of the five intervals moved, stated plainly
• A matched pair of calls, one affected and one clean
• Signaling logs, media statistics or recordings, shared securely
• Device, browser, network, dialing mode and bridge details
• Any configuration, carrier, workflow or software change in the window

Do not disable recording, disclosure or compliance controls to make a call faster, and get internal approval before changing production configuration. Teams on Kixie should check current Kixie support documentation for product-specific log collection, since the available diagnostics change over time and current product documentation beats any generic guidance, including this article.

Nothing here is legal advice. State rules add requirements on top of the federal ones, and everything quoted here is the federal baseline rather than the complete set of rules you operate under. Confirm your calling motion with counsel before you build to it.

Outbound Call Connection Delay FAQs

Why does an outbound call take several seconds to ring?

Usually because the pre-answer leg is genuinely allowed to take that long. The ITU-T grade of service recommendation targets a mean post-selection delay of 3 seconds locally, 5 on a toll connection and 8 internationally under normal load. Compare your dial, first-response and alerting timestamps before you escalate anything.

What is the two second rule for outbound calls?

A call is abandoned if it is not connected to a live sales representative within two seconds of the called person’s completed greeting. That definition appears in 47 CFR 64.1200(a)(7) and in the FTC’s Telemarketing Sales Rule at 16 CFR Part 310. The clock starts when the greeting ends, not when the buyer picks up.

Why is there silence after the customer answers?

Either the media path is not ready or no rep is. Those are different fixes, so compare answer to two-way audio against answer to rep join. If the rep interval is the long one, the problem is pacing and staffing rather than the network.

Does ringback mean the buyer’s phone is ringing?

Not necessarily, and there is a rule about it. Under 47 CFR 64.2201 a long distance provider may not convey a ringing indication before the terminating provider signals that the called party is being alerted, and intermediate providers may not generate that signal at all. Trust the signaling record over the tone.

Can we hang up faster on calls that are slow to connect?

No. 47 CFR 64.1200(a)(6) prohibits disconnecting an unanswered telemarketing call before at least 15 seconds or four rings, and the FTC safe harbor rule sets the same floor. You cannot buy post-answer budget on the pre-answer leg.

What should we collect before escalating a connection delay?

Call identifiers, timestamps with time zones, numbers, user, device, network, dialing mode, which of the five intervals moved, and a matched pair of affected and clean calls. Evidence lets the responsible team find the delay instead of guessing at it.

Sources reviewed October 13, 2026.

Sources

• 47 CFR 64.1200, Delivery restrictions, U.S. Government Publishing Office, 2025 edition revised as of October 1, 2025. Paragraphs (a)(6), (a)(7), (a)(7)(i) and (a)(7)(iii).
• 16 CFR 310.4, Abusive telemarketing acts or practices, U.S. Government Publishing Office, 2025 edition. Paragraphs (b)(1)(iv) and (b)(4).
• 47 CFR 64.2201, Ringing indication requirements, U.S. Government Publishing Office, 2025 edition revised as of October 1, 2025.
• ITU-T Recommendation E.721, Network grade of service parameters and target values for circuit-switched services in the evolving ISDN, International Telecommunication Union, revised May 1999. Clauses 2.2 and 3, Table 2.

Sources verified by the Kixie Research Team on October 13, 2026.