Ring group strategies — sequential, simultaneous, hybrid, and the patterns that actually scale

A ring group is a list of extensions that ring together when one of several inbound destinations is hit. FreePBX® and FusionPBX® both expose ring groups with multiple "ringing strategies"; picking the right one shapes how callers experience reaching your team. This article covers the strategies and when each works.

The strategies

Ringall vs queue — which one to use

Ring group and queue are conceptually similar (both ring multiple extensions). Real differences:

• Ring group: caller hears ringing; if no one picks up, fall through to destination (voicemail, IVR, another ring group).
• Queue: caller hears music + position announcements; agents log in/out, calls distributed per queue strategy; statistics reporting; callbacks possible.

Rule of thumb:

• Up to ~5 extensions, no concept of "logged in vs not" — ring group.
• 5+ agents with shift schedules, login/logout, reporting needs — queue.

FreePBX ring group config

Applications → Ring Groups → Add.

• Ring-Group Number: the extension callers dial (e.g., 600 for "Sales").
• Group Description: "Sales" or "Front Desk" — what shows up in CDR.
• Ring Strategy: from the list above.
• Ring Time: seconds before falling through. Default 20s; for ringall, 15-20s is reasonable.
• Extension List: the actual extensions, one per line. Append # to a number for external (e.g. 2125551234# to dial out to a cell).
• Destination if no answer: where the call goes if nobody picks up. Voicemail box, IVR, another ring group, hangup.

External numbers in the ring group

The #-suffix pattern is genuinely useful — ring the front-desk extension AND the manager's cell simultaneously. Caveats:

• External calls consume a SIP trunk port. If your trunk is sized at 4 channels and you ringall to a group with 3 cell numbers, that's 3 channels used. Plan trunk capacity.
• If the cell number's voicemail picks up, it counts as "answered" — the call gets connected to the cell voicemail instead of your PBX's voicemail. Use "confirm calls" / "remote secure" to require a DTMF press before the call is considered answered.
• Outbound caller ID — make sure your outbound caller ID is the actual business number, not a random trunk number. Caller answers a call from "+1 (xxx) xxx-xxxx unknown" much less reliably than from "Your Business Name."

Voicemail interaction

When ring group hits Ring Time without answer, the No Answer Destination fires. Common patterns:

• "Voicemail: Sales VM" — sends to a shared inbox.
• "Voicemail: 101 unavailable" — sends to a specific person's voicemail.
• "IVR: After-hours menu" — offers callback, voicemail, or repeat.
• "Ring Group: Tier 2" — fallback to a senior team.

The fall-through chain can go deep. Don't go deeper than 3 levels; caller patience runs out.

Time conditions

Routing to different ring groups by time of day is standard:

• Business hours: ringall(Sales)
• After hours: voicemail(Main)
• Lunch: IVR("press 1 for emergency support, 2 to leave voicemail")

FreePBX → Applications → Time Conditions or Time Groups. Wire the inbound route's destination through a time condition that picks among ring groups based on current time.

Anti-patterns

• 10-extension ringall. Everyone's phone rings, almost certainly multiple people pick up at once, one wins the race and the others see "call disconnected before you answered." Confusing. Use a queue.
• Hunt with no fallback. Last person's voicemail is the de-facto fallback. Make it intentional — set the no-answer destination explicitly.
• Ring time of 60+ seconds. Callers expect to be picked up within 30 seconds or sent to voicemail. Extended ringing is annoying, not helpful.