Routing design

Every call should have a plan before it rings.

Call routing is the set of rules between a caller dialling your number and a person saying hello. Get it right and callers reach the right department first time; get it wrong and every call is a transfer.

Business call routing is the set of rules that decides where an incoming call goes: which greeting plays, which menu options are offered, which people or departments ring, in what order, and what happens if nobody answers. It combines a main menu, ring groups or queues, overflow rules and time-of-day schedules. 3CTel designs and configures these rules with you, then tests them on a temporary number before go-live.

The five building blocks

Almost every routing plan, from a three-person shop to a fifty-agent desk, is assembled from the same five parts. Knowing what each one does makes the design conversation short.

Main menu (auto attendant)

The greeting and the options. It sorts callers by intent: sales, service, accounts, a specific person. Two to four options is the practical range.

Department routing

Each menu option, or each direct number, lands on a department. A department is a group of people plus the rules for how they ring.

Ring groups

Ring several people at once, or one after another, for a set number of seconds. Simple, fast and right for small teams where anyone can answer.

Call queues

Hold callers in order, play position or hold music, and deliver each call to the next available agent. Right for teams that get more calls than they can answer at once.

Time-of-day rules

Different paths for open hours, lunch, evenings, weekends and holidays. Every other block can behave differently depending on when the call arrives.

Ring group or queue: choosing correctly

The most common routing question is whether a department should be a ring group or a queue. The answer depends on how often more callers arrive than there are people to answer.

If a second call while the first is still ringing is rare, use a ring group: everyone rings, the first free person answers, and an unanswered call goes to a fallback. If simultaneous calls are normal, use a queue: callers hold in order, hear their position, and are delivered one at a time, with a callback offered when the wait grows.

  • Ring group: small teams, low simultaneous volume, no reporting required beyond missed calls.
  • Queue: support desks, order lines, anywhere callers regularly wait; reporting on wait times and abandonment is available.
  • Both: a ring group for the front desk with overflow into a queue when the group is busy is a frequent pattern.

A worked routing example

Illustrative rules for a twelve-person distribution business with a sales team, a customer service desk and a warehouse. Each row is one rule: the condition on the left, the outcome on the right.

Illustrative example. Ring times, overflow order and options are set with you during planning.
WhenThen
Main number, Monday to Friday 8:00 to 17:00Greeting → press 1 sales, 2 customer service, 3 warehouse, 0 or stay on the line for reception
Caller presses 1 (sales)Ring group: three sales reps ring together for 25 seconds → overflow to the sales manager → voicemail to email
Caller presses 2 (customer service)Queue: four agents, longest-idle first, position announcement every 45 seconds → callback offered after 2 minutes
Caller presses 3 (warehouse)Ring group: warehouse desk phone and the supervisor's mobile app → voicemail to email with transcript
Caller stays on the lineReception extension for 20 seconds → overflow to the customer service queue
Customer service queue has no agents signed inSkip the queue → AI receptionist takes the details and creates a callback
12:00 to 13:00 weekdaysSales and warehouse ring groups also include the reception extension so lunch coverage is shared
After 17:00, weekends and statutory holidaysClosed greeting → press 1 for the on-call number (urgent orders) → otherwise AI receptionist or voicemail
Caller dials a direct extensionThat person rings for 20 seconds → their personal fallback (colleague or voicemail)

Overflow: the rule people forget

Every destination in a routing plan needs an answer to 'and if they do not pick up?'. That answer is the overflow rule; leaving it blank is how calls ring forever or drop.

  1. Set a ring time for every group

    Twenty to thirty seconds is typical. Longer than that and callers hang up; shorter and people cannot reach their phone.

  2. Choose the next destination

    Another group, a manager's extension, a queue, the AI receptionist or voicemail. Each is a legitimate choice; 'nothing' is not.

  3. Chain at most twice

    Group → manager → voicemail is fine. Four hops is a caller who has been ringing for two minutes and is now annoyed.

  4. Treat empty queues differently

    A queue with no agents signed in should skip straight to the fallback rather than holding a caller for nobody.

AI agents in your call routing

AI does not replace the building blocks above; it becomes one of them. The AI Receptionist sits at the front of the flow or at the overflow point, resolving routine calls and handing the rest to a queue with the reason already captured. AI communication optimization then reviews the routing you built against real call data and proposes adjustments, which you approve before anything changes.

AI Receptionist as a routing step

Place the AI Receptionist before the menu to answer common questions, or after the ring group as overflow. It identifies intent, transfers with context or books a callback into the right team’s queue.

Routing recommendations you approve

AI communication optimization studies where calls wait, abandon or bounce between groups, recommends changes to ring times, overflow paths and callback thresholds, and estimates the effect of each before you apply it.

Every routed call logged where it belongs

After the call, an AI workflow logs the summary against the right contact and department in your CRM or helpdesk and schedules the callback the agent promised, in the approval mode you choose.

Routing questions we hear most

How many menu options should a main menu have?

Two to four. Callers hold a short list in their head and start pressing buttons before a long one finishes. Lead with the most common reason to call, keep 'stay on the line' as a way to reach a person, and put rarely used destinations behind a direct number instead of on the menu. Menus can be changed in minutes once real calls show what works.

Can calls be routed by the caller's number or area code?

Yes. Rules can look at the calling number and send known customers to their account manager, send callers from a particular region to the nearest branch, or bypass the menu for a VIP list. These rules sit in front of the main menu and are configured with 3CTel during planning, using lists you maintain.

What is the difference between an IVR and an auto attendant?

In everyday business use they are the same thing: a recorded menu that routes callers by keypress. Strictly, an IVR can also collect information such as an account number and look it up before routing, while an auto attendant only routes. Most businesses need the simpler auto attendant; an IVR is used where callers must identify themselves first.

Frequently asked questions.

Yes. Ring times, group membership, hours and greetings are edited in the console by your administrator. Larger changes, such as a new department structure, can be made by 3CTel on request.

Draw your call flow with a specialist.

Bring your departments, your hours and your busiest hour of the week. We will turn it into routing rules, build it on a test number and let you hear it before anything goes live.

Call 3CTelBuild My System