Call Routing for Small Business | Ring & Hunt Groups

Call Routing for Small Business: Ring & Hunt Groups

Call routing for a small business is how inbound calls to your main number (and other DIDs) are sent to the right people — usually via ring groups or hunt groups on a hosted PBX — instead of one receptionist phone or a chaotic “everyone answers everything” free-for-all. For roughly 20–100 person companies, good call routing means mapping who should ring first, whether phones ring together or in order, what happens if nobody answers, and how softphones and desk phones stay in the same rules. This playbook is a practical call-routing checklist for IT managers: ring groups vs hunt groups, simultaneous vs sequential ring, how SessionPBX-style hosted PBX routing fits with auto attendants and queues, and what to test before cutover — without inventing answer-rate statistics or rewriting IVR/contact-centre guides.

What is call routing (and how is it different from an auto attendant or a call queue)?

Call routing is the set of rules that decide which phones or softphones ring when someone dials your main number or another inbound DID. On a hosted PBX such as SessionPBX, that usually means ring groups, hunt groups, and no-answer paths — not one reception handset and not “ring every extension.”

It is not an auto attendant: menus ask the caller to choose (press 1 for sales) before a human rings. Call routing is what happens when the call should ring people, with or without a menu first.

It is not a call queue either. Queues hold callers while agents log in and out; a ring or hunt group simply rings a small team until someone answers or the call overflows.

Call forwarding sends a call to one destination. Routing decides which set of endpoints should try first.

Call routing vs related phone features

When should a 20–100 person company use a ring group vs a hunt group?

Vendor UIs label these differently, so document the behaviour you want rather than arguing about the acronym.

Use a ring group when a small team shares a DID and any member can answer — main reception, sales overflow, or a three-to-six person service desk. Members ring by rule, often all at once.

Use a hunt group when order matters: try reception first, then the office manager, then a named backup. Hunt walks members until someone answers; it suits VIP lines where the first-try person is intentional.

Practical rules of thumb for 20–100 people:

• Main published number → ring group of reception + one or two trained backups (simultaneous or short sequential).
• Department DIDs (sales, accounts) → ring group of that team only — do not dump them into the all-hands main line.
• Executive / VIP DIDs → hunt or tight sequential list; keep executives out of the noisy main ring.
• If callers need to wait in line with hold treatment → evaluate a queue instead (queues/IVR buyer guide); do not stretch a ring group into a fake contact centre.

If you are migrating routing patterns from another PBX, copy the *outcomes* (who rings, for how long, where unanswered calls go) into SessionPBX rather than cloning every legacy label.

What is simultaneous ring vs sequential ring (and when is find-me/follow-me useful)?

Simultaneous ring rings every member at once — first to pick up wins. Fast for small reception or sales teams; every phone buzzes on every call.

Sequential ring (linear hunt) tries member A for N seconds, then B, then C. It preserves a preferred answerer and is quieter for people later in the list; keep per-step times and the member list short so callers are not waiting forever.

Find-me / follow-me is an optional layer that tries a person's desk phone, then softphone, then a mobile number. Useful for named executives or on-call roles — not a substitute for a clean main-line ring group. Treat personal-mobile hops as an explicit policy choice, and pair overnight paths with out-of-hours call handling rather than redesigning after-hours here.

Pick mode per DID: simultaneous for small shared teams that need a fast pickup; sequential (short per-step ring times) when a preferred answerer matters; find-me on a named extension when coverage must hop devices — still behind a group or attendant for the public main line.

How do you design inbound call routing for main line, departments, and VIP DIDs?

Design by number purpose, not by whoever shouted loudest in the kick-off meeting.

1. Main line — public website/stationery number. Ring group of reception-capable people; optional short auto attendant *before* the ring if you need press-1/press-2 (auto attendant). Define no-answer: voicemail, overflow group, or queue.
2. Department DIDs — sales, service, accounts. Separate ring groups so a service spike does not steal every sales headset.
3. Direct / personal DIDs — individual extensions with optional find-me. Do not auto-add every direct into the main ring.
4. VIP / executive DIDs — tight hunt or sequential list; assistants first if that is the culture. Keep executives out of the all-hands simultaneous ring.
5. Fax / legacy / unused numbers — inventory them; park, cancel, or dead-end voicemail so they do not surprise-ring a desk after cutover. If numbers are moving, finish the porting checklist before inventing routing for DIDs you do not yet control.
6. Multi-site — when you add branches, use the multi-location call routing playbook; this post stays on single-site business-hours ring/hunt design.

Ring group design worksheet

