Send Checkmk Host and Service Alerts as Text

Turn any Checkmk host or service notification into an instant text/SMS with TextBolt, sent from a 10DLC-compliant business number. Reach the on-call sysadmin without a GSM modem or a per-seat paging platform.

  • Checkmark Add a gateway address to any notification rule and the alert becomes text
  • Checkmark Works with your 10DLC business number
  • Checkmark Replies thread back to the admin’s inbox
Delivery rate
Up to 98% SMS Delivery Rate
Setup time
30 min Setup Time
Team members
Up to 10 Team Members
Shield
Built for teams who can’t afford to miss critical alerts. Trusted by DevOps, IT, and Support teams worldwide.
Send Text Alerts Directly from Checkmk

Common Challenges of Sending SMS Alerts From Checkmk

Checkmk sends notifications to email, Slack, PagerDuty, Opsgenie, Microsoft Teams, Cisco Webex, and other services through its Notification rules engine. Cloud SMS is not a native notification method. As a result, many sysadmins, IT operations teams, NOC engineers, and MSPs face the same challenges when adding SMS alerting to their Checkmk environment.

No native SMS

Checkmk Has No Built-In Cloud SMS Method

Checkmk supports notifications through email, Slack, PagerDuty, ServiceNow, Opsgenie, Splunk On-Call, Microsoft Teams, Cisco Webex, and more, but not cloud SMS. Its only native SMS option requires a local GSM modem with smstools and manual configuration. TextBolt uses your existing email notification rules to deliver SMS without installing anything on the Checkmk server.

Gateways shut down

Carrier Email-to-SMS Gateways No Longer Work

Many teams previously sent Checkmk email alerts to carrier gateways like @vtext.com, @txt.att.net, and @tmomail.net. That workaround is disappearing. AT&T and T-Mobile have already retired their gateways, and Verizon is shutting down vtext.com by March 31, 2027. Existing SMS alert workflows can silently stop working.

Unreliable gateways

A GSM Modem Creates a Single Point of Failure

Checkmk’s native SMS method depends on a GSM modem, SIM card, and active carrier plan. Hardware failures, expired SIMs, signal loss, or USB disconnects can stop alerts completely. Administrators have also reported built-in SMS handler issues on the Checkmk forum. Maintaining dedicated hardware adds unnecessary risk to your monitoring notification pipeline.

 Gmail Has No Native SMS Feature

Custom SMS Scripts Require Ongoing Maintenance

Checkmk also supports custom notification scripts that connect to SMS APIs like Twilio. Someone must build and maintain the script, manage API credentials, update it when APIs change, and monitor per-message costs. Instead of simplifying alerting, the SMS integration becomes another application your operations team must maintain.

Replies Disappear

PagerDuty and Opsgenie Add Per-User Costs

Many organizations use PagerDuty or Opsgenie to add SMS notifications to Checkmk. Both are full incident response platforms with per-user licensing on top of your Checkmk Enterprise or MSP subscription. If you only need SMS alerts, paying for an entire IRM platform can be an expensive solution.

Fragmented teams

Two-Way SMS Usually Requires an IRM Platform

Native GSM modem and custom-script methods only send one-way SMS alerts. Two-way acknowledgments are typically available only through incident response platforms like PagerDuty or Opsgenie. Teams that simply want engineers to reply to alerts from their phones often end up deploying a much larger incident management solution than they actually need.

Benefits of Sending Checkmk Alerts as SMS With TextBolt

TextBolt connects Checkmk to a registered 10DLC business number using the same email notification method your notification rules already use. There is no GSM modem, smstools, custom notification script, or PagerDuty/Opsgenie integration to manage. You simply add TextBolt as an email recipient, and Checkmk notifications become SMS alerts.

Send SMS instantly

SMS Reaches the On-Call Engineer in Seconds

Every Checkmk notification is converted into an SMS within seconds. Critical alerts such as Host Down, Service Critical, Disk Nearly Full, Database Unreachable, or Certificate Expiring reach the on-call sysadmin, NOC technician, or IT operations engineer immediately, reducing response time before users notice an outage.

10DLC compliant

Carrier-Compliant 10DLC Delivery

TextBolt registers your business with The Campaign Registry during onboarding and sends messages through carrier-approved 10DLC infrastructure. You get a professional business number, high delivery rates, and an exportable message history, making it suitable for regulated industries such as healthcare, finance, and government.

