Write it now. Send it Tuesday at 9.

Most of what an operations team sends by text isn't an alert. It's the shift reminder, the site-access change, the “gates open at 10, park in blue zone” briefing the night before an event. Today that usually means someone copying numbers out of a spreadsheet into their personal phone: untracked, unrepeatable, and gone the moment they change handsets.

Campaigns fix that. Compose a message to one or more of your recipient lists, and either send it now or schedule it for the moment it is most useful. The send goes out from your workspace's own number, on time, whether or not anyone is at a keyboard.

Campaigns are also two-way. Attach a question with keyword choices, such as “Working the late shift Saturday? Reply YES or NO”, and replies are matched and tallied automatically, per person, in your dashboard. You see who said yes, who said no, and who has said nothing at all. Anything that doesn't match a keyword lands in your inbox as a normal reply, so nothing anyone sends is ever lost.

Plans change, so campaigns bend: pause a send part-way through, resume it, or cancel it outright, with live delivery status for every recipient. And because this is whoot., the informational path is built completely apart from the emergency one, so a routine reminder can never slow down a genuine alert.

The obvious concern with adding routine messaging to a life-safety platform is the day both fire at once. We built for that day first. Campaigns run on their own dispatch pipeline, entirely apart from emergency alerts, sharing your recipient lists and your number but never the alert path itself. Content is reviewed for appropriateness before it goes out, opt-outs are honoured automatically, and every send and reply is logged. Routine messages get a proper system, and urgent ones keep their right of way.