Sequential Call Routing API: Automate Multi-Number Call Sequences
Build Intelligent Call Sequences with the Simple Telecom Routing API — Never Miss a Call
Key Sequential Routing Features
- Create multi-step call sequences with configurable ring durations
- Add the same number multiple times with different ring times
- Set display names to identify each forwarding destination
- View the complete routing sequence with position ordering
- Update or remove individual steps in the sequence
What Is Sequential Call Routing?
Sequential call routing is a call management technique where incoming calls are directed through a predefined sequence of phone numbers. The system rings the first number for a set duration. If there’s no answer, it automatically moves to the next number in the sequence. This continues until someone answers, or until all numbers have been tried. It’s a simple but powerful way to ensure every call reaches a live person, maximising the chance of connecting with customers.
Small businesses might use a two-step sequence: ring the office phone for 15 seconds, then forward to a mobile. Larger organisations might use complex sequences involving multiple team members, voicemail, and overflow destinations. The Simple Telecom Routing API gives you complete control over these sequences, letting you create, modify, and manage them programmatically.
For Australian businesses with 1300 or 1800 numbers, sequential routing is one of the most valuable features. It ensures that a professional national number doesn’t just ring endlessly — calls are intelligently directed to the right person at the right time, improving customer experience and conversion rates.
How Sequential Routing Works with the API
In the Simple Telecom Routing API, each forwarding number is an entry in a sequence. The position field determines the order, and the duration field controls how many seconds the system will ring that number before moving to the next. The display_name field helps you identify each entry — for example, ‘John Mobile’, ‘Office Desk’, ‘Backup VOIP’.
To create a sequential routing setup, you add forwarding numbers one at a time using the POST /api/services/{service_id}/routing/forwarding endpoint. Each new number is added to the end of the sequence. If you need a specific order, add them in the order you want them to ring.
The default ring duration is 180 seconds (3 minutes) per number, but you can customise this per entry. For a typical business sequence, you might set 15 seconds for the first attempt (quick ring, move on), 30 seconds for the second, and 180 seconds for the final destination. This ensures calls flow through the sequence efficiently without excessive waiting at any single number.
Advanced Sequential Patterns
The API supports several advanced patterns beyond simple linear sequences. One powerful technique is same-number sequential calling, where you add the same phone number multiple times with different durations. For example, add a mobile number with a 15-second duration, then other numbers in the sequence, then add the same mobile number again with a 180-second duration. This creates a pattern where the system quickly tries the mobile, attempts other destinations, and finally returns to the mobile for a longer ring.
Another pattern is time-based escalation. During business hours, you might have a short sequence (office → mobile → voicemail). After hours, you can use the API to switch to a different sequence (mobile → home office → voicemail). By updating the forwarding configuration at scheduled times, you create an automatic escalation system based on the time of day.
Overflow routing is a third pattern. When your primary team is busy, you can add overflow numbers at the end of the sequence — additional team members, a backup mobile, or a voicemail service. Calls that aren’t answered by the primary team within their ring durations automatically flow to the overflow destinations.
Building a Complete Call Handling Strategy
A well-designed sequential routing strategy ensures every caller reaches someone who can help them. Here’s a typical setup for an Australian business with a 1300 number:
Step 1 (15 seconds): Ring the primary sales desk. This is your main number, but the short duration means calls move quickly if no one is available.
Step 2 (20 seconds): Ring the secondary sales desk or a colleague’s mobile. This ensures coverage if the primary desk is temporarily unattended.
Step 3 (30 seconds): Ring the manager’s mobile or a senior team member. Escalation to someone with more authority to handle the call.
Step 4 (180 seconds): Voicemail or a final answered destination. If no one has answered by this point, the caller can leave a message or reach a guaranteed-answered service.
This structure ensures calls are handled efficiently: quick attempts at the primary team, escalation to backups, and a safety net at the end. The API lets you build and modify this strategy programmatically, adapting to changing team structures and business hours.
Automating Sequential Routing Updates
One of the key advantages of API-based sequential routing is the ability to automate updates. Here are practical automation scenarios:
Shift-Based Routing: Connect to your staff scheduling system. When a morning shift starts, set the sequence to ring morning team members first. When the afternoon shift starts, update the sequence to ring the afternoon team. This ensures calls always go to the right people without manual routing changes.
Holiday Routing: Automatically update routing for public holidays. Switch to a reduced sequence (manager mobile → voicemail) on holidays, then restore the normal sequence on the next business day. This can be scheduled months in advance.
Performance-Based Routing: Use CDR data to identify which team members answer calls most quickly and effectively. Automatically adjust the routing sequence to prioritise your best-performing staff during peak hours.
Monitoring and Optimising Your Sequence
Once your sequential routing is in place, use the CDR API to monitor its effectiveness. The destination field in CDR records shows which forwarding number the call was ultimately connected to. By analysing this data, you can see which positions in your sequence actually answer calls, and at what stage in the sequence calls are typically answered.
If you notice most calls are answered at position 3 or 4, your sequence may be too long — consider moving the effective numbers earlier. If calls are frequently not answered at all, consider adding more destinations or extending ring durations. The combination of the Routing API (for configuration) and the CDR API (for monitoring) gives you a complete feedback loop for optimising your call handling strategy.
Regular review of your sequential routing configuration ensures it continues to meet your business needs as your team, hours, and call volumes change. The API makes it easy to iterate — test a new sequence, monitor the results with CDR data, and refine as needed.
Frequently Asked Questions
Frequently Asked Questions About Sequential Call Routing
How many numbers can I add to a sequential routing sequence?
There’s no hard limit on the number of forwarding numbers in a sequence. However, a sequence of 3–5 destinations is typically sufficient for most businesses. Longer sequences may frustrate callers waiting for someone to answer.
What happens if all numbers in the sequence are unanswered?
If no one answers at any destination, the call is typically disconnected or sent to voicemail depending on your service configuration. Consider adding a voicemail or auto-attendant as the final step in your sequence.
Can I have different sequences for different times of day?
Yes. Use the API to update the forwarding configuration at scheduled times — for example, at 9am switch to a business hours sequence, at 5pm switch to an after-hours sequence. This can be automated with a simple scheduled task.
Does sequential routing work with call recording?
Yes. Call recording is configured per service, not per forwarding number. If recording is enabled, all calls to that service are recorded regardless of which forwarding number answers the call.
Can I see which number in the sequence answered a call?
Yes. The destination field in the CDR API response shows which number the call was connected to, which corresponds to a forwarding number in your sequence.
Sequential call routing automates how incoming calls flow through your team, ensuring no customer gets missed while you manage costs effectively. Understanding the 1300 number cost to call helps you budget for inbound campaigns, while businesses serving international clients appreciate knowing they can call 1300 numbers overseas without complications. This automation streamlines operations across your national presence, making customer communications smoother and more professional.
