Grafana Alerting supports contact points for chat apps, email, incident platforms, webhooks, and push notifications. However, there is no native SMS contact point. When a critical alert needs to reach a phone, teams must add another layer, such as an incident platform, SMS API, or email-to-SMS gateway. Here are the common gaps teams face when Grafana send alerts:
Grafana supports 20+ contact points, including Slack, Teams, Discord, Google Chat, Telegram, email, PagerDuty, Opsgenie, webhooks, and Amazon SNS. However, none sends a direct SMS message. Teams need an additional service, custom webhook, or email gateway to bridge Grafana cloud alerts to a phone number.
Email is the simplest Grafana contact point, but it depends on someone checking their inbox. Push notifications can also be silenced after hours. Older carrier email-to-text workarounds are no longer reliable, with AT&T shutting down its gateway in June 2025. Teams still using it need an AT&T email-to-text alternative.
Grafana OnCall OSS was archived on March 24, 2026, and the Cloud Connection that supported SMS, phone, and push notifications ended at the same time. Self-managed teams now need to choose between Grafana Cloud IRM, building their own SMS workflow, or routing alerts through an email-to-SMS gateway.
Grafana IRM provides incident workflows and SMS capabilities for teams with formal incident management processes. For teams that only need direct SMS alerts, its broader features may add unnecessary complexity and licensing costs.
A webhook connected to Twilio, Vonage, AWS SNS, or a custom service gives teams complete control over SMS delivery. However, it also requires maintaining application code, API credentials, messaging accounts, sender numbers, 10DLC registration, and billing across multiple vendors.
Grafana notification templates allow teams to customize email content, but SMS formatting depends on the delivery method. Incident platforms may add their own message structure, while an email-to-SMS gateway can send the alert content defined in Grafana templates directly to the phone.
TextBolt adds SMS delivery to Grafana through the existing email contact point. Add your TextBolt gateway address, attach it to a notification policy, and Grafana alert emails become text messages. Your alert rules, label matchers, grouping, and notification templates stay unchanged.
When Grafana releases an alert through a notification policy, the email reaches TextBolt and is converted into an SMS within seconds. Grafana’s own grouping rules, group wait time, and group intervals remain fully under your control.
Grafana’s email contact point already works with every alerting workflow. Add TextBolt as another email destination, attach it to your notification policy, and send alerts to email, Slack, and SMS from the same rule.
TextBolt registers your sender with The Campaign Registry during onboarding, so alerts use carrier-approved 10DLC compliance infrastructure instead of personal numbers or consumer carrier gateways. Delivery rates reach up to 98%. Registration approval takes up to 48 hours before messages can be sent.
TextBolt sends the alert email generated by Grafana. Since default Grafana emails can be long, use notification templates to include only key details like alert name, instance, and value. Keeping messages under 155 characters helps limit SMS credits. Disable resolved messages if you only want failure alerts.
When an engineer replies to an alert, the response returns as an email to the mailbox connected to Grafana’s SMTP sender. Teams can acknowledge incidents or continue the conversation through email. A STOP reply unsubscribes that number from future alerts.
TextBolt requires no webhook, Twilio account, custom code, or incident platform license. If Grafana can send an email contact point, it can send SMS alerts through TextBolt. Grafana Cloud supports SMTP by default, while self-hosted installations only need SMTP configured once in grafana.ini.
Up to 98%
SMS Delivery Rate
Two-Way
SMS Replies to Your Inbox
Carrier-Grade
Routes & Infrastructure
Up to 10
Team Members on Shared Account
Hands-on setup takes about 30 minutes: create your account, choose a business number, and add one email contact point in Grafana. TextBolt handles 10DLC registration in parallel. Carrier approval can take up to 48 hours, and messages start sending once approval is complete. Self-hosted Grafana instances need SMTP configured first, while Grafana Cloud includes SMTP support.
Sign up using your team’s email address. Account creation takes about two minutes and works regardless of where your Grafana instance is hosted.
Select the dedicated toll-free business number that will send your Grafana alert texts. Engineers can save it as a contact so critical alerts are recognizable during after-hours incidents.
Provide your business details during onboarding. TextBolt submits your brand and campaign registration to The Campaign Registry on your behalf. Approval can take up to 48 hours, while the remaining setup steps can be completed during the review process.
Go to Alerting → Contact points → Add contact point and select Email as the integration type. Add your TextBolt gateway address (+1[phone]@sendemailtotext.com) as the recipient. Under optional email settings, keep Single email enabled. If you only want alerts when an issue starts, enable Disable Resolved Message under notification settings.
Go to Alerting → Notification policies and create a policy for alerts that need SMS delivery. Use label matchers such as severity=critical or team=infra, then assign your TextBolt contact point. Adjust group wait and group interval settings based on how quickly you want alerts delivered.
Use Grafana’s Test button to send a sample alert. Confirm the message arrives and review delivery details in TextBolt’s SMS history. Then invite up to 10 engineers to the shared account. Each phone number can have its own gateway contact point, while the team continues using the same business number.

