πŸ“ž Call Routing

Overview

Call Routing determines:


  • Which calling channels are available: FaceTime, Android, WhatsApp, and Twilio.
  • The order in which calling lines are attempted when a call cannot be connected.
  • How lines within the same row are treatedβ€”as alternatives rather than backups.
All routing behaviour is controlled through the Call Routing grid.
Call Routing is the voice equivalent of Message Routing. Message Routing selects backup channels for messages, while Call Routing selects backup lines for calls.


Call Routing dialog: Rows represent priority levels (Primary, Backup 1, and Backup 2), while columns represent FaceTime, Android, WhatsApp, and Twilio.
Section 1: Accessing Call Routing
  1. Navigate to Subaccount SIM.
  2. Locate the required subaccount.
  3. In the Call Routing column, click the Call Routing button next to Message Routing.
The Call Routing dialog will open.
Note: The dialog also opens automatically when a calling device is connected to the subaccount. Click the β“˜ icon next to the dialog title to open the built-in Call Routing guide.
πŸ“ž Call Routing, screenshot 1
Section 2: Understanding the Routing Grid
The Call Routing grid follows two main rules.
Rows = Backup Order

If a call cannot be connected through the selected line, the system moves to the configured lines in the next row.

Same Row = Alternative Lines

Lines in the same row are alternatives, not backups for one another. You select the line to use when placing the call. If the call fails, the system moves to the next row instead of switching to another line in the same row.

The Grid
Priority

FaceTime 🍏

Android πŸ€–

WhatsApp 🟒

Twilio ☎️

1 Β· Primary β€” Try First

☐

☐

☐

☐

2 Β· Backup 1

☐

☐

☐

☐

3 Β· Backup 2 β€” Last Resort

☐

☐

☐

☐

  • Columns represent the calling channels available to the subaccount.
  • Rows represent priority levels. The first row is attempted first, the second is used if the first cannot connect, and the third serves as the last resort.
  • Select the desired lines by ticking the corresponding checkboxes, then click Save.
πŸ“ž Call Routing, screenshot 2
Section 3: Understanding Routing Logic

3.1 Starting Line vs. Backup Line
A typical routing configuration includes:
  • Starting line: The line the agent selects when placing a call.
  • Backup lines: Additional lines used if the selected line cannot connect the call.
Example configuration
  • Primary (Row 1): Android
  • Backup 1 (Row 2): FaceTime
System behaviour
  1. The system attempts to place the call through the Android phone first.
  2. If the Android phone cannot connect the call, the system attempts the call through FaceTime on the Mac.
3.2 Ordered Backup Sequence
The system follows the priority order configured in the routing grid. Within a row, lines are ordered from left to right.
Example sequence
  • Primary: Android
  • Backup 1: FaceTime
  • Backup 2: Twilio
System behaviour
The system proceeds through the configured rows until:
  • The call is successfully connected, or
  • All available routing options have been exhausted.
A backup call uses the calling line associated with the relevant subaccount, such as its Mac, Android phone, or default Twilio caller ID. This helps ensure that the contact sees the appropriate number.
If a call is initiated from a line that is not included in the grid, the system falls back to the configured lines in the grid.
3.3 Multiple Lines in the Same Row
Lines selected in the same row are alternatives, not backups for one another. The agent chooses which line to use when placing the call. If that line fails, the system moves to the next row instead of switching to another line in the same row.
Example configuration
  • Primary (Row 1): FaceTime and Android
System behaviour
  • Both lines are available as choices on the call button.
  • The call starts through the line selected by the agent.
  • If the selected line fails, the system moves to the next rowβ€”not to the other line in Row 1.
Section 4: Channel-Specific Requirements
4.1 FaceTime
Requirements
  • A Mac must be connected to the subaccount, with the Mac gateway app running version 0.9.55 or later.
  • Calling must be enabled for the iMessage/Mac line under Plans β†’ Calling β†’ iMessage.
  • FaceTime must be available and working on the Mac, which must be signed in with the correct Apple ID.
Notes
  • FaceTime calls can reach only Apple devices.
  • FaceTime cannot distinguish a declined call from a failed call. Therefore, a declined FaceTime call also triggers the backup route.
4.2 Android
Requirements
  • Android app version 10.9.11 or later.
  • A calling line enabled for the device's SIM under Plans β†’ Calling β†’ Android.
⚠️ Important: Only a phone with browser audio (a calling line on its SIM) can take over a call. A phone that can only ring the contact directly through its SIM is skipped as a backup.
Notes
  • Android is the only channel used by the Outbound Missed Call automation action.
  • The phone must be online, and the gateway app must be running, for the call to be placed.
4.3 WhatsApp
Requirements
  • A WhatsApp number must be connected to the subaccount.
  • Calling must be enabled under Plans β†’ Calling β†’ WhatsApp.
