Operations | Monitoring | ITSM | DevOps | Cloud

When your team shares one support number, someone has to decide who gets the calls when customers need help after hours. And if your team rotates on-call responsibilities weekly, which is common in IT (SRE, DevOps, ITOps, etc), clinical and field engineering teams, you’ve probably relied on manual call forwarding at some point. On paper, it seems straightforward: update the forwarding number each week to point to the person who’s on call. In practice? It often turns into a scramble.

When AT&T officially shut down its email-to-text and text-to-email service on June 17, 2025, a quiet but essential part of many organizations’ communication workflows disappeared overnight. Messages that used to be sent to addresses like simply stopped delivering. For teams who relied on those alerts to reach the on-call clinician, engineer, technician, or service lead — this created an unexpected and urgent gap. This wasn’t just a convenience feature going away.

Secure and seamless communication is at the heart of effective patient care. Whether coordinating handoffs, requesting consults, activating code teams, or managing after-hours coverage, clinicians rely on messaging systems that are reliable, fast, and built to protect patient data.