How do you get an urgent update to the right cleaners across multiple locations?

Yes. Slate lets the operations team narrow an urgent message to the cleaners who need it, review the audience before sending, and see whether each message is sent, still being checked, queued, or failed. That is more useful than sending a single broad announcement and hoping the right people notice it.

Start with the locations and people affected

An administrator opens Messages and chooses the Cleaner audience. Filters can narrow the audience by status, city, client, region, area, property, job, or role. This makes a practical difference for cleaning operations: a water shutoff at one client site can go to the cleaners assigned to that property, while a weather-related change can be scoped to a city or region. A role filter can distinguish cleaners from other people associated with the work.

Before a send, the panel shows how many people are reachable and how many have no phone number. The sender can select the resulting recipients, remove individual people where appropriate, and use a saved template or compose a new message. Personalization placeholders can identify the recipient or work context. The audience preview is a useful final check: it helps an operations lead catch a wrong region or an unexpectedly broad property selection before an urgent message leaves the system.

The sender then reviews the wording and the visible SMS segment count before starting the send. Sending runs as a background job, so the team does not have to keep a browser tab open while a multi-location audience is processed. The in-app message remains the operational record. Where configured, Slate also attempts an SMS mirror so the cleaner can receive the update through the channel used for field communication.

Use delivery states to decide what to do next

The message results distinguish several operational states. A message may be sent, pending, checking, queued, or failed. Those states prevent the team from treating “send started” as proof that every cleaner received an update. A failed SMS can be reviewed and, where it is a terminal SMS failure, retried through the resend workflow. A resend is an operational action to attempt delivery again, not a promise that a phone will receive or display the message.

That visibility supports a sensible escalation routine. First, confirm that the audience and message are correct. Next, check unreachable people and failure states. Then use the approved alternate contact process for cleaners who have no phone number or whose provider delivery did not complete. Keep the update concise and include the site, effective time, and action required. For a scheduled update, Slate records the scheduled message in the application and attempts the SMS mirror at the scheduled time; it preserves non-delivery reasons rather than hiding them.

What this means for a multi-location client

Your cleaners get fewer irrelevant messages, while the operations team has a defensible record of who was targeted and what happened during processing. Regional teams can communicate a change to the correct group without asking every cleaner to interpret a generic notice. A facilities leader can also ask for the audience and failure summary when confirming that a site change was communicated.

This workflow does not guarantee handset delivery, immediate reading, attendance, or compliance with the instruction. Reachability depends on contact data and the configured messaging provider. SMS costs, segment limits, carrier filtering, opt-out rules, and provider outages can affect the result. The message screen is for controlled operational communication; it is not a substitute for emergency services or a second contact method for a safety-critical event. Roles and available filters also depend on the account’s configuration.

See the communication workflow

Ask Slate to walk through a targeted update using your locations, regions, and escalation rules, including how delivery exceptions would be handled.

Discuss your messaging workflow