19 August 202611 min read

On-Call Escalation via SMS from Microsoft Teams

Learn how to build an on-call escalation workflow that turns critical Microsoft Teams alerts into SMS text messages, so the right responder is notified even after hours.

Introduction

When a critical system goes down at 2am, a Microsoft Teams message sitting unread in a channel does nothing for the on-call engineer who is asleep. Teams is excellent for daytime collaboration, but notifications inside the app rely on someone actively watching a screen. For after-hours incidents, that assumption breaks down and response times suffer.

This post covers how to build an on-call escalation workflow that pushes critical Teams alerts out as SMS text messages, ensuring the right person is notified no matter what device they're near. You'll learn what on-call SMS escalation actually means, why it matters for Australian teams running production systems, and how to set it up using Microsoft Teams, Power Automate, and the DataFlows SMS API.

What Is On-Call SMS Escalation

On-call SMS escalation is the practice of automatically converting critical alerts raised in a monitoring or collaboration tool into SMS text messages sent to the on-call responder's mobile phone. Rather than relying on a person to be logged into Teams or Slack-style apps, the alert reaches them through a channel almost everyone checks constantly: text messages. If the first responder doesn't acknowledge the alert within a set time window, the workflow escalates by texting a secondary contact, and then a manager if needed. This tiered structure is what makes it an "escalation" rather than a single notification. For teams running infrastructure, customer-facing applications, or physical equipment that needs monitoring, SMS escalation closes the gap between an alert firing and a human actually seeing it, especially outside business hours when app notifications are easy to miss or silence.

Why It Matters for Australian Businesses

Australian businesses increasingly run distributed teams and cloud infrastructure that needs attention outside standard hours. A retailer's checkout system, a healthcare provider's booking platform, or a logistics company's tracking service can fail at any time, and customers notice quickly when it does.

Email and in-app notifications are easy to miss overnight. Push notifications get muted. SMS, by contrast, has a very high open rate and typically reaches a phone even when data connectivity is patchy, since SMS runs on the mobile network rather than relying on wifi or app connectivity. For teams already using Microsoft Teams for daily operations, adding an SMS layer for critical alerts means no new chat tool to learn — just a more reliable path for the alerts that genuinely can't wait.

There's also a cost angle. A missed alert that turns into an extended outage is expensive, both in direct revenue terms and in customer trust. A text message that gets a response in minutes instead of hours is a small operational cost against a much larger risk.

Time zones and remote work add another layer. Many Australian companies now run support functions across multiple states, or rely on staff who work irregular hours. A person's laptop might be closed, but their phone is rarely far away. Building the escalation path around SMS instead of assuming someone is watching a screen matches how people actually work today.

Common Use Cases

SMS escalation from Teams isn't limited to software outages. A few common examples:

Infrastructure and DevOps teams use it to alert engineers when a server, database, or API endpoint stops responding, escalating from the on-call developer to a team lead if the issue isn't acknowledged.

Facilities and operations teams use it when a monitored system — a cold storage unit, a security sensor, or a piece of factory equipment — reports an alarm condition outside working hours.

Customer support teams use it to page a duty manager when a high-priority ticket sits unassigned past a service level target.

Healthcare and aged care providers use it to alert an on-call clinician when a monitoring system flags a condition needing prompt attention.

IT managed service providers use it to escalate client incidents through a defined chain, so a missed alert doesn't become a missed SLA.

In each case, the pattern is the same: an event happens inside Teams, and if the right person doesn't respond quickly enough, SMS carries the alert further until someone does.

Key Benefits

Faster response times — SMS reaches a phone even when the recipient isn't near a laptop or hasn't opened Teams, cutting the time between an incident firing and a human acknowledging it.

Built-in escalation logic — if the primary on-call contact doesn't respond, the workflow can automatically text the next person on the roster, so nothing sits unanswered.

No new app to install — responders don't need a dedicated on-call app; the alert lands as a normal text message on any phone.

Works without data or wifi — SMS delivery only needs mobile network coverage, which makes it more dependable than push notifications during connectivity issues.

