Skip to content
WelcoYour alerts, by text.

Credit union IT alerts by SMS, from the tools you already run

When DAYEND ends in errors or a branch circuit drops overnight, your on-call admin should know by text, long before the first teller signs on. Welco reads the alert emails that Nagios, PRTG, your job scheduler or your IBM i already send. It texts a short version, and nothing installs on your servers or your core.

Text me my server alertsBook a demo

7-day free trial, 15 message creditsCard required for verificationNo charge for 7 daysEmail reminder before billing

  • One email recipient added per tool
  • No agent on servers or the core
  • No per-user fees

Works by email with

  • Nagios
  • PRTG
  • Backup & batch jobs

Setup guide for

  • SolarWinds

A network map watched by Network monitor: five hosts answer pings until Branch 6 goes down (No ping 5 min) and the monitor raises the alert. The email reaches Welco and the phone shows: “Welco: [Branch 6] Firewall DOWN, no ping for 5 min at 5:47 AM. Reply STOP to opt out.”

Animation: alerts arrive through the night and each goes to the right person. 11:14 PM, to On-call systems admin: "Welco: DAYEND for BK014 completed with ERRORS at 11:14 PM. Reply STOP to opt out." 2:31 AM, to Night operator: "Welco: [GoAnywhere] File transfer FAILED, job ACH-OUT at 2:31 AM. Reply STOP to opt out." 5:47 AM, to Network admin on call: "Welco: [Branch 6] Firewall DOWN, no ping for 5 min at 5:47 AM. Reply STOP to opt out."

What a two or three person IT team gets

Your on-call admin gets failed jobs, file transfers and branch outages by SMS, overnight. The alerts come from tools that already email them, and nothing installs on the core.

  • The failed batch finds you first

    A failures-only rule texts the DAYEND error and leaves the success notices in email. Posting gets rerun while the branches are still dark.

  • Member data stays off phones

    Texts carry the job, the host and the time. Keep names and account numbers out of the alert email, and one-text trimming drops the rest.

  • The whole team, no seat math

    Everyone on the call list joins with no per-user fees. Nights go to whoever holds the phone this week through on-call routing.

  • A record for the examiner

    Delivery reports list every text, when it left and whether it reached the phone. The credit union IT case study shows one team's setup.

A DAYEND that ends in errors on a Tuesday night

Two admins split the on-call week at a small credit union. This is how one bad posting run plays out.

  1. The branches close and the night rule starts

    During the day, job alerts reach the whole IT team. After 6 PM they go only to the admin holding the on-call phone.

  2. The IBM i emails a DAYEND error

    JOB DAYEND (BK014) ENDED WITH ERRORS, SEE QSYSOPR. SYSTEM PROD1

  3. The on-call admin's phone lights up

    Welco: [PROD1] DAYEND BK014 ended with errors, posting stopped at 11:14 PM. Reply STOP to opt out.

  4. The admin answers from the couch

    Signing in now, will restart DAYEND from step 4

  5. The reply lands in the operations mailbox

    A text reply is emailed to whatever address sent the alert. Send job alerts from a mailbox the IT manager reads, and nobody needs a phone call.

    Reply from the on-call phone: Signing in now, will restart DAYEND from step 4

  6. The branches open on schedule

    Posting finished after midnight. The reply thread and the delivery report tell the morning huddle what happened overnight.

Times are an example, and mobile networks set the pace of each text. A reply to Welco leaves the job and the message queue on the IBM i untouched.

How to set up IT alert texts at a credit union

One admin can do this between tickets. Each monitoring or job tool changes by one email recipient.

  1. Sign up and verify your credit union

    Tell us who you are and which alerts you plan to send. We check every business first, so your number carries alerts and nothing else.

  2. Invite the admins on the call list

    Each admin opens their own invite, types their mobile and replies YES once. Nobody can be signed up by somebody else.

  3. Add Welco next to today's recipients

    Put your Welco address in Nagios, PRTG or the job scheduler, approve the sender, then fail a test job. Test mode previews each text without sending it.

Get the next failed DAYEND as a text

Verify your institution and add one alert address to your job scheduler.

7-day free trial, 15 message creditsCard required for verificationNo charge for 7 daysEmail reminder before billing

Text me my server alertsBook a demo

Which monitoring tools can send credit union IT alerts by SMS?

Each tile opens a setup guide in that tool's own menus, like Nagios text alerts or PRTG SMS notifications. OpCon, GoAnywhere and SQL Server jobs use backup and batch job alerts. Alerts that only reach you in Outlook use Microsoft 365 forwarding.

Alerts credit union admins act on overnight

