Skip to main content
June 29, 2026 · By Piyush Sahoo · Updated November 3, 2026 Call routing is how a phone system chooses who answers each call. Your rules might send it to a person, a team, a phone menu, voicemail, or a voice AI agent, based on the time, the caller, what they need, and who is free. Good routing gets callers to help with fewer transfers. This guide is for business owners and support leads. It explains the methods in plain language, helps you choose one, shows what extra queues cost in staff, and covers the Indian rules that shape routing decisions.
Key takeaways
  • Routing is a decision, not a feature. It answers one question on every call: given this caller at this moment, who should pick up?
  • Start simple. Most small teams need open hours, a way to share calls, and a backup for missed calls.
  • Every extra queue costs people. In our example, the same calls need 14 agents in one team and 20 across four queues.
  • Never leave a dead end. Each path should finish with a person, a message, or a promised callback.
  • India changes the rules. Mobile numbers don’t show location reliably, and rules affect overseas routing, number series, and loan recovery hours.

What does call routing actually do?

Picture a good receptionist. They know when the office is open, who handles what, and who is already on a call. Call routing writes that knowledge down as rules, so it works on every call, at any hour, and at any volume. The rules can be one line, such as “ring the front desk”. They can also check several facts, such as whether you’re open, who the caller is, and which team speaks their language. Four terms get mixed up constantly, and a call routing system and an automatic call distributor are often treated as the same thing. Separating the jobs makes planning easier:

What happens during a routed call?

Each call passes through the same four stages, whether your setup is simple or elaborate. Four-stage flow of a routed call. The call arrives with the dialled number, caller number, and time. Rules ask whether you are open, who is calling, what they need, and who is free. The call connects to a person, menu, voice AI agent, or voicemail. If nobody answers, a backup loops the call back to the next destination. Four-stage flow of a routed call. The call arrives with the dialled number, caller number, and time. Rules ask whether you are open, who is calling, what they need, and who is free. The call connects to a person, menu, voice AI agent, or voicemail. If nobody answers, a backup loops the call back to the next destination. Stage four is the one businesses forget. Every flow should end in a fallback for unanswered calls. Without one, your rules can work exactly as written and still lose the customer. Even the number dialled carries information. Some ad campaigns use their own numbers to track responses. A number printed on one flyer can also ring the team running that offer.

Which routing methods can you use?

Lists of routing types vary in length. The names matter less than the question each method answers, and there are only two questions.

Who in this team takes the call?

Which team or destination suits this caller?

For calls you place rather than receive, routing has a different meaning. Least-cost routing picks the cheapest carrier path for an outbound call, so it’s about cost and doesn’t affect who answers.

How do you choose the right method?

Work down this map, and stop at the first yes. Most businesses end up with one answer here, plus open hours and a backup. Decision map with five questions. Placing the calls yourself leads to routing by call purpose. A few people who can take any call leads to ringing together or fixed order. A larger team doing the same work leads to longest idle or round robin. Callers needing different skills or languages leads to a short menu, skills routing, and a shared overflow team. Records that identify the caller lead to relationship or customer-data routing. If every answer is no, start with open hours and one number. Decision map with five questions. Placing the calls yourself leads to routing by call purpose. A few people who can take any call leads to ringing together or fixed order. A larger team doing the same work leads to longest idle or round robin. Callers needing different skills or languages leads to a short menu, skills routing, and a shared overflow team. Records that identify the caller lead to relationship or customer-data routing. If every answer is no, start with open hours and one number.

Does splitting a team into more queues help?

Only up to a point, and none of the guides we read puts a number on this cost. Sending callers to specialists improves the match, but it also divides your team into smaller groups. Calls never arrive evenly. A large shared team absorbs a sudden cluster, because someone is usually free. A small queue can’t, so it has to keep more spare people for the same service. To size this effect, we ran the numbers with Erlang C, a standard formula for staffing queues. We used 120 calls an hour, five minutes per call, and a target of 80% answered within 20 seconds. Bar chart of agents needed for the same 120 calls an hour. One shared team needs 14 agents. Two equal queues need 8 each, or 16 in total. Four equal queues need 5 each, or 20 in total. The figures are an illustrative Erlang C calculation by Vobiz. Bar chart of agents needed for the same 120 calls an hour. One shared team needs 14 agents. Two equal queues need 8 each, or 16 in total. Four equal queues need 5 each, or 20 in total. The figures are an illustrative Erlang C calculation by Vobiz. Four separate queues need six more agents than one shared team, with no extra calls to handle. The formula assumes callers never hang up, so treat these figures as a guide to the pattern rather than a staffing plan. Three habits keep the cost down:
  • Split only when you must. Language and regulated work may require it. “Sales” and “enquiries” often don’t.
  • Train people across queues. Someone who handles two queues helps both.
  • Let queues overflow. Ring the best-matched group first, then widen to anyone who can help.

What does a good routing plan look like?

