Restaurant Team Chat and Shift Messaging

Every restaurant already has a team chat. Usually it is a personal messenger group with a name like "Kitchen" that has grown to forty people, including two who left last spring. The handoff from the morning shift is somewhere between a photo of someone's lunch and a sticker.

Team chat in Wox is a calmer place for work conversations. It sits inside the same system as your orders, stock and schedules, people join with their Wox accounts, and the history stays with the restaurant rather than on someone's personal phone. This guide covers how to set it up, the habits that make it useful, and the mistakes that turn it back into noise.

Why keep work talk inside Wox

The first reason is membership. Conversations in Wox are made up of people from your organization, signed in with their own accounts. You choose who is in each conversation, and you are not relying on personal phone numbers to reach staff.

The second is context. The person reading a handoff note in Wox is one tap away from the stock screen, the reservation book or the POS. A note that says "we are low on tarragon" is easier to act on when the inventory is right there.

wox.ge

Wox

Team

5 members · 3 locations

+ Invite

AK

Alex K.

Owner

alex@downtown.com

All locations

JR

James R.

Manager

james@midtown.com

Midtown

MS

Maria S.

Chef

maria@downtown.com

Downtown

SP

Sam P.

Line Cook

sam@downtown.com

Downtown

NT

Nina T.

Sous Chef

nina@midtown.com

Midtown

Decide how chat will be used

Before creating anything, spend ten minutes agreeing on a few rules. Teams that skip this end up with the same sprawl they had before, just in a different app.

1. 1Have the operations manager decide which group conversations exist and who belongs in each.
2. 2Agree on expected response times, for example within fifteen minutes during a shift and none on days off.
3. 3Make shift leads responsible for handoff notes and for raising urgent issues.
4. 4Write down what is not for chat: anything urgent enough to need a phone call, such as a gas smell, an injury or a no-show at opening.

Set up your conversations

Wox has two kinds of conversation. A direct chat is between two people. A group has a title and as many members as it needs. Keep the number of groups small; one per location or one per function is usually enough.

1. 1Open Team Chat in Wox and start a new chat.
2. 2To create a group, select several people and give the group a clear title, such as "Rustaveli kitchen" or "Batumi floor".
3. 3Add the people who work in that location or function, based on their role.
4. 4For one-on-one coordination that the group does not need to see, select a single person to start a direct chat.
5. 5Pin the conversations you use most so they stay at the top of your list.

Pins are personal. When a sous chef pins the kitchen group, it moves to the top of their list only, not everyone's. Each person can arrange their own list around the conversations they need.

If someone joins later, add them to the group from the conversation details. If a conversation is no longer relevant to someone, they can leave it.

Make the shift handoff a habit

The most valuable message in a restaurant day is the one that passes the shift from one lead to the next. When it is written in the same place every day, nobody has to ask what happened at lunch.

The handoff note should answer the question the next shift lead would otherwise call to ask.

1. 1Before the end of the shift, open the group for your location.
2. 2List what has sold out or is running low, such as khinkali dough or a particular wine by the glass.
3. 3Note deliveries still expected and anything wrong with deliveries that arrived.
4. 4Mention equipment problems, for example a fryer that is slow to heat or a fridge door that does not seal.
5. 5Flag reservations or guests that need attention tonight, such as a supra for twenty at nine.
6. 6Attach a photo where it helps, like a damaged crate or a delivery note.

Each message can carry up to ten images of up to 10 MB each. Photos of a delivery problem are often clearer than a paragraph describing it, and they stay attached to the conversation for whoever needs to follow up with the supplier.

Keep conversations focused

Reply to a specific message when you are answering it, so the answer stays attached to the question in a busy group. Forward a message to another conversation rather than retyping it. Use the search in your conversation list to jump to a chat by name.

When people are not in the app, they get a notification for new messages. Opening a conversation marks it as read, so unread counts reflect what someone has actually seen.

Safety and respect

Work chat should be a professional place. Anyone can mute a person whose messages they do not need notifications for, block someone, or report a specific message. Reports go to moderation for review.

Monthly tidy-up

1. 1Once a month, look through the list of group conversations.
2. 2Check that each group still has the right members, add anyone new, and ask people who no longer need a group to leave it.
3. 3Leave groups that are no longer active, and ask the team to do the same.
4. 4Merge the purpose of overlapping groups into one and tell the team which to use.

Common mistakes

Too many groups is the first. If a cook needs to check six conversations to know what is happening, they will check none. Keep to one per location or function.

No handoff habit is the second. Chat only replaces the phone call between shift leads if the note is written every day. Make the end-of-shift note part of the closing checklist.

For more on who can see what in Wox, read team roles and permissions. For alerts that come from the system rather than from people, see notifications and alerts. Chat also works in the mobile app.