Get Grafana Email Alerts on Your Phone
Stop relying on inbox checks and muted chat notifications for critical Grafana alerts. Connect your existing email contact point to TextBolt and start sending pipeline and monitoring alerts as SMS from your registered business number.

Use Grafana’s existing email alert path with the TextBolt gateway as the recipient. Add one contact point using +1[phone]@sendemailtotext.com and attach it to the root or a child notification policy. Every matching alert is converted into a text message. Best for individual on-call engineers or simple escalation paths.

Create separate gateway contact points for different teams or rotation members. Use notification policy label matchers to send infrastructure alerts to the infrastructure team, application alerts to developers, and security alerts to the security team. Each phone receives only the alerts it needs, while mute timings control when notifications are active.

Replace an existing Grafana OnCall or webhook-based SMS workflow with an email contact point connected to TextBolt. Your alert rules and notification policies stay the same, while custom Lambda functions, API code, and SMS vendor management are removed.
Six common Grafana monitoring categories where SMS to on-call engineers replaces a Twilio webhook handler, a per-seat IRM platform, or an unread email alert. Each links a Grafana alert rule to an on-call phone in seconds.
CPU saturation, memory pressure, disk-full thresholds, and host-down alerts from Node Exporter or your server monitoring stack. SMS the on-call SysAdmin or NOC operator the moment a host crosses a critical threshold.
Request latency spikes, error rate breaches, p99 regressions, and traffic anomalies from your APM data source. SMS application engineers and SREs before user-visible degradation compounds into a full incident.
Packet loss thresholds, bandwidth saturation, link-down events, and latency spikes from SNMP exporter or ping checks. Network engineers get SMS the moment a circuit, interface, or upstream provider degrades.
AWS CloudWatch, Azure Monitor, and GCP Monitoring data sources surfaced in Grafana send SMS for cloud-side incidents: instance failures, autoscaling events, billing anomalies, and managed-service disruptions.
Slow query thresholds, replication lag, connection-pool exhaustion, and storage growth from PostgreSQL, MySQL, or MongoDB exporters. Database administrators get SMS the moment a query backlog or replica falls behind.
Revenue dips, signup drops, payment-failure spikes, and SLI breaches surfaced in custom Grafana dashboards. Business and product on-call rotations get SMS for the metrics that matter to engineering leadership.

10DLC Compliant
Carrier Approved
Complete Audit Trail
Choose the approach based on how much alerting infrastructure you need. Incident platforms handle complete on-call workflows, webhooks provide maximum customization, and TextBolt provides a simple way to turn Grafana email alerts into SMS without adding another system.
For teams running formal incident programs
Full incident management platforms provide on-call schedules, escalation workflows, incident timelines, and SMS notifications through paid plans. They are a strong fit for organizations with established incident response processes.
Recommended
For teams that need direct Grafana-to-SMS alerts
TextBolt works as a standard Grafana email contact point or SMS alert system. Add the gateway address, attach it to a notification policy, and Grafana cloud alerts become texts from your registered business number. Replies return through email.
For teams that need full control
A webhook contact point can call your own service, which then connects to an SMS provider. This gives developers complete control over routing, message formatting, and automation.
CUSTOMER REVIEWS
Three ways customers route SMS through Grafana with TextBolt: replacing OnCall OSS after archival, skipping Cloud IRM seats, and dropping Twilio webhook receivers.

On Google Workspace Marketplace, with
263K+ installs
When OnCall OSS was archived, we had to choose between Grafana Cloud IRM and a Twilio webhook script. TextBolt was the third option we didn’t know existed. Email contact point, gateway address, done. The migration took an afternoon.

SRE Lead
Payments SaaS
Cloud IRM bundles SMS but adds a 2-minute delay we couldn’t tolerate during incidents. TextBolt’s email contact point delivers in seconds, and we’re not paying per-seat for the rest of the IRM features we don’t use.

