Text a number through your own Twilio connection. A chat message is easy to miss and an email is easy to sleep through. SMS is the point where an alert stops being informational and starts being a page.
SMS costs money per message and interrupts a person directly. Both are reasons to put it deliberately rather than everywhere.
Post to a channel immediately and only text after the outage has run for a few minutes. Most brief failures resolve before the text is ever sent.
Use a chat channel for awareness and SMS for the outages nobody has picked up. That keeps the interruption meaningful.
Email the on-call engineer with an Acknowledge button, then text a second person only if nobody claims it.
Because flows belong to individual monitors, a payment API can text while a background job stays in a channel.
Each notify step has a flap cooldown, fifteen minutes by default, which also limits how much a flapping monitor can cost you.
The default, and the right setting for SMS. Firing on every check would text on every failed probe.
Connect Twilio, put an SMS step behind a Wait, and let the real outages find you.