These are masked examples with no member data in them. Zabbix SMS alerts, SolarWinds SMS alerts and APC UPS alerts read much the same. Managed service providers and school district IT teams carry similar nights, as how other industries use Welco shows.

  • Branch WAN: Welco: [Branch 3] edge-rtr-03 DOWN, primary circuit lost at 6:04 AM. Reply STOP to opt out.
  • File transfer: Welco: [GoAnywhere] ACH-IN pickup FAILED, file not found at 3:10 AM. Reply STOP to opt out.
  • Core host: Welco: [PROD1] System ASP at 92%, CRITICAL threshold at 1:45 AM. Reply STOP to opt out.

A phone showing these alert texts: Branch WAN, "Welco: [Branch 3] edge-rtr-03 DOWN, primary circuit lost at 6:04 AM. Reply STOP to opt out."; File transfer, "Welco: [GoAnywhere] ACH-IN pickup FAILED, file not found at 3:10 AM. Reply STOP to opt out."; Core host, "Welco: [PROD1] System ASP at 92%, CRITICAL threshold at 1:45 AM. Reply STOP to opt out."

Which credit union IT alerts are worth a text at night?

Text the failures that stop posting, block a file transfer or keep a branch offline at opening. Success notices, warnings and recoveries can stay in email.

Text these at any hour

  • DAYEND or end-of-day posting that ends in errors.
  • An ACH or core file transfer that fails or finds no file.
  • A branch router or firewall down for more than one check.
  • Core host disk or ASP past its critical threshold.
  • The server room UPS running on battery.

Leave these in the mailbox

Job success notices, OK and RECOVERY messages, and disk warnings below critical. Patch and backup summaries that passed belong there too.

Keep member data out of every alert

A text is built from the alert email, so read each email before you approve its sender. Alerts should name systems and jobs, never members. The guide to writing short alerts shows what to cut.

An IBM i job failure, from email to text

IBM i alerts often arrive as plain mail from the system operator queue. Welco keeps the system, the job and the time.

Alert email from qsysopr@ibmi.example.org, subject “JOB NIGHTPOST FAILED”. Welco trims it to one text of 93 characters: “Welco: [PROD1] Job NIGHTPOST batch file did NOT complete at 1:12 AM. Reply STOP to opt out.”

Text received: Welco: [PROD1] Job NIGHTPOST batch file did NOT complete at 1:12 AM. Reply STOP to opt out.

Characters170931 credit

Animation: the alert email "JOB NIGHTPOST FAILED" is trimmed into one text: "Welco: [PROD1] Job NIGHTPOST batch file did NOT complete at 1:12 AM. Reply STOP to opt out."

Your scheduler might send the same alert from two places. Approve each sender address you want to text from.

Overnight IT alerts at a credit union, then and now

The old way

  • The DAYEND error waits in the QSYSOPR queue until someone signs on at 7.
  • Alert texts sent through a carrier email-to-text address that quietly stopped delivering.
  • Every OK and RECOVERY notice buzzes the phone along with the failures.
  • A paging tool priced per seat, for an IT team of three.

With Welco

  • The job, the system and the time on the lock screen.
  • One verified alerts-only number that carries nothing else.
  • Failures text, and recoveries wait in email for the morning.
  • The whole call list on one plan, with no per-user fees.

Frequently asked questions

Do we install anything on the IBM i, the core or our Windows servers?

No. Your scheduler, monitor or IBM i already sends email, and that is all Welco reads. Add your Welco address as one more recipient and approve the sending address. The alert emails your team gets today keep arriving exactly as before.

Should member information ever appear in an alert text?

No. Alert texts are about systems, so send the job name, host or branch and leave out member names and account numbers. Only approved senders can trigger a text, so a stranger's email can't reach your admins. The security page covers how alert data is handled.

Do our admins need an app, and can they answer an alert?

No app is needed, because each alert is a normal text. Each admin confirms their own mobile with YES once and can reply STOP whenever they like. A reply goes back by email to the alert's sender, as the reply by email page explains.

The core host went down and fifty checks failed with it. What reaches the phone?

A handful of texts, not fifty. Flood control caps a burst, and each phone gets one copy of a resent email. Two separate forwards from Exchange still look like two alerts, so remove the extra rule. Alerts past the cap are not texted, so open the console after the first one.

Can we show auditors which alerts went out and which ones failed?

Yes. Each text has a delivery report with the time it went out and whether it reached the phone. When a text fails, the report says why in plain words, such as a landline number. Pull it up for an examiner or the board whenever they ask.

What does it cost, and how does it compare to PagerDuty?

You pay no per-user fee or setup fee, and the 7-day trial with 15 credits never charges the card that verifies you. Your plan covers the message credits your alerts use, as plans and pricing shows. PagerDuty adds schedules and escalation, priced per user (PagerDuty pricing, October 2026). Teams that only want texts often find Welco is enough.

Hear about tonight's failed job before the branches open

Point one tool's alert email at Welco and add the on-call phone.

Text me my server alertsBook a demo

7-day free trial, 15 message creditsCard required for verificationNo charge for 7 daysEmail reminder before billing