Cutting On-Call Telephony Bills: Full-Screen DND Call vs. Direct Cellular Calls

Engineering teams running on-call rotations often pay an unexpected monthly telephony tax: per-minute voice fees, per-segment SMS charges, leased phone numbers, and carrier surcharges. Replacing direct cellular phone calls with a native full-screen emergency call UI over data slashes those costs by 80% to 95%—without compromising wake-up reliability.

The Telephony Tax in Modern On-Call Systems

When you manage an incident response workflow, notifying engineers requires urgent, unmistakable delivery. Historically, teams reached for direct cellular voice calls and SMS through telecom aggregators such as Twilio, Sinch, or Telnyx. While direct PSTN (Public Switched Telephone Network) calling works, the billing model penalizes active engineering teams:

The Bottom Line: If a mid-sized team with 20 engineers generates 500 alert dispatches a month, each firing 2 SMS messages and 1 voice call across escalations, the monthly telephony bill can easily surpass $150 to $300—on top of whatever software subscription or infrastructure hosting fees they already pay.

Why Engineers Relied on Voice Calls (The DND Dilemma)

Given the expense, why not simply notify engineers via standard mobile push notifications, Slack messages, or emails?

Because of the 3:00 AM problem. Standard mobile push notifications arrive as passive banners in the device's notification tray. When engineers sleep, their smartphones are routinely placed in Do Not Disturb (DND), Focus Mode, or silent mode. Modern mobile operating systems are intentionally designed to silence ambient pings, badge counters, and background chat notifications.

Traditional telephone calls were the only reliable mechanism that could break through silence: standard cellular calls trigger full-screen ringing, persistent audio vibration, and repeated wake cycles. Teams accepted exorbitant telecom bills because missed production outages cost infinitely more.

The Modern Alternative: Full-Screen Emergency Incoming Call UI over Data

OnCallAlert solves this dilemma by bringing the wake-up power of a traditional phone call to internet data (VoIP/Push). Instead of dialing out through telecom carriers, OnCallAlert delivers an Emergency Incoming Call UI directly inside the native mobile app (Android & iOS).

Here is how the incoming call screen operates under the hood:

  1. Lightweight High-Priority Wake Signal: When an alert triggers, your self-hosted OnCallAlert instance sends an encrypted wake-up payload containing only an alert ID and device token to the OnCallAlert push relay.
  2. High-Priority Push Delivery: The push relay dispatches the wake event through Firebase Cloud Messaging (FCM) or Apple Push Notification service (APNs) using high-priority emergency priority channels.
  3. Direct, Private Instance Fetch: The mobile app wakes up in the background and queries your self-hosted instance directly over HTTPS to retrieve alert details. Sensitive system health and incident data never pass through third-party telemetry aggregators.
  4. Full-Screen Intent & DND Override: If the user has enabled Bypass Do Not Disturb in their settings, the app invokes Android's high-importance notification channel with fullScreenIntent. This launches the full-screen IncomingCallScreen over the lock screen.
  5. Persistent Ringtone & Haptic Vibration: The device rings out loud with a chosen emergency ringtone and continuous vibration cadence, bypassing silent toggles and system DND restrictions just like an inbound cellular call.
  6. One-Tap Lock-Screen Triage: The responder sees the service name, alert summary, and severity immediately. They can tap to acknowledge the alert or silence the alarm right from the lock screen.

Because this entire notification and triage cycle takes place over the responder's existing cellular data plan or Wi-Fi connection, the carrier cost to your organization is exactly $0.00.

The Hybrid Reliability Architecture: Data Primary, Cellular Fallback

A pure VoIP-only alerting system has an Achilles' heel: mobile data connectivity is not infallible. Responders occasionally drive through subway tunnels, step into cellular dead zones, encounter airplane mode, or exhaust their battery.

To deliver true enterprise-grade incident management, OnCallAlert uses a Hybrid Reliability Architecture:

Tier Channel Delivery Mechanism Telephony Cost
Primary (0 min) Mobile App Full-Screen Call Push Relay → FCM/APNs → Full DND Incoming Call Screen $0.00 (Zero carrier fees)
Automatic Fallback (+3 to 5 min) Direct Cellular Voice (PSTN) Twilio Voice Engine dialing mobile phone number Standard carrier per-minute rate
Secondary Fallback (+5 to 10 min) Direct Cellular SMS & Escalation PSTN SMS dispatch to secondary team member / manager Standard carrier per-segment rate

In this hybrid architecture:

You get the uncompromising reliability of carrier telephony as an automated safety net, but you only pay for phone calls when an engineer is genuinely unreachable over data.

Side-by-Side Economics: Pure Cellular vs. Hybrid DND

Let's compare the cost economics of a traditional telephony-first alerting pipeline against OnCallAlert's hybrid model for a team handling 400 alerts per month across 15 engineers:

Metric / Cost Factor Pure Cellular (Twilio / Legacy On-Call) OnCallAlert Hybrid (DND Call + PSTN Fallback)
Delivery Channel Every alert sends SMS and dials PSTN voice Full-screen DND call over data; PSTN only if unacknowledged
Variable Cost per Alert ~$0.04 to $0.08 per alert (voice call + 2 SMS segments) $0.00 for acknowledged push; ~$0.04 only on 5-10% fallback
Monthly Telephony Usage (400 alerts) ~$16.00 to $32.00 in variable voice/SMS ~$1.20 to $2.50 in variable voice/SMS
Dedicated Numbers & 10DLC Fees Multiple leased DIDs + A2P monthly brand registration Single low-volume fallback DID (or none if push-only)
International Responders Expensive ($0.25–$0.70/min international voice rates) $0.00 anywhere worldwide over data
Wake-Up Effectiveness High (Rings phone out loud) High (Full-screen ringing incoming call over DND)
Data Privacy Incident metadata transmitted across telco carrier logs Encrypted HTTPS directly to your self-hosted database

Configuring the Hybrid Setup in OnCallAlert

Setting up this architecture in your own instance takes less than five minutes:

  1. Connect the Mobile App: In your OnCallAlert web console, navigate to your user profile and select Connect Mobile App. Scan the secure QR code using the companion mobile app (available on Team, Business, and Unlimited plans).
  2. Enable Do Not Disturb Override: In the mobile app settings, toggle Bypass Do Not Disturb to active. This grants the notification permissions necessary to display the full-screen ringing call screen over locked and silenced devices.
  3. Set Notification Rules: On your user profile under Notification Rules, set the Mobile App as your immediate first contact method (0 minutes). Add your Voice Phone Number and SMS as subsequent steps delayed by 3 to 5 minutes.
  4. (Optional) Telecom Kill-Switches: If your team operates fully on data and wishes to completely eliminate external telecom dependencies, administrators can toggle Disable SMS Contact Method or Disable Call Processing in the web admin panel.
Share this post:

Stop overpaying for on-call seats and telephony surcharges. Run your alerting on your own infrastructure with flat licensing and data-first mobile alerting.

PagerDuty cost calculator → Pricing & plans

Sources and technical references