Two-way replies

Two-Way SMS Replies

When an engineer replies with messages like “On it,” “Investigating,” or “Handing to Priya,” TextBolt delivers that reply to the original notification email inbox. Everyone monitoring the mailbox sees the acknowledgement, enabling simple two-way communication without deploying a separate incident management platform.

Email-native

Add TextBolt as an Email Recipient

Open your Checkmk notification rule, select the HTML or ASCII email method, choose Explicit email addresses, and enter +15551234567@sendemailtotext.com. Checkmk sends the notification email to TextBolt, which converts it into SMS. No Checkmk user account, contact object, or additional plugin is required.

Shared Account

No Hardware, Scripts, or Per-Seat Licensing

TextBolt eliminates the need for GSM modems, SIM cards, smstools, custom scripts, or per-user incident response platforms. It works with the email notification method already included in every Checkmk edition. One subscription supports up to 10 team members without additional seat licensing.

No code required

Works With Every Checkmk Edition

Because every Checkmk edition supports email notifications, TextBolt works with Checkmk Raw, Enterprise, Cloud, and MSP. The same email-to-SMS workflow works across all deployments, with no edition-specific configuration, plugins, or upgrades required. One account can support your entire Checkmk environment.

Performance Metrics

Up to 98%

SMS Delivery Rate

Two-Way-f9cf1b

Two-Way

SMS Replies to Your Inbox

Carrier-Grade-1f829c

Carrier-Grade

Routes & Infrastructure

Up to 10-604a83

Up to 10

Team Members on Shared Account

How to Set Up Checkmk SMS With TextBolt

Hands-on setup takes around 30 minutes. TextBolt handles 10DLC business verification with The Campaign Registry on your behalf in parallel. No modem to configure, no smstools daemon to start, no script to deploy on the Checkmk server.

Sign Up for TextBolt and Choose a Business Number

Create your TextBolt account using your work email. Account creation takes about 2 minutes. The account ties to your domain so you can add coworkers later. Then, pick a dedicated toll-free or 10DLC number for outbound SMS. The number is the sender ID on every SMS Checkmk sends through TextBolt.

TextBolt Handles 10DLC Business Verification

Provide your business details during TextBolt onboarding. TextBolt handles 10DLC business and campaign registration with The Campaign Registry on your behalf, so you don’t manage the registration process yourself. Once approved, your number is enabled for compliant business SMS.

Add a Checkmk User for the TextBolt Address

Go to Setup > Users > Users and create or edit the user who should receive texts. Under Contact Information, put the TextBolt gateway address in the Email address field in the form +15551234567@sendemailtotext.com, then add the user to the relevant Contact Group such as Linux Admins or Network Engineering. The Pager number field is only for Checkmk’s native smstools modem method, so leave it empty for this path.

Create the Notification Rule

Go to Setup > Events > Notifications and click Add notification rule. Set the Notification Method to HTML Email or ASCII Email. With the gateway address on the user you just set up, the rule hands that notification to TextBolt, which converts the email to SMS. To skip the user object entirely, choose Add recipient > Explicit email addresses instead and enter the gateway address directly on the rule.

Filter to Critical and Down States

Scroll to the rule’s Conditions and add Match host states or Match service states, restricting the SMS to the states that need a person awake, usually DOWN and CRITICAL. Save the rule and Activate changes to deploy it live. Lower-severity events keep going to email or Slack instead of the on-call phone.

Trigger a Test Notification

Use Checkmk’s built-in Test notifications feature (Setup > Events > Notifications > Test notifications) to fire a sample host or service notification, or temporarily lower a threshold to trip a real check. The SMS should land within seconds. Check the TextBolt delivery log to confirm.

How to Set Up Checkmk SMS With TextBolt

Your Notification Rules Stay the Same. The Alerts Now Reach a Phone.

Sign up, grab your gateway address, and paste it into a Checkmk notification rule. Most teams finish setup during a single maintenance window.

Three Ways to Send SMS From Checkmk

1. Single Gateway Address on a Notification Rule (Most Common)

Add +1[phone]@sendemailtotext.com as an explicit recipient in a notification rule that uses Checkmk’s email method. Checkmk sends the notification email to TextBolt, which converts it into an SMS. This is the simplest option for a single on-call engineer, solo administrator, or basic escalation workflow.

