Can a single temporary number stop missed incidents and cut response time?
Enable the live line feature to assign a dedicated number that forwards incoming items to the right on-call responder. Configure LCR once account features permit. The number acts as a single point of contact for teams and reduces handoffs.
Use the LCR setup to map schedules and escalation steps. Grant full management rights to standard users; limit access for restricted roles. Automate triggers to lower MTTA and MTTR — measure the impact with time-based metrics.
Maintain 24/7 coverage with a managed phone line and clear responder assignments. Test the number and failover logic before production. Log every event for post-incident analysis.
Key Takeaways
- Assign a single dedicated number to centralize incoming incidents.
- Enable LCR on the account before configuring the number.
- Map schedules to ensure the correct responder receives the alert.
- Automate triggers to reduce mean-time-to-acknowledge and mean-time-to-resolve.
- Grant management rights to appropriate users and audit changes.
Understanding the Role of PagerDuty Off Call Routing
Dynamic live call delivery aligns incoming contacts with the right responder based on schedule and escalation logic. Implement the service to maintain continuity during incidents.
Core Functionality
Live call routing maps on-call schedules to a single routing number. The system evaluates escalation policies and forwards calls or voicemails to the active on-call responder.
Availability depends on plan tier — offered as an add-on for Professional and Business customers and included in Enterprise. LCR extends phone-based incident support into operations workflows.
Business Benefits
Reduce time to acknowledge — direct delivery eliminates manual transfers and missed notifications. Track metrics to quantify improvements in time to resolve.
Ensure customer access — customers and teams reach the right responder any time. Configure a call routing number to capture calls, voicemails, and escalation cases during major incidents.
- Maintain operational continuity through schedule-driven delivery.
- Use professional business plans to unlock full live call routing features.
- Support diverse use cases — support, incident response, and global operations.
Configuring Your Live Call Routing Setup
Provision a phone number via the Integrations → Live Call Routing pane to centralize incoming lines.
Select country and a preferred area code when prompted. Choose a local number to improve reach for customers and teams.
Associate up to nine services with a single live call routing number to build a phone tree. This structure routes escalation paths to the correct on-call teams.
- Navigate to the call routing page in the web app to add a new number for your team.
- Only Manager-level users may view, add, edit delete numbers and configurations on the routing page.
- Digital Operations plans include one free line for small accounts; other business plans may include three lines.
- Use the service association to ensure calls reach the on-call responder and reduce time to acknowledge.
| Step | Action | Outcome |
|---|---|---|
| 1 | Open Integrations → Live Call Routing | Begin provisioning a routing number |
| 2 | Select country and area code | Improve local reach for customers |
| 3 | Associate services (up to nine) | Create phone tree and map escalation |
| 4 | Assign Manager access | Control edit delete permissions |
Managing Escalation Policies and Incident Triggers
Establish deterministic escalation behavior so a live contact follows the intended path to an on-call responder.
Set escalation timing. The default interval before escalation is 20 seconds. Adjust the timer per policy to match response SLAs.
Handle unanswered engagements. If no one answers, prompt the caller to leave a message. That voicemail then triggers an incident for the on-call responder.
Customizing Greeting Messages
Use clear greetings to guide callers. Create short, service-specific greetings to help customers reach the right team and reduce misrouted incidents.
- Show either the incoming number or the live line number on responder displays.
- Configure automatic incident resolution when the responder completes the interaction.
- When multiple people share the first escalation level, assign the incident to all on-call responders simultaneously.
- Edit delete routing number settings on the call routing page to refine triggers and behavior.
| Action | Default | Configurable |
|---|---|---|
| Escalation delay | 20 seconds | Yes |
| Voicemail -> incident | Enabled | Yes |
| Auto-resolve after answer | Optional | Yes |
Optimizing Call Routing for Global Teams
Provision phone numbers by region to guarantee consistent connectivity for dispersed responders and customers.
Choose local numbers in Australia, Canada, the United Kingdom, and the United States to lower latency and improve delivery for live call routing.
Use a centralized call routing number to reach right experts across time zones. Enable the available-add-on to provision additional phone numbers and extend operations internationally.
Note: Toll-free numbers require separate administration and may need Sales for upgrades. Chinese prefix numbers (+86) remain unsupported as of November 2023.
- Select a regional number where most responders reside to reduce failures.
- Associate one routing number with services and escalation workflows to maintain coverage.
- Use local and international numbers to support diverse use cases and on-call teams.
| Number Type | Regions Supported | Requires Sales |
|---|---|---|
| Local number | AU, CA, UK, US | No |
| Toll-free | Multiple (admin handled separately) | Yes |
| International number | Global where phone notifications work | Depends |
Troubleshooting Common Connectivity and DTMF Issues
Confirm media-level DTMF handling at the gateway. Verify that DTMF transmits out-of-band using RFC-2833 (RTP events). Telephony providers require RTP events to detect digit presses during a live call routing session.
Addressing DTMF Compatibility
Do not use in-band DTMF or SIP INFO methods. Those methods will not be detected. Ensure Cisco Webex Calling gateways are configured for RFC-2833.
Check payload types. Use the expected DTMF payload (typically 101). Test digit presses end-to-end. If responders cannot accept by pressing “1,” the signaling method likely fails.
Verifying Service Availability
If callers hear a message that the line is not set up, confirm at least one active service is associated with the routing number. Confirm an active on-call responder is assigned to that service.
- Verify gateway uses RFC-2833 — eliminate in-band DTMF.
- Confirm DTMF payload type — typically 101 — matches provider expectations.
- Check service association for the routing number and on-call responder assignment.
- Provide support with call SIDs and timestamps for complex troubleshooting.
| Issue | Likely Cause | Action |
|---|---|---|
| Digits not detected | In-band DTMF or SIP INFO | Switch gateway to RFC-2833; test RTP events |
| Line plays “not set up” | No service associated | Associate a service with the routing number; add on-call responder |
| Intermittent failures | Incorrect payload type | Confirm payload 101; capture call SID for support |
Streamlining Incident Response for Future Operations
,
Treat each routing number as a measurable asset. Track delivery metrics, incident volume, and escalation timing. Use that data to refine live call routing and on-call schedules.
Apply digital operations principles—standardize workflows, automate handoffs, and enforce periodic reviews. Validate that each service maps to an appropriate escalation and that an on-call responder can be reached rapidly.
Document configuration changes. Run post-incident analyses and adjust the number and escalation rules based on use cases and time-to-resolve metrics.
Next step: Consult the incident management platform for guided best practices and integration options: incident management.