1. DID / number label
2. Purpose (main / sales / service / VIP)
3. Members (name + desk/softphone)
4. Ring mode (simultaneous / sequential)
5. Ring time per step (seconds)
6. No-answer destination
7. Business hours schedule
8. Owner + last reviewed date

Fill one row per DID before you save in SessionPBX — source of truth for testing and monthly headcount reviews.

What does a practical call routing checklist look like before go-live?

Week 1 — Map numbers & owners

1. List every inbound DID: main line, department lines, directs, fax/legacy — link the porting checklist if numbers are moving.
2. For each DID, write the business outcome in plain language (e.g. “main number: sales + reception first; overflow to service”).
3. Name owners: who edits routing rules, who approves changes, who gets the “nobody answered” ticket.
4. Decide business hours vs out-of-hours handoff — use the live out-of-hours post; do not rewrite that playbook here.

Week 2 — Choose ring / hunt patterns

1. Pick ring group (members ring per rule; common SMB default) vs hunt group (ordered hunt through members) per DID — vendor labels vary; document the behaviour you want, not the acronym.
2. Choose simultaneous (all ring together) vs sequential (one after another) and max ring time per member.
3. Define no-answer path: voicemail, overflow group, mobile/find-me, or queue — link the queues/IVR buyer guide if you need holding; link auto attendant if callers should press 1/2 first.
4. Separate VIP / executive DIDs from the noisy main line so executives are not in the all-hands ring.

Week 3 — Build in SessionPBX (hosted PBX)

1. Create groups and assign members (desk phones + softphones) in SessionPBX / hosted PBX — this is where inbound call routing is configured.
2. Align softphone registrations and presence so remote staff are in the same ring rules (softphone setup checklist).
3. Confirm SIP trunk / DID assignment so the right number lands on the right group; verify firewall/ports so softphones can actually ring.
4. Document a change process: routing edits only via ticket; no silent after-hours rewires.

Week 4 — Test & cutover

1. Test matrix: open hours, closed hours, all members busy, one member DND, softphone offline, desk phone unplugged.
2. Record expected ring order and voicemail greetings; have a rollback (previous forward or temporary simultaneous ring).
3. Train reception/sales on who is in which group and how to escalate.
4. Review monthly when headcount or departments change; keep multi-site rules linked to the multi-location post if you add branches.

Sanity-check VoIP network requirements so audio quality matches the routing design. For a wider feature map, see small business phone system features.

How do softphones, SIP trunks, and SessionPBX fit into day-to-day routing?

Think of three layers:

• SessionPBX (hosted PBX) — control plane for ring groups, hunt groups, schedules, and no-answer paths. Configure inbound call routing at sessiontalk.io/hosted-pbx.
• SIP trunk / DIDs — how public numbers enter the PBX (SIP trunk for small business). Wrong trunk assignment means perfect groups never see the call.
• Endpoints — desk phones and softphones that ring. Softphones join the same SessionPBX groups when registered; they are not a substitute for PBX routing. Day-one install stays in the softphone setup checklist; SessionTalk softphone trials on sessiontalk.io are secondary after hosted PBX rules exist.

Day-to-day: add or remove group members on join/leave, keep firewall and Wi-Fi healthy so remote softphones stay in the ring (VoIP firewall ports, VoIP network requirements), and change routing only via ticket — surprise Friday rewires are how Monday's main line goes to voicemail. After-hours schedules belong in the out-of-hours design, not as leftover Christmas forwards.

This playbook stays on business-hours inbound ring and hunt design — not an IVR tutorial, contact-centre skills guide, or vendor bake-off.

FAQ

What is call routing for a small business?

The rules that send an inbound call to the right ring group, hunt group, person, or overflow path on your phone system — so customers reach a human (or the right menu) without IT guessing who should pick up.

What is the difference between a ring group and a hunt group?

Both send one call to multiple people. A ring group usually rings members together or by a simple rule; a hunt group typically walks members in order. Product UIs differ — define the behaviour you want and configure SessionPBX to match.

How is call routing different from an auto attendant or IVR?

An auto attendant/IVR asks the caller to choose (press 1 for sales). Call routing is what happens when the call should ring people — with or without a menu first. See the live auto-attendant post for menus; keep this post on ring/hunt behaviour.

Do remote softphones work in the same ring groups as desk phones?

Yes, if they are registered members of the same SessionPBX group and network/firewall allow SIP. See softphone setup plus the VoIP network and firewall/ports checklists.

Should we use a call queue instead of a ring group?

Use a queue when callers should wait in line with hold treatment and agents log in/out. Use a ring/hunt group when a small team should simply ring until answered. Evaluate queues with the queues/IVR buyer guide — do not clone that post here.