2. Conditional SMS Routing With Notification Rules

Use Checkmk notification rule conditions such as host groups, service groups, host tags, or notification periods to route alerts to different gateway addresses. Teams receive only relevant SMS alerts based on severity, environment, customer, or on-call schedule, making it ideal for NOCs and MSPs without custom scripts or plugins.

3. Replace GSM Modems or Carrier Email Gateways

If you’re using a GSM modem or retired carrier gateways like @vtext.com, replace the recipient with your TextBolt gateway address. Your existing notification rules remain unchanged while eliminating the modem, SIM card, smstools daemon, and discontinued carrier email-to-SMS gateways.

Checkmk Alert Types That Use TextBolt SMS

Five common Checkmk notification categories where SMS to the on-call engineer replaces a GSM modem, a per-seat IRM plugin, or a dead carrier gateway. The same email method works across every check type. TextBolt is built for operational alerts to your own on-call IT staff, not for cold customer outreach or marketing campaigns.

Host and Availability Alerts

Sysadmins get SMS for host DOWN, UNREACHABLE, and recovery-to-UP events on servers, network switches, routers, firewalls, and VPN devices. The same email method works on every host notification rule, so a switch going offline at 2 AM reaches the on-call phone in seconds.

Server Resource Alerts

IT operations engineers get SMS for CPU spikes, memory pressure, disk-space thresholds (“C: drive is 95% full”), and stopped services before applications crash. Standard email-method rule, no per-check configuration.

Database Alerts

Database admins get SMS when MySQL, PostgreSQL, SQL Server, or Oracle response times climb, replication lags, or a database server goes unreachable. Checkmk reports the issue through the same email method before users start filing tickets.

Website and Certificate Alerts

Web and platform teams get SMS when a site starts returning 500 errors, load time crosses a threshold, or an HTTPS certificate is about to expire. Checkmk’s HTTP and certificate checks push through the same gateway-address pattern.

Cloud and Container Alerts

DevOps engineers running Checkmk against AWS, Azure, GCP, Kubernetes, and Docker get SMS for instance failures, node-pool problems, container restarts, and managed-service disruptions surfaced through Checkmk. One TextBolt account covers the whole stack.

IT-and-DevOps-Teams

Built for Compliance and Security

10DLC Compliant

Carrier Approved

Complete Audit Trail

Checkmk SMS Options: GSM Modem, TextBolt, or an Incident Response Platform

There are three practical ways to send SMS alerts from Checkmk. You can use a local GSM modem or SMS gateway appliance, route notifications through an email-to-SMS service like TextBolt, or connect Checkmk to an incident response platform such as PagerDuty. Each option differs in cost, maintenance, and operational complexity.

GSM Modem or Hardware SMS Gateway

Local hardware with a SIM card

Checkmk’s native SMS approach relies on a GSM modem, while appliances like SMSEagle or Ozeki provide similar functionality through an on-premises SMS gateway. Both require hardware, a SIM card, and ongoing maintenance. They’re best suited for air-gapped environments where outbound internet access isn’t allowed.

  • XHardware appliance to deploy and maintain
  • X SIM card and carrier plan required
  • X Notification script or manual configuration
  • X Single point of failure
  • X No email-threaded two-way replies

TextBolt

Flat monthly plan, no per-message billing

Add +1[phone]@sendemailtotext.com as an explicit recipient in your Checkmk notification rule. TextBolt converts the notification email into SMS using a registered 10DLC business number. No hardware, scripts, or additional monitoring plugins are required.

  • Checkmark Up to 98% delivery rate
  • Checkmark 10DLC-compliant business number
  • Checkmark No modem, SIM, or custom scripts
  • Checkmark Multi-user access: up to 10 team members
  • Checkmark Replies in admin’s inbox
  • Checkmark Works with Raw, Enterprise, Cloud, and MSP editions

Incident Response Platforms (PagerDuty, ilert, SIGNL4, Splunk On-Call)

Enterprise alerting and on-call management

These platforms integrate with Checkmk and provide SMS, escalations, on-call scheduling, mobile apps, and incident management. They’re designed for enterprise operations, but per-user licensing and additional platform administration can make them more than teams need if SMS delivery is the only requirement.

  • X Per-user subscription costs
  • X Separate platform to deploy and manage
  • X Includes advanced IRM features beyond SMS
  • X Best for large operations with structured on-call processes

