Get Your XProtect Alerts as a Text Message

XProtect is Milestone’s video management software (VMS), the platform many organizations use to run their security camera systems and respond to alarms as they happen. Sending XProtect alarms into text messages is not something the software does on its own.
An alarm fires overnight. XProtect emails the alert, exactly as it’s configured to. Nobody is checking that inbox until morning, so nothing happens until then.
The reason is simple: the XProtect Mail Server tab, the screen behind every email alert XProtect sends, has no way to send a text message instead. According to Milestone’s 2026 R1 documentation, every setting on that tab is built for email, not SMS.
TextBolt closes that gap by turning the same email into a text message, without changing anything inside XProtect itself.
The Mail Server tab is where XProtect stores the settings it uses to send email notifications. It’s a short, five-field screen inside the Management Client, and every one of those fields is built for one thing: getting an email out.
None of them touch a phone number, a carrier network, or an SMS gateway. That gap matters most exactly when it’s least convenient. A camera goes offline at 2 a.m., archiving fails over a weekend, an alarm trips while the security office is unstaffed, and the resulting email just waits in an inbox until someone happens to open it.
That gap comes down to five settings, all sitting on one tab, and every single one of them built for email, not for text.
You’ll find the Mail Server tab under Tools, then Options, in the Management Client. Here’s what each of those five settings actually does.
The address that shows up as the sender on every alert email, across every Notification Profile, something like sender@organization.org.
The address of the SMTP server that actually sends the emails, for example mailserver.organization.org.
The connection port XProtect uses to reach that server. Port 25 by default, which is unencrypted. Port 465 or 587 for an encrypted connection instead.
A checkbox that secures the link between XProtect and the mail server. Turn it on, and the connection starts unencrypted, then switches to SSL using a step called STARTTLS.
Turn this on if your mail server needs a username and password before it will send anything.
That’s the whole tab, five fields, all built for email. Fill them in, connect a Notification Profile to them, and XProtect can send an email the moment an alarm fires. That’s as far as it goes.
Getting that email onto a phone as a text is the next step, and it’s not one this tab can take.
That next step happens outside XProtect, since the tab has nothing left to give. It happens by taking the email XProtect already sends and forwarding it somewhere that turns it into a text: TextBolt.
Make sure your sender and mail server settings are working and a real alert is landing in an inbox you can access directly.
In that inbox’s settings (in Gmail, this is Settings, then Filters and Blocked Addresses, then Create a New Filter), create a rule matching the alert’s sender address or subject line.
Set that rule’s action to forward matching messages to +1[phone number]@sendemailtotext.com, using the phone number of whoever should receive the text.
Trigger the alarm, or wait for a real one, and check that the message reaches the phone within a few minutes.
Nothing changes on the XProtect side through any of this. Your Mail Server tab, Notification Profiles, and alarm definitions stay exactly as they are. TextBolt only ever sees the one email you choose to forward.
Setting up TextBolt takes 10 to 30 minutes. 10DLC approval, required for business texting in the U.S., can take up to 48 hours, so it’s worth starting that early.
XProtect’s Mail Server tab only supports standard SMTP email; there’s no field for a phone number or a text message anywhere on it. The alarm, the rule, and the Notification Profile all stay exactly as they are, since nothing inside XProtect changes.
Forwarding that same email to a TextBolt gateway address is what turns it into a text.
TextBolt fits this gap precisely because it doesn’t ask XProtect to become something it isn’t. There’s no developer, no SDK, and no new platform for your security team to learn, just the one email XProtect already sends, pointed at an address that turns it into a text.
The result: an alarm that used to sit in an inbox overnight now reaches a phone within seconds, without a single change inside XProtect.
It also reaches the right person no matter who that is, an on-call engineer, a subcontracted guard, or a facilities manager who’s never logged into XProtect, since receiving the text doesn’t require an XProtect account at all.
Most of the work is a one-time setup. Once the forwarding rule is in place, every future alarm from that Notification Profile texts automatically, with nothing left to configure on either side.
Ready to set it up, or want to talk it through first? Book a call with the TextBolt team to walk through your setup.
Route Your First XProtect Alarm to a Phone
Point one XProtect alarm rule at your TextBolt address and the next event arrives as a text on your operator’s phone. No plugin, no code, and no change to your alarm logic.
It holds the email settings XProtect uses to send alerts: the sender address, mail server address, port, encryption option, and login, if your server needs one.
No. Every setting on it is for email. There’s no phone number or SMS option anywhere on the screen.
It secures the connection to your mail server, switching from an unencrypted start to SSL using STARTTLS.
Forward the email your Notification Profile already sends to +1[phone number]@sendemailtotext.com. TextBolt turns it into an SMS and sends it to a phone.
No. TextBolt just uses the email your Mail Server tab already sends. Nothing about that tab needs to change.