Clear audit trail — each SMS sent, delivered, and acknowledged can be logged, giving teams a record of how an incident was handled.

Two-way acknowledgement — responders can reply to the SMS to confirm they're on it, and that reply can be routed back into Teams automatically.

Step-by-Step Guide: Building the Workflow

This setup uses Microsoft Teams as the trigger source, Microsoft Power Automate as the orchestration layer, and the DataFlows SMS API to deliver and track the messages.

1. Get your DataFlows API Token.

Sign up at dataflows.com.au and open the Developer section of your dashboard. Generate an API Token — this is what Power Automate and Teams will use to authenticate outbound SMS requests.

2. Set up your on-call contact list.

In DataFlows, create a Contact List for your on-call roster, including primary and secondary responders with their mobile numbers. Keeping this list current is what makes the escalation logic reliable.

3. Connect Microsoft Teams as the trigger.

Use the DataFlows Microsoft Teams integration to watch for messages posted to a designated "Incidents" channel, or trigger from an adaptive card action when a monitoring bot posts an alert. This is the event that kicks off the escalation.

4. Build the escalation flow in Power Automate.

With the DataFlows Power Automate connector, create a flow that:

Sends an SMS to the primary on-call contact when a new incident message appears in Teams.

Waits a defined period (for example, 5 minutes) for an acknowledgement.

If no reply is received, sends a follow-up SMS to the secondary contact, and posts a status update back to the Teams channel.

Continues escalating up the chain until someone acknowledges the alert.

5. Handle acknowledgements.

When a responder replies to the SMS (for example, texting "ACK"), DataFlows' inbound SMS webhook can trigger a Power Automate action that posts a confirmation back into the Teams channel, so the whole team sees who picked up the incident.

6. Test the full loop.

Trigger a test incident outside business hours to confirm messages arrive, escalation timing works as expected, and acknowledgements flow back into Teams correctly before relying on it for real incidents.

How DataFlows Helps

DataFlows provides the SMS API and Microsoft Teams integration that this whole workflow depends on. Messages sent through the API include delivery status tracking, so you can confirm an alert actually reached the recipient's phone rather than assuming it did.

The two-way SMS capability means responders aren't just receiving alerts — they can reply directly, and those replies can be routed back into Teams through Power Automate, keeping the whole incident thread visible to the team without anyone needing to switch apps mid-crisis.

For teams that want a branded sender rather than a generic long number, DataFlows Sender IDs let escalation texts arrive clearly identified, which helps responders recognise a real alert at a glance. And because the Contact Lists feature keeps your on-call roster centralised, updating who's on call this week is a matter of editing one list rather than reconfiguring a flow.

If your team also wants a self-service option, DataFlows SMS Automation can trigger the same escalation logic directly from rules set up in the dashboard, without needing a Power Automate flow for simpler cases. This is useful for smaller teams that want on-call SMS alerts running quickly, and can move to the full Teams and Power Automate setup as their process matures.

Best Practices

Keep escalation windows short but reasonable. Five to ten minutes gives a responder time to see and act on an alert without letting a real incident sit too long.

Test the flow regularly, not just once. On-call rosters change, and a flow that worked when it was built can quietly break when a contact's number or role changes.

Use clear, specific message content. An SMS that says "Server down — check Teams incidents channel" is more actionable than a generic "Alert triggered" text.

Require an explicit acknowledgement. A one-word reply like "ACK" is faster for a half-asleep responder to send than opening an app and clicking a button.

Log every escalation. Keeping a record of who was alerted, when, and whether they acknowledged helps with post-incident reviews and roster planning.

Avoid over-alerting. Reserve SMS escalation for genuinely critical incidents — if every minor warning triggers a text, responders will start ignoring them.

Conclusion

Microsoft Teams is where your team already collaborates, but it shouldn't be the only place a critical alert lives. Pairing Teams with DataFlows SMS and Power Automate gives you an escalation path that reaches the right person even when they're away from their desk, asleep, or offline from the app. Sign up at dataflows.com.au to get your API Token and start building an on-call escalation workflow that actually wakes people up when it matters.