Here is one plan for an imaginary home services company in Bengaluru, with 12 staff who speak Kannada, Hindi, and English. It handles a mix of new enquiries and customers with jobs in progress. Example routing plan. A customer calls the business number. If the company is closed, the caller hears a closed message and reaches voicemail, with a callback the next day. If open and the caller has an open job, their coordinator rings for 20 seconds. Other callers choose Kannada, Hindi, or English, and that language team rings for 20 seconds. Unanswered calls from either path ring everyone on shift, then reach voicemail with a callback within the hour. Example routing plan. A customer calls the business number. If the company is closed, the caller hears a closed message and reaches voicemail, with a callback the next day. If open and the caller has an open job, their coordinator rings for 20 seconds. Other callers choose Kannada, Hindi, or English, and that language team rings for 20 seconds. Unanswered calls from either path ring everyone on shift, then reach voicemail with a callback within the hour. The order of the checks is deliberate:
  1. Hours come first. Nobody should sit through a menu only to learn you’re closed.
  2. Records come before the menu. A customer with an open job shouldn’t have to explain themselves to a machine.
  3. The menu stays short. It has one level, and pressing nothing still reaches a person. Our guide to multi-level IVRs covers when deeper menus are worth it.
  4. Overflow beats perfection. After 20 seconds, a less-matched colleague is better than more ringing.
  5. Missed calls have an owner. A named person returns voicemails by a stated time.
Salesforce suggests offering a callback rather than an endless hold. Before you build your own plan, answer these questions on one page:
  • What are the five most common reasons people called last month?
  • What are your real open hours, including public holidays?
  • Who can take which kind of call, and in which languages?
  • How long should a phone ring before the call moves on?
  • Who returns missed calls, and how quickly?
Then ring your own number, on a mobile, at different times of day. You’ll find problems no diagram shows.

What changes when you route calls in India?

None of the general guides we read covers the rules below, yet these six points change routing decisions in India. Rules change often, so confirm the current text and take legal advice for your own case. Language deserves extra thought in India, because it can turn one team into several small ones. Check how many calls really need each language before you create a queue for it. A rarely used language may work better as overflow to two bilingual colleagues. Some guides suggest passing calls to an office in another time zone once yours closes. Before you copy that idea for Indian numbers, check the overseas point in the table above.

Should a voice AI agent answer first?

It can, for calls with predictable reasons, such as booking status or opening hours. A voice AI agent becomes one more destination in your plan. It can also do the sorting a menu used to do, by working out what the caller wants from what they say. Treat it like any other destination, with a backup. Decide which requests always go to a person, such as complaints or anything involving money. Make sure the handover works during busy hours too, and pass along what the caller already said so they needn’t repeat it.

How do you know your routing is working?

Review these monthly, and again after changing a rule.

How Vobiz handles call routing

Vobiz is programmable telephony: it runs the routing decisions your application makes. You attach a number to an application. When a call arrives, Vobiz sends a webhook (callback) to your server, and your server replies with VobizXML instructions. Your application holds your rules, staff list, and customer records, so it can apply any method in this article. Here is how each part of a plan maps to Vobiz:
  • Menus. Gather collects key presses and speech. Play plays your recorded MP3 or WAV prompts, which suits a regional-language menu, and Speak reads text aloud.
  • Ringing together. Several numbers inside one Dial ring at once. The first to answer gets the call, and the others stop ringing.
  • Fixed order. Your application returns one destination at a time and moves on when a call attempt fails.
  • Staff on browsers or softphones. User rings a SIP or registered WebRTC endpoint rather than a phone number.
  • Moving a live call. Redirect sends the call to new instructions, and call transfer moves a call that’s already in progress. Call escalation covers tiered handovers.
  • Backups. An application’s fallback_answer_url takes over if your main server can’t be reached, times out, or returns invalid VobizXML. You can also make one application the default for new numbers created without one.
  • Your own phone system. If you already run a PBX, an inbound trunk can deliver calls to it instead.
  • Voice AI. Stream sends live call audio to your AI agent’s server, with guides for platforms such as LiveKit and Bolna.
  • Outbound. Campaigns let you set a daily calling window, a time zone, and retry attempts.
  • Review. Call logs and call detail records show how each call ended, and hangup causes explain why.
Vobiz is available in 130+ countries, and current rates are on the Vobiz pricing page. To see a full build, read about cloud IVR and contact centres on Vobiz. Test calls are billed to your account, so run them with your own Auth ID and Auth Token, and confirm the numbers first.

Frequently asked questions

Call routing is a set of rules that works like a receptionist. It looks at each incoming call, then sends it to the person, team, menu, or voicemail box you chose for that situation. You decide the rules once, and they run on every call.
Call forwarding moves calls from one number to another, usually for one simple reason such as no answer. Call routing makes a choice on each call, using facts such as the time, the caller, and who is free. Forwarding can be one step inside a routing plan.
Some methods share calls within a team, such as ringing together, fixed order, round robin, and longest idle. Others pick the right team, such as phone menus, time of day, skills or language, priority, and customer data. Many businesses combine two or three.
Yes, if a missed call costs you work, though you only need a little. Ring your few staff together or in order, send closed-hours calls to voicemail, and name who calls back. Add a menu only when callers really need different people.
No. An IVR is a phone menu that asks callers what they need. Call routing is the wider set of rules that uses that answer, along with other facts, to choose a destination. You can route calls well without any menu.
Not reliably from a mobile number alone. Since July 2015, Indian subscribers can keep a mobile number when they move to another service area, so the number may not show where someone lives. Use a language menu, or the address in your customer records.

Further reading on Vobiz

Sources

Indian regulators and government data Reference

Build on Vobiz

Provision a number and wire up programmable call routing in minutes.