CUSTOMER REVIEWS

What Customers Say About Checkmk SMS Alerts

Three IT teams share how TextBolt replaced GSM modems, carrier email gateways, and expensive incident management platforms with reliable Checkmk SMS alerts.

Frame 1686556011

On Google Workspace Marketplace, with

263K+ installs

We were still relying on a GSM modem for Checkmk notifications. Every few months the SIM would expire or the modem would disconnect, and we’d find out only after missing an alert. TextBolt let us keep our existing notification rules and removed that entire failure point

Brian Stanley

Senior Systems Administrator

Managed Service Provider

When Verizon started retiring its email-to-SMS gateway, our Checkmk alerts stopped reaching the on-call phone. We replaced the old recipient address with TextBolt’s gateway and everything worked again. No plugins, no scripts, and no changes to our monitoring setup.

Jimmy Parker

NOC Manager

Manufacturing Company

We looked at PagerDuty, but paying per user just to get SMS notifications didn’t make sense. TextBolt plugged into Checkmk’s existing email notifications, gave us two-way texting, and our entire operations team was live in less than an hour.

Mike S.

Infrastructure Operations Manager

Financial Services

Why Checkmk Teams Pick TextBolt

The things that matter when wiring SMS into a Checkmk notification stack.

Up to 98%

SMS Delivery Rate

30 min

End-to-End Setup

Up to 10

Team Members on Standard Plan

4.4★

Workspace Marketplace (483+ reviews)

Frequently Asked Questions

Can Checkmk send SMS without a modem?

Yes. Checkmk’s native SMS needs a GSM modem, but TextBolt uses Checkmk’s email instead. You add a gateway address to a notification rule and the email becomes a text, so there is no modem, SIM, or smstools daemon involved.

How do I set up SMS alerts in Checkmk?

Create a TextBolt account, then in Checkmk put the gateway address on a user’s email field, build a notification rule with the HTML Email method, and limit it to critical or down states. Save, activate changes, and send a test. It takes about 30 minutes.

Where do I add the TextBolt gateway address?

In a notification rule under Setup > Events > Notifications, or on a user’s email field under Setup > Users > Users. Either way, Checkmk sends the alert email to that address and TextBolt turns it into a text.

Which Checkmk alerts can I turn into text?

Any alert sent by email: host down or unreachable, service critical or warning, flapping, recovery, and scheduled-downtime notices. If the rule uses the email method, TextBolt can deliver it as SMS.

Does Checkmk support SMS through an API?

Only through a custom script that calls an SMS API like Twilio, or a plugin like ilert or SIGNL4 that uses its own API key. Both need credentials and upkeep. TextBolt skips the API and uses Checkmk’s email method instead.

Can I use email-to-SMS instead of direct SMS?

Yes, and it is usually simpler. Direct SMS needs a modem or an API. Email-to-SMS reuses the notification email Checkmk already sends, so you just point a rule at a gateway address.

How do I send only critical alerts by SMS?

In the notification rule’s conditions, set the service state to CRITICAL and the host state to DOWN, and leave warnings out. Only those events become texts, so the on-call phone stays quiet otherwise.

Can an engineer reply to acknowledge an alert?

Yes. A reply to the text arrives as an email in the sender’s inbox, so the rotation sees the acknowledgment. It does not write back into Checkmk itself, which still needs the Checkmk interface.

Does it work with the free Checkmk Raw edition?

Yes. TextBolt works on any edition with the email method, which includes Raw, Enterprise, Cloud, and MSP. No upgrade is needed.

What is the best SMS provider for Checkmk alerts?

It depends on your setup. For no hardware and no code, an email-to-SMS gateway like TextBolt is simplest.

Why are my Checkmk SMS alerts not sending?

Check that a rule matches the alert and uses the email method, that the gateway address is typed correctly, and that Checkmk’s mail server is actually sending email. Then confirm 10DLC approval and check the TextBolt delivery log for a reason code.

Reach the On-Call Sysadmin Without a Modem or a Per-Seat Platform

Send SMS from any Checkmk notification rule in about 30 minutes. Add the gateway address as a recipient and your existing rules, conditions, and schedules keep working, now compliant and two-way.