Picture an agency worker in her second week at a food plant. She works nights. On Tuesday the safety team changes the cleaning procedure for line 3. The update goes out by email, gets posted on the canteen screen and is read out at the 6 a.m. briefing.
She sees none of it. She has no company email. She walks past the canteen at 10 p.m., when the screen shows the lunch menu. She is asleep at 6 a.m.
Nobody made a mistake here. All three channels worked as designed. They were built for someone else.
The people your channels were not built for
Around 80 percent of the global workforce works away from a desk, according to Microsoft’s frontline research. In logistics, food production, retail, healthcare and hospitality, a large share of that group is temporary: agency staff, seasonal hires, fixed-term contracts that cover a peak and end.
Their time on site is short. In Germany, more than half of all agency employment relationships that ended lasted less than three months, according to the Federal Employment Agency. If your communication starts on day one and builds up over months, it starts too late for these people and ends before it has worked.
The gap is not only about temps. In Microsoft’s Work Trend Index, 63 percent of frontline workers said messages from leadership don’t make it to them. Temps sit at the far end of that chain.
What each channel assumes about the person on the other end
Comparing internal channels by which one is “best” gets you nowhere with a mixed workforce. Each channel assumes something about its reader, and temp workers tend to lack the same five things: a company email, a software licence, a desk, time on site and a shared first language.
| Channel | What it does well | Who it misses |
|---|---|---|
| Shift briefings and team leads | Trust, context, no device needed | Other shifts, days off, anyone who starts mid-week |
| Digital signage | Safety notices, shift figures, ambient reach | Anyone not standing in front of it at the right time |
| Email and intranet | Long-form content, records | Everyone without a company address |
| Microsoft Teams / M365 | Collaboration for licensed staff | Everyone without an account |
| SMS | Reaches any phone | Context, replies, languages, cost control |
| WhatsApp groups | Fast and familiar | Your data protection officer, and anyone who has left |
Briefings and team leads
A good shift lead is still the most trusted channel on any site. The weakness is the relay. Each retelling changes the message a little, nobody records who heard it, and the briefing only reaches the people who are there. Shift leads are also short on information themselves: in the same Microsoft study, 69 percent of frontline managers said their own leadership communicates poorly with them.
Digital signage
Screens work for what everyone should see in passing: safety reminders, output figures, the canteen menu. They are broadcast only. You cannot tell whether a specific person saw a specific message, which matters when the message is a changed hygiene rule. And a screen cannot reach anyone before their first shift or after their last.
Email, intranet and the Microsoft stack
These channels assume an identity. A company address, an Entra ID account, a licence. Microsoft offers cheaper frontline licences for this, and if every permanent employee already runs on Microsoft 365, Teams can look like the free option.
For a worker who stays six weeks, the maths changes. Someone in IT has to create the account, assign the licence, explain the login, reset the password twice and remove it all again when the assignment ends. Multiply that by every peak season. Teams has plenty of features. What it lacks is a way for IT to keep up with a workforce that turns over every few weeks.
WhatsApp is already your channel
When the official channels do not reach people, shift leads open a WhatsApp group. It works on day one, everyone already has the app and nobody needs training. That is why it spreads.
The catch: everyone in the group sees everyone else’s private number. Messages stay on the phones of people who left months ago. The group belongs to whoever set it up, and once that shift lead moves on, nobody owns it or knows what was sent to whom. Under GDPR, your company is still responsible for all of it.
Banning WhatsApp rarely works. Shift leads went there because it solved a real problem. If you take it away, you need to offer something that is just as easy to join on the first day.
What a dedicated app can do that the others cannot
The biggest difference is timing. An app on the worker’s own phone reaches people before their first shift. A temp can get access when the contract is signed, read the site rules, find out where to park and what to wear, and arrive on day one already knowing the basics. With half of assignments ending within three months, those first days carry most of the weight.
You can also send a message to one site, one shift or one language group and see who read it. And when a worker has a question, they can ask it from the bus instead of queuing at the shift office.
Nobody needs a company identity to join. Workers can sign up with an invite code or a QR code on site, so nobody has to create a mailbox first. When the assignment ends, access ends with it. When the same person comes back next season, you can switch them back on instead of starting over.
On many sites, one shift has five first languages. Translated content and push notifications in the worker’s own language do more for understanding than any poster. A modern AI stack helps even the smallest teams to deliver heavily localized communication on a daily basis.
This is also where a lean comms team runs out of hands. Translating every update, preparing welcome content per site and shift, and sending reminders before a first shift is repetitive work. At tchop, customers can connect their own AI agents to the platform to do that part, while the comms team approves what goes out.
Belonging for people who are not on your payroll
Temp workers are often kept out of internal communication on purpose. They are not employees, so the newsletter, the town hall and the recognition posts are for someone else.
I think this is the most underrated point in the whole discussion. Temps run your lines, pack your orders and talk to your customers. If you treat them as guests, they act like guests: they ask fewer questions, leave sooner and don’t come back next season. Letting them read the same news and see the same thank-yous as everyone else costs you almost nothing. Leaving them out costs you in turnover and in mistakes nobody asked about.
When you do not need an app
An app is not always the answer. If you run one site with stable shifts, low turnover and a team that sees each other every day, a good shift lead and a screen in the break room may be enough. The case for an app grows with the number of sites, the number of shifts, the share of temp workers and the number of languages. If none of those apply to you, invest in your shift leads first.
The model that works: one system of record, several channels
Screens, briefings and shift leads keep their jobs. What changes is that each channel gets a clear role:
- Screens for ambient information, with a QR code that leads into the app.
- Shift leads for context and conversation on the floor.
- The app as the place where every message lives, reaches each person on their own phone and can be answered.
That way the night-shift worker from the opening gets the line 3 update on her phone, in her language, before her next shift. And when her assignment ends, her access ends too.
Rolling this out to people without company email raises its own questions: how they log in, who creates their accounts, and how you switch them off again. We cover that in the second part of this series.
Want to see what this looks like for your sites? Book a 20-minute demo.
