SMS
The delivery channel for the alert that can’t wait for an app to open.
How SMS fits into Aanty
SMS is one of Aanty’s external delivery channels for notifications — critical alerts, approval requests, guardian notices — following the same per-user, per-event-type preference model (with quiet hours) that governs every delivery channel, and replacing bespoke SMS senders like trainty’s deferred guardian-alert plans.
Critical-path delivery
Reserved for the alerts and approvals that genuinely need a channel outside the app — not a firehose.
Quiet-hours aware
Respects the same per-user, per-event-type preferences and quiet hours as every other delivery channel.
Sibling pattern, generalized
Replaces bespoke per-platform SMS senders (trainty’s guardian alerts) with one governed delivery path.
Outbound integration
Aanty publishes registry-named events (aanty.<domain>.<action>) and delivers to SMS so actions taken in the product — replies, approvals, mentions — reach the people and systems that need them, governed by the same per-recipient preferences as every delivery channel.
See it alongside
Other integrations and pages that pair naturally with this one.
See SMS inside a real Aanty workspace
Bring the SMS events your team already generates. In fifteen minutes we'll show you what they look like as a conversation, not a notification.