Guide
SMS outage alerts for Canadian businesses (and why the sending number matters)
Three things decide whether an outage text actually reaches a Canadian phone: consent, a working STOP, and where the message is sent from.
Published
If you want a text when your website goes down, the hard part is not writing the message — it is consent, opt-out, and the sending number. Canada's anti-spam law (CASL) governs the first two, and carrier filtering quietly decides the third. Get any of them wrong and the failure is usually invisible: no error, no bounce, just a text that never arrives.
1. CASL: consent is not a checkbox you assume
CASL applies to commercial electronic messages sent to Canadian recipients, and text messages count. For operational alerts — “your website is down” — the practical rule is simple: the person must have actually agreed to receive texts at that number, and you should be able to show when and how they agreed.
That is why serious alerting tools make you verify a number with a one-time code before anything else is sent to it. Verification does two jobs at once: it proves the person controls the phone, and it creates the consent record. A number typed into a form and never confirmed is not consent — it might be a typo, or somebody else's phone.
One nuance worth knowing: consent to operational messages is not consent to marketing. If a vendor collects a number for outage alerts and later texts you a promotion, that is a different purpose requiring different permission.
2. STOP has to work instantly — and it is broader than people expect
Replying STOP must end the messages immediately, with no settings page to hunt for and no grace period. Most platforms handle STOP at the carrier or platform layer so it works even if the application is broken — which is the right design, because an opt-out that depends on an app being healthy is not really an opt-out.
The part that surprises people: opt-out is usually recorded against the number, for the whole sender — not per-website or per-alert-type. If you monitor five sites and reply STOP to one outage text, you have typically unsubscribed that phone from all of them. That is correct behaviour from the recipient's point of view — they said stop texting me, not stop texting me about one thing — but it means a shared on-call number should be treated carefully.
HELP matters too. Carrier guidelines expect a reply identifying the program and how to get support. It is easy to overlook because nobody tests it.
3. The sending number decides whether the text arrives at all
This is the part that catches people out. Sending a text from one country to another — for example a Canadian number texting a US mobile, or the reverse — is not simply a matter of dialling. Carriers filter application-to-person (A2P) traffic aggressively based on the sender's registration and reputation, and unregistered cross-border traffic is frequently blocked.
The dangerous part is the silence. A blocked message often does not produce an error you can see. The platform reports it as accepted, the carrier discards it, and if nobody is checking delivery receipts, the sender believes it went out. For a marketing blast that is annoying. For an outage alert it means you think you will be told when your website breaks, and you will not be.
The practical takeaway for a Canadian business: alerts sent to Canadian mobiles from a Canadian number, on a route registered for that traffic, are the reliable case. Anything crossing a border should be treated as unproven until you have watched a real message arrive on a real handset.
4. A short checklist before you trust a text alert
- Did you verify the number with a code? If a tool texts a number you simply typed in, there is no consent record and no proof of control.
- Does STOP work? Test it. Then check you can resubscribe.
- Does HELP reply? Most people never try it; carriers expect it to work.
- Where is the text sent from? Ask what number and which country. If your phone is in a different country from the sender, ask whether that route is registered.
- Have you seen one arrive? Not a dashboard saying “sent” — an actual message on the actual phone that will need to receive it at 2am.
How PingStuff handles this
PingStuff is operated from Waterloo, Ontario, and sends alert texts from a Canadian number to Canadian mobile numbers. Numbers outside Canada are not supported yet — United States carrier registration is a separate process we have not completed — so accounts with non-Canadian mobiles receive every alert by email instead. We would rather say that plainly than let a text quietly not arrive.
Every number is verified with a one-time code before it receives anything, consent is recorded with its source and timestamp, replying STOP unsubscribes that number from all PingStuff texts immediately and confirms it, replying HELP returns a message naming the service and how to reach us, and marketing texts do not exist in the product at all. Those are the checklist items above, applied to ourselves. You can read the specifics in our SMS Terms.
This guide is general information about how SMS alerting works, not legal advice. If CASL compliance matters to your business, talk to a lawyer about your specific situation.
See whether your site is healthy right now
Run a free instant health check — no signup. If you want to be told when something breaks, SMS alerts reach verified Canadian mobiles, and email alerts work everywhere.
Check a website free