Skip to content
WelcoYour alerts, by text.

Urgent ticket SMS alerts from your help desk

An urgent ticket SMS alert puts the ticket number and title on the on-call tech's phone when an Urgent or High ticket arrives after hours. Routine requests wait in the queue for morning. Your help desk already emails notifications, so one trigger or automation sends the urgent ones to your Welco address.

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

  • One trigger or automation in the help desk
  • No app for techs to install
  • No per-user fees

Works by email with

  • Help-desk tickets

Published:

A help-desk queue of low and normal tickets; a high-priority ticket, “Wi-Fi down in library”, arrives on top. The email reaches Welco and the phone shows: “Welco: Ticket #4821 HIGH, Wi-Fi down in library, opened 7:52 PM. Reply STOP to opt out.”

Animation: a long Help desk alert email is trimmed into one short text: "Welco: Ticket #4821 HIGH, Wi-Fi down in library, opened 7:52 PM. Reply STOP to opt out."

What the after-hours tech gets from the help desk

  • Urgent after hours, on one phone

    A High ticket at 8 PM texts the tech holding the on-call phone. Daytime tickets stay with the people watching the queue.

  • Password resets wait for morning

    Priority decides what reaches a phone. Normal and Low tickets never leave the help desk.

  • Ticket number and title, nothing more

    The text carries enough to judge the problem. Requester names and long descriptions stay inside the ticket.

  • The queue still owns the ticket

    Every ticket lands in the help desk as it does today. Welco only adds a text for the few that qualify.

What you need before you start

Plan on about 20 minutes for a help desk admin, plus a short team talk about what counts as urgent. Urgent tickets then join your other texts for IT on-call teams. Districts that also run an after-hours urgency line can text both to the same tech.

  • A help desk that sends email notifications, such as Spiceworks or incidentIQ.
  • A clear rule for urgent: a priority, a category like network outage, or any ticket after hours.
  • A Welco account and your Welco address. Start free, then verify your business.
  • On-call techs invited to Welco. Each joins with their own mobile and replies YES to start getting texts.

Set up an urgent ticket SMS alert in 5 steps

Help desks name these settings differently. Look for notifications, triggers, rules, automations or workflows.

  1. Write down what counts as urgent

    Agree on it with the team. Priority Urgent or High, a network or safety category, and VIP requesters are common choices. A password reset is not.

  2. Have the help desk email Welco for those tickets

    Add a trigger or automation that sends a notification email to your Welco address when a ticket matches. If your help desk only emails agents, some teams add a notification-only contact instead.

  3. Approve the help desk's sender

    Check the From address on a ticket notice and add it to your Welco sender list to block mail from unknown senders. Then the help desk can trigger texts and nothing else can.

  4. Add a Welco rule as a safety net

    Make one of Welco's matching rules that texts only messages with Priority: High or Urgent. If the help desk ever sends more than it should, routine tickets still stay off the phone.

  5. Open a test ticket

    Create a High ticket titled Test, please ignore, check the text, then close the ticket. Run it as a no-send test in Welco to see the result without a real text.

The urgent ticket reaches a tech, not just the queue

Point urgent ticket notifications at your Welco address. Routine work stays in the help desk.

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

Why routine tickets should stay off the phone

Here is an ordinary ticket notice. Without a filter, it becomes a text like any other. That is why the urgent rule matters.

Alert email from helpdesk@district.example.org, subject “New ticket: password change”. Welco trims it to one text of 90 characters: “Welco: Ticket #4790 Normal, password change, Front office, 9:14 AM. Reply STOP to opt out.”

Text received: Welco: Ticket #4790 Normal, password change, Front office, 9:14 AM. Reply STOP to opt out.

Characters253901 credit

Animation: the alert email "New ticket: password change" is trimmed into one text: "Welco: Ticket #4790 Normal, password change, Front office, 9:14 AM. Reply STOP to opt out."

A rule that drops Priority: Normal keeps this one in the queue. To cut alerts to one lock screen, also drop the description and link from the urgent ones.

Keep ticket texts rare enough to trust

Techs stop reading texts that cry wolf. These habits keep each one worth opening.

  • Text after hours, email by day

    Night and weekend routing texts urgent tickets only in the evening and on weekends, to whoever holds the after-hours queue.

  • New tickets only, not every update

    Triggers on ticket updated, new comment or resolved fire all day. Point only the new-urgent-ticket trigger at Welco.

  • SLA reminders stay in email

    Some help desks re-send a warning as a ticket nears its due time. Keep those reminders off the Welco address.

  • One outage, forty tickets

    When the Wi-Fi drops, half the building opens a ticket. Flood limits per phone stop the tech's phone from buzzing for each one.

  • Keep names out of the text

    Trim the requester's name and the description. The tech opens the help desk for the rest.

When an urgent ticket doesn't text

Check these in order, from the help desk to the phone.

No email in the help desk's notification log

Where to look
The trigger's conditions didn't match that ticket's priority or category.

Welco dropped the message

Where to look
The subject and body lacked the words your Welco rule looks for.

Welco refused the message

Where to look
The help desk's From address isn't approved yet.

The feed shows a text, but a phone stayed silent

Where to look
Welco shows which phones got it and why a text didn't arrive.

Frequently asked questions

Which help desk tickets should send a text?

Only the ones where waiting causes harm. Network outages, a server down, a whole building offline and anything urgent after hours are common picks. Password resets, new accounts and printer jams belong in the queue. If techs get more than a few texts a week, tighten the trigger.

Do techs need an app or a help desk login on their phone?

No. The urgent ticket arrives as a normal text message on any mobile. Techs only open the help desk when they decide to work the ticket.

Can I reply to the text to update the ticket?

Not reliably. A reply goes back by email to the alert's last sender, here the help desk's notification address. If that address turns email into ticket comments, it may land there. Many help desks send from a no-reply address, so update the ticket in the help desk itself.

Our help desk only emails agents. How do I add Welco?

Look for a trigger, automation or workflow that can email any address. Most help desks have one. If yours doesn't, some teams add a contact or agent record with the Welco address. Check whether that uses a paid seat first.

Can urgent tickets go to a different tech each week?

Yes. Keep the help desk sending to one Welco address. In Welco, change whose phone the after-hours routing uses, and the next urgent ticket texts that person. Nothing changes in the help desk when the week turns over.

What do ticket texts cost?

There are no per-user fees, so adding a fifth tech costs nothing extra. Each short ticket text uses one message credit. Raise a test Urgent ticket during the 7-day free trial with 15 credits. Your card is verified but not charged until you approve a plan from the pricing page, and there are no overage fees.

Let the next urgent ticket find the tech on call

One trigger to your Welco address. The queue keeps the rest.

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