Platform Engineering Lead
eCommerce SaaS
We had a Lambda receiving Grafana webhooks and forwarding to Twilio. Every Grafana version bump broke something. TextBolt’s email contact is just a contact point — no code, no maintenance, no on-call doc explaining how to redeploy the receiver.

DevOps Manager
Manufacturing SaaS
The numbers that matter when wiring SMS into a Grafana alerting stack.
Up to 98%
SMS Delivery Rate
30 min
End-to-End Setup
Up to 10
Team Members (Standard Plan)
4.4★
Workspace Marketplace (483+ reviews)
No. Grafana Alerting ships with email, Slack, Microsoft Teams, webhook, PagerDuty, OpsGenie, and other contact-point integrations, but SMS is not one of them. GitHub issue grafana/grafana#24546 has been open without a native fix. To send SMS from Grafana, the alerting system needs a connection to an external service like TextBolt (via the email contact point) or a custom webhook to Twilio, Vonage, or AWS SNS.
The Grafana OnCall OSS GitHub project went read-only on 2026-03-24. Active development moved to paid Grafana Cloud IRM. Self-hosted users have three options: pay for Cloud IRM with per-seat licensing (and accept the 2-minute SMS bundle delay and locked message template), rebuild SMS routing through a separate stack, or replace the SMS step with TextBolt’s email contact point path. TextBolt is the no-migration option: same Grafana alert rules, same notification policies, swap the OnCall + Twilio contact for a TextBolt email contact and you’re done.
Sign up for TextBolt and complete onboarding (TextBolt handles 10DLC business verification with The Campaign Registry on your behalf). Once your number is approved, in Grafana Alerting add an email contact point with the address +1[phone]@sendemailtotext.com. Attach the contact point to your notification policy. Every matching alert becomes an SMS in seconds. No webhook handler, no Twilio account, no Lambda or AWS SNS service. The whole integration is the email contact point.
Yes. The TextBolt SMS body is whatever the Grafana alert email body is. Use Grafana’s notification templates, label substitutions, and silent fields to shape the message exactly the way you want. There is no fixed “Grafana OnCall” wrapper, no ASCII heart, no surrounding text you cannot remove. International teams that need translated SMS or regulated industries that need compliance-controlled wording have full control via Grafana templates.
Yes. TextBolt registers your sender identity with The Campaign Registry as part of onboarding so SMS sent through TextBolt routes through carrier-approved 10DLC infrastructure. This satisfies FCC business SMS requirements and avoids the spam-folder filtering that hits unregistered traffic. TextBolt is not HIPAA compliant; healthcare-adjacent monitoring with PHI requirements should contact sales for Enterprise options.
Yes. When an on-call engineer replies “ack,” “rerouting to Sam,” or any other text to a TextBolt-sent SMS, the reply lands as an email in the inbox of whoever the alert came from (typically the Grafana admin or alert-distribution mailbox). The whole rotation sees acknowledgments without logging into a separate IRM dashboard. Replies are routed reliably regardless of the carrier.
About 30 minutes of hands-on configuration: account creation, toll-free business number selection, and adding the email contact point in Grafana. TextBolt handles 10DLC business verification with The Campaign Registry on your behalf in parallel; once the carriers approve your number, trigger a test alert and the first SMS lands in seconds.
The Grafana IRM mobile app (iOS or Android) sends a push notification to the engineer’s own phone when they are signed into the OnCall mobile client. It works for self-alerting an on-call engineer who keeps the app installed and signed in. TextBolt sends a standard SMS to any phone number you specify in the Grafana email contact point, so a recipient does not need to install or sign into the Grafana app, does not need a Grafana Cloud IRM seat, and receives the alert as a normal text message. If the on-call rotation includes contractors, shared phones, or engineers without the IRM app, TextBolt is the path. If every recipient is a Grafana Cloud IRM user with the app installed, push notifications can cover self-alerting at no extra cost.
Grafana alerts can monitor infrastructure, applications, and system performance by tracking data from connected sources. Common examples include alerts for high CPU usage, low available memory, increased error rates, slow API response times, database failures, service downtime, failed deployments, unusual traffic changes, and low disk space.
For DevOps and SRE teams, the most important alerts are usually those that indicate production issues, such as application errors, infrastructure failures, or deployment problems that require immediate action. These alerts can be routed through Grafana notification policies and delivered through channels like email, Slack, or SMS when faster response is needed.
Reach SREs, DevOps, and On-Call Engineers Without a Webhook or IRM Seat
Send SMS from any Grafana alert in about 30 minutes. No Twilio, no Cloud IRM, no Python plus AWS SNS. Just an email contact point.