Restaurant staff communication that reaches people
A restaurant is close to the worst case for internal communication: nobody has a work email, nobody is at a desk, half the team is off at any hour, and a quarter of them will be new by spring. Most of the usual advice assumes none of that is true.
Why it breaks down here specifically
- No work email. Almost nobody on an hourly restaurant roster has a company address, and personal inboxes go unread for days. Reaching employees without work email.
- Split and overlapping shifts. There is no moment when the team is all in the building, so there is no meeting that reaches everyone.
- Phones are away during service. Whatever you send is read before the shift or after it, not during.
- Turnover. A list built in March is wrong by June unless maintaining it is somebody’s actual job.
- Two languages, often. A message only half the kitchen can read is not a message. Texting Spanish-speaking employees.
- Front of house and back of house barely overlap. Most messages apply to one or the other, and sending both to everyone is how people stop reading.
Match the channel to the message
| Message | Channel that works | Why |
|---|---|---|
| Next week’s schedule | Scheduling app — 7shifts, Toast, When I Work | It needs to be looked up later, not pushed once |
| Call-out, two hours before service | SMS to the people who could cover | The only channel already on the phone and read within minutes |
| Closure, burst pipe, power cut | SMS to everyone scheduled | Has to land before people leave home |
| Menu change, 86’d items, specials | Pre-shift meeting and the board | It is for the people on that shift, not the roster |
| Policy, payroll, new POS steps | Printed notice plus a text pointing at it | Detail needs somewhere to live; the text is just the nudge |
| Team banter and shift swaps between staff | A group chat they already use | This is the one thing a group chat is genuinely good at |
The common mistake is using one channel for all six rows. A WhatsApp group handles the last row well and the first five badly. Why WhatsApp groups fail at work.
Keep the urgent channel separate
If closures and open shifts go into the same thread as photos and chat, the thread gets muted, and a muted thread does not ring at 6am. The fix is not a rule about what people may post — it is a second channel that only ever carries messages a manager needs an answer to.
A broadcast tool does this by sending each person their own individual text. A reply reaches the manager and nobody else, so one open shift does not buzz twenty phones fourteen times. How to group text without reply-all.
Front of house and back of house are different lists
A dish machine failure concerns the kitchen. A POS outage concerns servers. A closure concerns both. Keeping two lists and a combined send costs nothing and is the difference between staff reading your messages and skimming past them. Multi-site operators want the same split by location — texting across multiple locations.
The roster is the real work
- Add the number on day one, in the same pass as the W-4 and the POS login, while you have the new hire in front of you.
- Get an explicit yes. A recorded opt-in, not a nod. What the law expects when you text staff.
- Remove leavers the week they leave. Former staff receiving shift offers is both awkward and a consent problem.
- Audit the list once a quarter, or after any busy-season hiring run. Part-time and seasonal staff.
What this costs a restaurant
Our worked example puts one badly covered shift at around $171, so a month of almost any tool here is cheaper than a single bad Friday. The usual comparison is not tool against nothing, though — it is a $30 to $40 per location per month scheduling suite against a per-employee broadcast tool you add alongside it.
What one no-show actually costs: the cost of an unfilled shift. Industry detail, including how this sits next to 7shifts and Toast: staff texting for restaurants.
Common questions
What is the best way to communicate with restaurant staff?
Use two channels, not one. Keep schedules in your scheduling app where staff can look them up, and send anything urgent — call-outs, closures, open shifts — as SMS, because it is the only channel already on every phone with no app or login. Pre-shift meetings still carry the detail for that day’s service.
Should restaurant managers use a group chat for staff?
For shift swaps and team chat, yes. For announcements and call-outs, no — reply-all noise gets the thread muted, and a muted thread does not deliver the next closure notice either. Keep the urgent channel separate from the social one.
How do I reach kitchen staff who do not read English?
Keep separate lists by language and send the same message twice, written in each. On Airhorn Plus, Groups do this, so the kitchen gets the Spanish version and front of house gets the English one from the same broadcast screen.
Can I text restaurant staff about an open shift?
Yes, with their consent, and it is the fastest way to fill one. Send it as individual texts rather than a group thread so the first yes comes back to you privately and the other replies do not pile onto everyone’s phone.
One text, before service starts
Reach the whole roster or just the kitchen, with replies that come back to you alone. $5/mo plus $0.75 per employee, 7-day free trial, no card.
Free for 7 days and 60 messages — no credit card. Your trial starts when you send your first broadcast, not when you sign up.