SMS alert case studies: how three teams moved alerts to text
These SMS alert case studies follow three teams whose alert emails reached nobody at night. They are a water district, a credit union IT group and a school district. Today the person on call gets a short text instead. Each story shows the old setup, the new one and what changed, with names and figures left out on purpose.
7-day free trial, 15 message creditsCard required for verificationNo charge for 7 daysEmail reminder before billing
- No team replaced its system
- Every alert still kept in email
- Built on real alert traffic
Works by email with
- Tank & well levels
- Backup & batch jobs
- Cisco Unity
An alert email from jobs@ops.example.org arrives. The Welco rule “Only job errors, any time of day” trims it, and On-call systems admin gets one text: “Welco: [Core] DAYEND for BK014 finished with errors at 11:52 PM. Reply STOP to opt out.”
On-call systems admin received: Welco: [Core] DAYEND for BK014 finished with errors at 11:52 PM. Reply STOP to opt out.
What changed for these three teams
Each team had an alert email that reached nobody after hours. Here is where it lands now.
The water district's night operator
Tank and pump alarms left a slow carrier gateway. The operator on call gets one short text per alarm. Read the water district SCADA case study.
The credit union's on-call admin
Overnight job failures and down servers stopped waiting in a shared mailbox. See the credit union overnight alerts story.
The school district's tech on call
Staff calls to the urgency line arrive as a text with a link to play the message. Read the school district voicemail case study.
The problem each team started with
Three very different systems shared one gap: an alert email existed, but it didn't reach a person in time.
Before Welco
- Alarm texts sent to addresses like
5551234567@vtext.combegan arriving late, or not at all. AT&T ended email-to-text on June 17, 2025 (read October 5, 2026). - Job schedulers and phone systems mailed a shared inbox. During the day someone reads it. At 2 AM, nobody does.
- Urgent voicemail meant dialing in and entering a PIN to hear it.
- Big on-call tools charge for each user, which is hard to justify for a small crew that only needs a text.
After Welco
- The same alert email goes to one Welco address, from a sender each team approved.
- Rules send each kind of alert to the right person at the right hours.
- Voicemail arrives as a text with a private link to play the recording.
- No per-user fees, so adding the night operator or a second tech doesn't raise the bill on its own.
Read the case studies
Each story covers the situation, the old setup, the Welco setup and what changed. They suit plant and water operators, IT teams at banks and credit unions and school and help desk teams.
- Water district SCADAA water district SCADA alarms case study: tank and pump alarms moved off a slow carrier gateway and onto the on-call operator's phone as short texts.
- Credit union IT monitoringA credit union IT monitoring case study: server checks and overnight batch job failures moved from a shared inbox to the on-call admin's phone as texts.
- School district urgency lineA school district urgency line case study: staff voicemail to the tech line now reaches the on-call technician as a text with a link to play the message.
Which case study is closest to your setup?
Find the column that looks most like your own alerts, then read that story first.
What sends the alert
- Water district
- SCADA alarm emails for tanks and pumps
- Credit union IT
- A monitoring tool, a job scheduler and IBM i
- School district
- Cisco Unity Connection voicemail
Where it went before
- Water district
- Carrier gateway addresses like
vtext.com - Credit union IT
- One shared Outlook mailbox
- School district
- A notice in the help desk inbox
What went wrong
- Water district
- Texts arrived hours late, or never
- Credit union IT
- Night alerts were seen only if someone checked
- School district
- Messages waited until the desk opened
Who gets the text now
- Water district
- The operator on call for nights and weekends
- Credit union IT
- The admin on call that week
- School district
- The tech on call and the team lead
What stays in email
- Water district
- Clears and acknowledgements
- Credit union IT
- Routine success notices
- School district
- The original message, kept in Cisco
The rule worth copying
- Water district
- A flood limit for storm nights
- Credit union IT
- Keyword rules that text failures only
- School district
- Texts only outside help desk hours
How each team set up Welco in 3 steps
None of the teams changed their alarm, monitoring or phone system. They changed where its email goes.
Point the alert email at Welco
Each team replaced an old gateway address, or added one more recipient, with their Welco address. They approved the system as a sender so nothing else could text their staff.
Choose who gets which alert
They invited the on-call staff, and each person joined with their own phone and confirmed with YES. Alert rules sent each kind of alert to the right person, at the right hours.
Trim the noise
Long emails were cut to one short text. All-clear messages and routine notices stayed in email.
Your system already emails alerts. Make them texts
The setup in each story starts the same way: one alert email, sent somewhere new.
7-day free trial, 15 message creditsCard required for verificationNo charge for 7 daysEmail reminder before billing
What systems did these teams use?
Each team kept what it ran. Welco only needed the email those systems already sent.
Alerts like the ones in these stories
Masked examples of the alert types each team cared about.
- Water district: storage tank: Welco: [Hilltop Tank] Level HIGH alarm, unacknowledged at 3:26 AM. Reply STOP to opt out.
- Credit union: core banking server: Welco: [core-app-02] Host DOWN, no ping reply at 1:09 AM. Reply STOP to opt out.
- School district: tech urgency line: Welco: Urgent voicemail, Tech line, from ext 5120, 0:41. Listen: welco.ai/v/S8kd3T Reply STOP to opt out.
Questions to answer before you copy a setup
Every team in these stories answered the same few questions first. Write your answers down before you sign up, and setup goes quickly.
0 of 5 done
How we write a Welco case study
Every story here is based on real alert traffic: the kinds of systems, alerts and problems we see. We describe each team in general terms, like a water district in the western US.
We leave out names, places and figures. Nobody has approved a quote or a number for publication, so we don't print one. The results are described in plain words instead.
Every setup step in these stories uses a Welco feature you can turn on today. Nothing in them depends on a custom build or a special arrangement.
Features these teams leaned on
Approved senders
Only the systems they named can text their people.
After-hours routing
Nights and weekends go to the on-call phone.
Alarm flood control
A burst of alarms doesn't become a burst of texts.
Voicemail links
Urgent voicemail plays from a private link in the browser.
Frequently asked questions
Why don't these case studies name the customers?
Why are there no numbers in the results?
Did these teams have to replace their alarm or phone systems?
Can I try a setup like these without texting my staff?
What did these teams keep doing the old way?
How much did these teams pay for Welco?
Is my setup close enough to one of these stories?
Write your own alert story, starting tonight
Point one alert email at Welco and see the first text arrive.
7-day free trial, 15 message creditsCard required for verificationNo charge for 7 daysEmail reminder before billing