Notes
  • Enabling WhatsApp calling uses one purchased calling line.
  • If no WhatsApp number is connected, the grid displays the channel as unavailable.
4.4 Twilio
Requirements
  • Twilio calling must be enabled under Plans β†’ Calling.
  • A default Twilio caller ID must be selected for the subaccount under Twilio β†’ Calling.
Notes
  • Calls are placed through your own Twilio account, and Twilio bills you directly.
  • Without a default caller ID, the system cannot determine which number to use for a backup call.
Section 5: Common Scenarios
Scenario A β€” Android Preferred, FaceTime Backup
Configuration
  • Primary: Android
  • Backup 1: FaceTime
Behaviour
  • The system attempts the Android phone first.
  • If the phone cannot connect the call, the system attempts FaceTime.
Requirements
  • An Android calling line enabled on the SIM.
  • A Mac with iMessage calling enabled.
Scenario B β€” FaceTime Preferred, Twilio Backup
Configuration
  • Primary: FaceTime
  • Backup 1: Twilio
Behaviour
  • The system attempts FaceTime on the Mac first.
  • If the Mac cannot be reached or the call ends before anyone answers, the system attempts Twilio.
  • If the contact does not use an Apple device, the call is placed through Twilio instead.
Requirements
  • A Mac with iMessage calling enabled.
  • Twilio calling enabled, with a default caller ID configured.
Scenario C β€” Agent Chooses the Calling Line
Configuration
  • Primary: FaceTime and Android
  • Backup 1: Twilio
Behaviour
  • The agent selects either FaceTime or Android when placing the call.
  • If the selected line fails, the system attempts Twilio.
  • The system does not switch to the other line in Row 1.
Section 6: Saving the Configuration
After configuring the routing grid:
  1. Review the selected lines.
  2. Verify the backup order.
  3. Confirm which lines share the same row.
  4. Click Save to apply the configuration.
The panel at the bottom of the dialog describes the behaviour of the current setup.
If no lines are selected, it displays:
No backup lines yet: calls stay on the line you pick, as before.
Saving an empty grid is valid. It means no backup lines are configured, and calls continue to use the line selected by the agent.
Section 7: Configuration Notes
  • Call Routing is configured separately for each subaccount.
  • The order of the rows determines the backup execution sequence.
  • Reordering rows changes the routing priority.
  • Lines in the same row are alternatives. A failed call never moves sideways to another line in that row.
  • A backup call uses the calling line associated with the relevant subaccount.
  • A call initiated from a line that is not included in the grid falls back to the configured lines in the grid.
  • Only qualifying connection failures trigger a backup attempt, such as an unreachable Mac, an Android phone that cannot place the call or carry its audio, or a call rejected by Twilio.
  • A busy line, a declined call, or an unanswered call on Android or Twilio does not trigger another attempt through a backup line.
  • The Outbound Missed Call automation action follows the same routing order, starting with the top row.
  • The availability of calling lines depends on the devices, calling lines, and plans configured for the account.
Section 8: Implementation Checklist

Use this checklist before finalizing your Call Routing configuration.

Decide on the Starting Line
  • Which calling line should agents use by default?
Define the Backup Order
  • Which line should take over first?
  • Which line should serve as the last resort?
Confirm Calling Line Availability
  • iMessage/Mac: Calling is enabled under Plans β†’ Calling β†’ iMessage.
  • Android: A calling line is enabled on the SIM under Plans β†’ Calling β†’ Android.
  • WhatsApp: WhatsApp calling is enabled if a WhatsApp number is being used.
  • Twilio: Twilio calling is enabled, and a default caller ID is configured if Twilio is being used.
Verify Android Backup Requirements
  • Confirm that the phone has a calling line on its SIM (browser audio).
  • Confirm that the phone is online and the gateway app is running.
Verify FaceTime Backup Requirements
  • Confirm that the Mac is online and signed in with the correct Apple ID.
  • Remember that FaceTime can reach only Apple devices.
Final Check
  • Review the routing grid and confirm the backup order.
  • Click Save to apply the configuration.
Summary
  • Β Call Routing is controlled by the Call Routing grid.
  • Rows define the backup sequence. If a call cannot be connected, the system moves to the next configured row.
  • Lines selected within the same row are alternatives. The agent selects one, and a failed call does not move sideways to another line in that row.
  • Backup calls use the calling lines associated with the relevant subaccount.
  • Only qualifying connection failures trigger a backup attempt. A declined call, a busy line, or no answer on Android or Twilio does not.
  • Call Routing is the voice equivalent of Message Routing and also determines the routing order for the Outbound Missed Call automation action.
Related Articles

Was this article helpful?

0 out of 0 liked this article

Still need help? Message Us