One pattern, ordered
Sequential Call Routing: The Ordered Answer Pattern
Sequential routing tries destinations in a fixed order — the first person free takes the call, then the second, and so on. It is the ordered cousin of round-robin, and choosing between them is a staffing decision more than a technical one.
- Fixed order, first-free wins
- Round-robin compared honestly
- Manageable via Routing API
Sequential routing questions
What is sequential call routing?
A routing pattern where incoming calls are offered to a predefined sequence of destinations — first the primary, then the fallback, then the next. Each call starts at the top of the list, so the first destination gets every opportunity to answer.
How is it different from round-robin?
Round-robin spreads calls evenly across a team so nobody is overloaded; sequential funnels every call through the same order so a primary answer point is always preferred. Choose sequential when priority matters more than evenness — a senior first, juniors after.
Can routing behaviour be managed through the API?
Yes — the Routing Management area of our API controls call forwarding and recording programmatically, so destination changes that implement your routing strategy can follow your systems. The area is described on the API page.
Sequential routing answers a deceptively simple question: when several people could take a call, in what order should the phone try them? The sequential pattern fixes that order permanently — destination one, then destination two, then three — so every call gets its best chance of reaching the preferred answerer before falling further down the list. This page explains the pattern, compares it honestly with round-robin, and shows where the API fits.
How the pattern behaves
A call arrives and is offered to the first destination in the sequence. If that destination answers, the call ends there. If it is busy or unanswered, the call moves to the second destination, then the third — the ordered fallback chain, which is why sequential routing and overflow routing are close cousins. The difference is intent: overflow is a safety net behind one destination, while sequential is a deliberate priority ladder across several.
Sequential versus round-robin
| | Sequential | Round-robin | |---|---|---| | Order | Fixed priority list | Rotating, even spread | | Who answers most | The top of the list | Everyone equally | | Best for | Primary-first teams, expertise tiers | Same-level teams, load balancing |
Both patterns appear in the routing options described in how 1300 numbers work. The choice is organisational: if your team has a genuine priority order — account manager first, backup second — sequential expresses it; if your team shares load equally, round-robin expresses that.
Where the API fits
The routing behaviour lives in the rule-space behind your numbers, and the Routing Management area of the API manages that space programmatically — call forwarding and recording control over RESTful JSON with bearer-token authentication. For sequential setups, the API is most useful when the ladder itself changes: a team member is on leave, a new junior joins the list, a seasonal reorder. Your rostering system knows those facts first; the API lets it make the routing change too. The forwarding-focused walkthrough is in API call forwarding.
Getting started
Sequential routing starts with a number and an honest list of who answers, in order. Standard 1300 and 1800 numbers run from $10 a month, searchable on available numbers, with rates on the pricing page. Configure the ladder in the console first, watch the call reports for a week, and let the API take over the edits once the pattern is trusted.
Numbers that follow your order
Get routing that matches your team
1300 and 1800 numbers from $10 a month, with time, overflow and round-robin patterns available.