Send verification codes straight to your team's tools
When a new SMS verification code arrives, JoltSMS can notify your team in Slack, Discord, Email, or a custom Webhook. Combine that with the shared inbox so nobody has to ask, "Did anyone see the code?".
- Connect Slack, Discord, Email, or your own Webhook
- Configure notification rules per number
- HMAC-SHA256 signed Webhooks for your application
Stop waiting on whoever has the dashboard open
Even with a shared inbox, you don't want people refreshing a page to see new codes. Notifications push new SMS verification messages to the channels your team already watches.
- New codes show up where your team works all day
- Reduce Slack/DM noise asking "What's the code?"
- Keep the inbox as the single source of truth
Send codes to Slack and Discord in real time
Post new SMS messages into your Slack or Discord channels so on-call teammates see codes immediately.
- Add one or more Slack endpoints pointing to any channel
- Add Discord Webhooks for ops, security, or dev channels
- Each endpoint can be reused across multiple numbers
- Message payload includes number label, sender, and message text
Email notifications for simple, reliable alerts
Not everyone lives in Slack or Discord. Email notifications ensure key people still see new messages even if they never log into the dashboard.
- Add one or more Email addresses as destinations
- Use Email notifications for managers or finance/legal stakeholders
- Good for teams that prefer simple, auditable communication
- Can be used alongside Slack/Discord/Webhooks
Webhooks with HMAC-SHA256 signatures for your app
When you need your own systems to react automatically, connect a custom Webhook. JoltSMS sends a JSON payload to your endpoint and signs it with HMAC-SHA256 using a secret you configure.
- Your endpoint receives HTTP POST requests with JSON payloads
- Each Webhook uses a signing secret you provide
- Signatures are generated with HMAC-SHA256
- Verify the signature in your app before trusting the payload
Example Payload Fields
| number_id | ID of the JoltSMS number that received the SMS |
| from | Sender of the SMS (e.g., short code) |
| body | Full text of the SMS message |
| received_at | Timestamp the message was received |
Control notifications per number
Some numbers are critical. Others are experimental. Notification rules let you decide which endpoints should receive messages for which numbers.
- Turn notifications on or off per number
- Choose which endpoints get messages for each number
- Use different channels for high-signal vs low-signal numbers
- Change rules without changing the underlying number
How notifications work with your inbox
Connect endpoints
Add Slack/Discord Webhooks, Email addresses, and/or custom Webhooks in your JoltSMS account.
Choose rules per number
Decide which endpoints get notified when a specific number receives new messages.
Receive and act on codes
New SMS verification messages appear in the inbox and are pushed to your chosen endpoints in seconds.
The inbox remains your system of record. Notifications are how you make sure the right people see new codes quickly.
Notifications FAQ
JoltSMS supports notifications to Slack, Discord, Email, and custom Webhooks. You can configure one or more endpoints of each type and assign them to numbers.
Never miss another verification code
Send SMS verification codes from your dedicated non-VoIP numbers straight to Slack, Discord, Email, or your own app—while keeping everything logged in the shared inbox.