Simultaneous vs. sequential ringing: choose a ring group for your team

Start with who should get the first chance to answer

Choose simultaneous ringing when several people can handle the same call and should get the chance together. Choose sequential ringing when one person owns the first response and others are backups. In either case, decide where the caller goes if nobody answers.

A ring group sends a call to several people or phones.[1] Rinzo supports simultaneous ringing and an ordered hunt, called single in its technical settings.[2] The choice is about your team's work: who can answer, who should be interrupted, and how long a caller should wait before reaching a useful fallback.

The plans below are hypothetical examples for a small workshop, not configurations already applied or call tests performed. Use them to write your own route before changing the phone system.

Ring together when the team shares the job

Suppose three workshop coordinators can all book a repair. A simultaneous group gives each of them a chance to answer without waiting for another person's turn. In Rinzo, simultaneous members with no delay start together; a user member rings that user's phones at once, subject to the forwarding settings discussed below.[2][3]

This is a useful starting point for a small shared front desk. Everyone needs to know that the call is a shared responsibility. If two people regularly reach for the phone together, decide how they will divide the work rather than adding more ringing time.

Proposed plan: ring the three coordinators together for up to 20 seconds, with an explicit no-answer route to the workshop's business mailbox. That duration is an example, not a recommended universal setting. Check whether staff can actually reach their phones in that window and whether the resulting wait is acceptable from the caller's side.

The trade-off is interruption: each incoming call can alert several people. If only one person is normally expected to answer, a shared group may disturb the others without a useful reason.

Ring in order when there is a clear first responder

For a workshop with a dedicated coordinator and an owner who covers breaks, an ordered hunt can fit better. Put the coordinator first, then the owner, and finish with the business mailbox if neither answers. Rinzo's single strategy attempts members in list order, using each member's timeout; member delays do not apply to that strategy.[2]

The benefit is clear ownership. The backup does not need to be the first person alerted. The cost is waiting: a caller may sit through unanswered attempts before reaching someone available. Review the whole route, including any welcome message or menu before the group, rather than judging each member's ring time separately.

Write down the actual order. A list that happens to put the owner first is not the same as a deliberate reception-first plan. Revisit it when staff roles change, and avoid placing someone who rarely answers at the front merely because they created the account.

An ordered hunt is a fixed sequence, not evidence that calls rotate fairly or that the system selects whoever has been idle longest. Do not describe your setup that way unless you have configured and verified that different behavior.[2]

A delayed backup can join without replacing the first person

You may want reception to ring first, then have a backup join while reception keeps ringing. That is different from a strictly sequential hunt. Rinzo's simultaneous strategy supports a separate delay and ring duration for each member, with the group's overall timeout limiting the attempt.[2]

For example, a proposed 30-second group attempt could use these settings:

• Reception: no delay, with a 30-second member ring duration.
• Backup: a 15-second delay, with a 15-second member ring duration.
• No answer: an explicitly configured route to the business mailbox.

The overlap is intentional. The proposed settings let both people answer during the later part of the attempt. These are illustrative settings, not guarantees of a handset's exact audible ringing or the full time before voicemail. Have the administrator check the overall group limit as well as member delays and durations; a short group limit can cut off a backup before it has a useful chance.

Keep cell forwarding and voicemail in the plan

A person's forwarding settings can change which phone rings when the group reaches them. In Rinzo, user call forwarding also applies to ring-group calls unless it is restricted to direct calls.[3] Check those settings before treating the member list as the complete destination list.

If a backup uses a cell phone, plan for the cell's own voicemail. Rinzo documents a cell-phone group member with press-1 acceptance and a business-voicemail overflow.[3] For user forwarding, check that require_keypress is enabled; the answerer must then press 1 to accept.[2] Test the unanswered case rather than assuming that any mobile destination keeps messages in the business mailbox.

A direct outside-number target is different: Rinzo documents that an unanswered plain external forward ends the call instead of continuing to another fallback. Use the documented group-member path when you need business-voicemail overflow.[3]

Name the person who checks the final mailbox and a backup for absences. The business voicemail guide covers message ownership. Mobile forwarding uses your plan's included minutes, then the per-minute rate; check current pricing [4] before choosing that route.

Write a short ring-group brief

Before configuring anything, fill in these decisions:

• Purpose: which calls should reach this team?
• First chance: everyone together, a fixed order, or reception with a delayed backup?
• Members: which people, and which phones or forwarding destinations will each use?
• Wait: how long should the full ringing attempt last before fallback?
• Unanswered calls: which business mailbox or staffed destination comes next, and who owns it?
• Schedule: should this group receive calls outside business hours?

A concise agent brief might be: 'During opening hours, ring our workshop coordinators together. If nobody answers, take a message in the workshop mailbox. Closed-hours calls should go straight to that mailbox.' Your agent can configure that brief within your existing delegation.

Use the call-routing guide [1] for the Control panel or the agent setup guide to delegate configuration. If your agent creates the main-number menu and hours through the CLI, edit that route in Advanced Callflows rather than recreating it in SmartPBX.[1] The hours-planning guide covers the schedule around the group.

Call from outside the group and check the fallback

Inspect the saved strategy, members, timing, and overflow first. Rinzo's CLI can simulate routing, but simulation is not proof of audible ringing or an answered phone call.[2][3] For the live check, use an outside phone: a call from a group's own member skips that member's phone in Rinzo.[3]

1. Call the real business number during the intended open-hours path. Observe which phones ring first.
2. Let the first responder ignore the call. Check when backups begin and whether the original phone continues, as your plan requires.
3. Answer at each intended position in separate calls. Confirm both sides can hear one another.
4. Let the call go unanswered at every destination, including any forwarded cell. Leave a labeled test message and retrieve it as the mailbox owner.
5. Check the closed-hours path separately so the group does not ring when it should be bypassed.

Keep expected and observed results beside the brief. If the route differs, correct the specific timing, forwarding, or fallback setting and repeat that case. These are proposed acceptance steps, not tests performed by this article. Never use an emergency number for a test. Rinzo does not support 911 or other emergency calling during early access; keep another way to call for help.[9]