
A useful team message fits in three lines: one action, one owner, one time. A long message goes unread, one posted in the group chat scrolls away with everything else, and an instruction given out loud at shift change gets forgotten. As for a sharp tone, it does more damage than the slip it complains about. AI can help shorten, structure, translate while keeping the original, and soften a tone. It does not write on the manager's behalf without review, and it sends nothing without their confirmation.
Friday, 5:50 p.m., in the locker room
Margaux ties her apron. Her shift starts at 6. On her phone is a message from Franck, the general manager, sent at 4 p.m.:
"Tonight: 2 tables of 10 at 8:30 (back room). Margaux and Yacine on it. Group menu on the sheet at the pass."
Three lines. She knows where she will be, with whom, and where to find the menu. She puts the phone away and heads upstairs.
Last month, the same kind of information arrived differently: a fourteen-line message posted at 11:40 p.m. in the team group chat, between a photo of the terrace and a question about time off. The booking time was on line nine. Two servers missed it. Nobody had worked badly; the message was just poorly put together.
Both scenes are fictional. The gap between them is very common.
Why messages get lost
The thread swallows everything
A group chat mixes the urgent, the trivial and the personal. An important message posted between two others gets skimmed, or skipped. And an instruction that has to last does not belong there at all, as we explain in a procedure buried in WhatsApp is not a procedure.
The sticky note and the verbal handover
The sticky note on the till falls off, curls up, or stays there three weeks after it stopped mattering. A verbal instruction at shift change depends on the memory of the person taking over, at the exact moment they are starting their station with ten other things in mind.
The message that is too long
The longer the message, the deeper the useful part is buried. The manager writes to get everything off their mind; the team reads to find out what they have to do. Those are different needs.
The tone that stings
"Once again, the terrace wasn't cleared. This is unacceptable." Written at midnight after a hard service, it relieves the person sending it. It humiliates the people reading it, including those who had nothing to do with it, and it still does not say who clears the terrace tonight.
The message that arrives at the wrong time
A message sent late at night or on a day off is read outside work, or not read before service. In France, the labor code (article L2242-17) lists the right to disconnect among the subjects of annual negotiation in companies required to hold one; without an agreement, the employer drafts a charter. It also simply works better: a message read at 5:50 p.m., just before service, does more than one received at midnight.
The three-line rule
- One action per message. If you have three things to say, that is often three messages, or a three-line list.
- A named owner. A first name or a station. "The team" does nothing.
- A date or a moment. "Tonight before close", "Thursday before noon". Not "ASAP".
- The key point in line one. What gets read first is often the only part that gets read.
- Facts, not blame. "Last night the chairs were left outside" rather than "as usual".
- In the right place. A message for today's information; a task if someone has to do something; a sheet if the instruction has to last.
- At the right time. Before the shift starts rather than in the middle of the night.
What AI can do, and what it does not do
A manager knows what they want to say. What they lack is the time to say it briefly. An assistant can handle the shaping:
- Shorten. Bring a fourteen-line message down to three, keeping the time, the place and the names.
- Structure. Bring out one action, one owner, one time, and flag when one is missing: "Who is doing it?"
- Translate while keeping the original. For a colleague who struggles to read the main language, suggest a translation under the original, which stays visible. In France, article L1321-6 of the labor code requires documents setting out an employee's obligations to be written in French, and allows translations alongside them. For a hygiene or safety instruction, the translation should be checked by someone who speaks the language. We go further in non-native speakers in the kitchen: understanding without shame.
- Soften a sharp tone. Suggest a version that keeps the substance and the observed fact, without the aggression. The manager chooses.
What it does not do:
- Write on the manager's behalf without review. The message goes out under their name. They answer for it, and a rephrasing can change a word that matters.
- Send without confirmation. The assistant prepares, the manager reads and confirms. A message sent to the whole team by mistake cannot be taken back.
- Read the team's mood in their messages. Softening the tone of your own message is help with writing. Inferring other people's motivation or mood from their messages is something else entirely: Tsuno refuses to do it, and the EU Artificial Intelligence Act (Regulation (EU) 2024/1689, article 5) has prohibited inferring emotions in the workplace since February 2, 2025.
Five messages, before and after
| Original message | What is wrong | Short version |
|---|---|---|
| Fourteen lines at 11:40 p.m. in the group chat: the booking, the menu, a remark about the terrace, a reminder about time off | Booking time on line nine, several subjects mixed, sent at night | "Saturday: group of 20 at 8:30, back room. Margaux and Yacine on it. Group menu on the sheet at the pass." Time off: a separate message, Monday morning. |
| "Once again the terrace wasn't cleared. This is unacceptable." | Blames everyone, no owner, no time | "Last night, chairs and umbrellas were left outside. Tonight, Yacine clears the terrace before 11:30 p.m. and ticks the closing checklist. Thanks." |
| Sticky note on the till: "Call wine supplier" | Who, by when, about what | A task rather than a message: "Franck: call the wine supplier before Thursday noon about the 6 missing cases." |
| At shift change, out loud: "Table 12 is waiting on dessert, and the coffee machine is playing up." | Nothing written, details get lost, nobody owns the machine | "Table 12: dessert ordered at 2:05 p.m., not out yet. Coffee machine: left group head down, use the right one. Awa calls the technician before 4 p.m." |
| "From Monday the dish sinks get emptied after every service and the chemical is dosed with the pump, not by eye." sent to a dishwasher who struggles to read it | Long sentence, no translation, a lasting instruction left in a message | Short original version first, checked translation underneath, and the instruction added to the Dish station sheet, dated. |
In every case, the short version stays friendly. It is easier to follow and leaves no doubt about who does what.
Common mistakes
- Putting everything in the group chat. Today's information gets through; the instruction that has to last dies there.
- Writing in anger. A message written the night of a bad service is reread the next morning, before it is sent.
- Pasting a translation without checking it. On a chemical dose or an allergen, one wrong word can have serious consequences.
- Letting the tool send. Even well worded, the message goes out under your name.
- Naming someone to blame them in front of everyone. The observed fact goes in the team message; the conversation with one person happens face to face, calmly.
What to measure
- The average length of team messages over a week, in lines. Beyond five, something needs another look.
- The share of messages that name an owner and a time. The figure is often lower than you would think.
- The number of "I didn't see the message" over a month. It is the best sign that a message is too long, in the wrong place or sent at the wrong time.
Where Tsuno and San fit in
Tsuno has internal team messaging, organized by channel, so work information does not get mixed up with everything else. When someone has to do something, an assigned task with a due date beats a message: it shows up on that person's Today page and gets ticked off when done. Publishing the schedule notifies the team by email and push notification. The interface is in French and English, and the welcome booklet can be fitted to a language, drafted by AI and reviewed by you before use. The details are on the Features page.
Tsuno's assistant answers in plain language, from Tsuno or from the AI assistant you already use (ChatGPT, Claude, Mistral), with the same permissions. It prepares actions, summarizes their effect, and nothing runs without your confirmation; it is recorded. Tsuno San, the intelligent voice assistant for teams, acts within the person's permissions and evaluates no one. San Voice is available in demo.
As for the rest, shortening, structuring and softening a message when the manager asks, or suggesting a translation under the original, is what a good tool should do and what we are working on in Tsuno. If all you want is to reword a message, a general-purpose assistant already does that very well. What Tsuno adds is where the instruction lives afterwards, who owns it, and the record. And Tsuno refuses to infer anyone's mood from their messages. What we do with your data is described on the Trust and data page.
Further reading
For the big picture of AI on the management side, read the pillar page AI for frontline managers: analyse, advise, reassure. On writing an instruction that says who, what and when, see clear, SMART instructions: what AI changes in handing over work. To get lasting instructions out of the chat thread, read a procedure buried in WhatsApp is not a procedure, and for colleagues who struggle to read the main language, non-native speakers in the kitchen: understanding without shame.
Key takeaways
A team message is judged by what the team does with it: one action, one owner, one time, read before the shift starts. AI can help write it short and right, but the manager reads it, confirms it and answers for it.
Frequently asked questions
How do you write a clear message to a restaurant team?
Three lines at most: what needs doing, who is doing it, by when. One action per message where possible, facts rather than blame, and the important information in the first line.
Why do messages get lost in team group chats?
Because they scroll past with everything else, often arrive outside working hours and name nobody. An instruction that has to last belongs in a sheet or a checklist, not in a chat thread.
Can you use AI to write messages to your team?
To shorten, structure or soften a message, yes. But the manager reads every message before it goes out, and nothing should be sent without their confirmation. AI suggests wording; it does not speak for you.
How do you pass an instruction to a colleague who struggles to read the main language?
Keep the original instruction visible and add a translation underneath, checked by someone who speaks the language when it concerns safety or hygiene. In France, employment law requires work documents to be written in French and allows translations alongside them.
Can a tool read the team's mood from their messages?
It should not. Inferring someone's mood or motivation from their messages is not a work fact. Tsuno refuses to do it, and under EU law, inferring emotions in the workplace has been prohibited since February 2025.