Ring your whole team at once (Ring Group node)

The Ring Group node rings your team simultaneously through their Dispatch Bros apps — browser, desktop app, and iPhone — and the first person to answer takes the call. By default it rings every online owner, admin, and dispatcher; the settings panel confirms this with "Rings all logged-in owner/admin/dispatcher users". Pick a Call Group instead to ring only a specific subset, like your after-hours crew.

Before you start

• Your team members must be added as owner, admin, or dispatcher — see add a dispatcher or admin.
• Teammates ring only while they're online in Dispatch Bros. Someone who has switched themselves offline, or has no app open anywhere, will not ring.
• To ring a subset, create the group first in Phone System → Team Routing — see answer groups.

Step 1 — Add the Ring Group node

1. Open your flow in Phone System → Call Flows.
2. Drag Ring Group from the Node Palette onto the canvas and click it to open its settings.

Step 2 — Choose who rings

The Call Group dropdown starts on "All team members (default)" — every online owner, admin, and dispatcher rings. To narrow it, pick one of your Call Groups; the panel shows the group name and its member count. A group-scoped ring never pulls in people outside the group.

Step 3 — Set the ring timeout

Ring Timeout (seconds) is how long the team rings before the flow moves on — from 10 to 120 seconds (30 is the default). If more people are eligible than can ring at once, Dispatch Bros rings them in waves within this total budget, so nobody eligible is skipped.

Step 4 — Wire the no-answer path and publish

Drag a line from the bottom of the Ring Group node to the step that should catch unanswered calls — almost always a Voicemail node. A Ring Group is allowed to be the last step, but then an unanswered call simply ends. Press Publish when the preflight reads "All checks passed — safe to publish."

How answering works

• Everyone eligible rings at the same time, on every device where they're live — with one refinement: a teammate running the desktop app rings there rather than in their browser tabs.
• The first person to answer gets the caller; every other ring stops immediately and those teammates see the call was answered elsewhere.
• You can watch this live on the Live HUD — who's ringing, who answered, and how long they've been on the call.

Troubleshooting

• Nobody rings — check that at least one owner/admin/dispatcher is online. The Team Routing tab's group expander and the Live HUD both show live presence per person ("Available", "Ringing", "On call", "Offline"). If everyone shows "Offline", the call goes straight past the ring to your no-answer path.
• Only some people ring — the node is scoped to a Call Group; check its membership in Phone System → Team Routing. Offline members of the group don't ring either.
• Calls end instead of reaching voicemail — nothing is wired after the Ring Group node. Connect its bottom dot to a Voicemail node.
• An older flow shows a "Ring Group (Legacy)" node — that legacy node dials outside phone numbers directly (it has a Numbers list and a Strategy of Simultaneous or Sequential) rather than ringing the team's apps. New flows should use the current Ring Group node.