How many rings before voicemail — and how to change it

Most US carriers ring an unanswered line for roughly 20 to 25 seconds before handing the call to voicemail. That works out to about four to six rings, depending on where in the ring cycle the call was connected.

Counting rings is a poor way to think about it. The network is running a timer in seconds, not counting rings, and the ring you hear as the caller is generated locally — it isn't synchronised with the ring on the receiving phone. Two people calling the same number can hear a different number of rings before the same voicemail picks up.

So the real question isn't "how many rings" but "how many seconds", and on GSM networks that timer is adjustable.

Ring duration is set by the no-reply conditional forwarding rule — the same **61* family of codes used to route unanswered calls. The syntax is:

**61*<voicemail number>**<seconds>#

Then press call. For example, **61*+18005551234**30# rings for 30 seconds before forwarding.

Two constraints the carriers enforce and no code gets around:

• Seconds must be a multiple of 5 — 5, 10, 15, 20, 25, or 30.
• 30 seconds is the maximum. There is no code, carrier setting, or app that extends it beyond 30. Anything promising 60 seconds is wrong.

To check the current setting rather than change it, dial *#61# — the network replies with the active no-reply rule, including the destination and the timer.

The code needs the number your carrier uses as the voicemail destination, which usually isn't your own number and isn't the same as the number you dial to listen to messages.

The reliable way to find it: dial ***#61#** and read the destination in the response. That's the exact string your network already has on file — copy it, including the leading +1, into your new code.

If *#61# returns nothing useful, dial *#62# (the not-reachable rule) which usually points at the same voicemail platform. Failing both, your carrier's support line can give you the voicemail access number for your account.

Using the wrong destination is the single most common way this goes wrong — you end up forwarding unanswered calls to a dead number, and callers get an error instead of your greeting.

AT&T and T-Mobile (and the MVNOs riding on them — Mint, Cricket, Metro, Google Fi, US Mobile) run GSM-style networks and generally accept the **61* timer. This is the mainstream case.

Verizon is the awkward one. Its network heritage handles conditional forwarding differently, and the **61* timer is commonly rejected or silently ignored. On a Verizon line the ring duration is usually fixed at the network default, and changing it means asking Verizon support directly — there's no self-service code.

UScellular behaviour varies by device and plan; try *#61# first to see whether a no-reply rule exists at all.

If the code returns an error, that's the network refusing, not a typo — no amount of reformatting will make an unsupported carrier accept it.

Thirty seconds sounds generous until you're the one waiting. Most callers give up well before a voicemail greeting starts, and the ones who do reach voicemail frequently hang up without leaving a message — a silent missed call that never appears as anything you can follow up on.

Stretching 20 seconds to 30 buys you ten more seconds to get to the phone. It doesn't change what happens when you can't: the call still ends in a recording, or in nothing at all.

The alternative is to stop treating voicemail as the fallback. Conditional forwarding — the same **61* mechanism, pointed somewhere other than voicemail — hands unanswered calls to a person or an AI that actually picks up. Same code family, meaningfully different outcome.