Frontline Employees | Internal Communication | Text Messaging
Do you really need an employee communication app?
Who an employee app is great for, where it gets hard, and how to reach your frontline team without asking anyone to download a thing.
TL;DR
- An employee communication app can be great when you have a big comms team and employees already open it every day.
- The hard parts are the download and keeping the feed fresh, and both get harder with frontline teams spread across a lot of locations.
- Text, email and landing pages can reach people on the phones they already carry, with no download.
- You can start with texting now and decide on an app later, with real data on who’s reading.
So here’s the thing: an employee app is kind of like an intranet’s cousin, with a cuter icon, push notifications, and easier access.
And I get why it comes up every time a company starts talking about reaching frontline employees! Everyone has a phone in their pocket, including every nurse, driver, line cook and warehouse lead you’re trying to reach. Put the company on that phone and you’re done, right?
Sometimes, yes! But like its cousin (I wrote about the intranet pipe dream last year), the app comes with a lot of hope attached: one place where every employee goes for everything.
So before you buy an employee communication app, it helps to get clear on what you want it to do. There may be a much easier way to get there!
What you’ll find in this article:
- What people are asking for when they ask for an employee app
- Where an employee app does well, and where it gets hard
- What reaching frontline employees takes
- You don’t have to decide on the app today
- Questions to bring to the stakeholder conversation
1. What people are asking for when they ask for an employee app
When a stakeholder says “we need an app,” they’re usually picturing the frontline employee who doesn’t sit at a desk, may not have a company email address, and hears about the benefits deadline from a coworker in the break room (three days late).
So the asks underneath sound more like this:
- Can we reach people who aren’t at a computer?
- Can urgent news get there in minutes?
- Can employees find the schedule or the PTO policy when they need it?
- Can we tell who got the message?
Those are great goals, and they’re all about reach and measurement. An app is one way to deliver on them, and there are others worth putting on the whiteboard next to it.
2. Where an employee app does well, and where it gets hard
Apps can be wonderful, and push notifications are hard to beat for speed. Whether one fits your company mostly comes down to a single question: is there already a reason for employees to open it every day?
Who it’s for: if you have a large comms team and content production is easy and free-flowing, with something relevant for every role every week, an app gives all of that a home. It’s even better when employees already open it every shift for something they need, like their schedule, because the habit comes built in.
Who it’s a tougher fit for: picture a company with frontline teams spread across a lot of locations, like a manufacturer with a dozen plants or a healthcare system with clinics all over the state. Phones are personal, some computers are shared, and the comms team is a couple of people. They’d be building the habit from scratch at every site and feeding the app enough to make it worth opening.
The hard part comes before any of that. I think about channels as push or pull: push channels (email, text) go to the employee, and pull channels (an intranet, a library of pages) wait for the employee to come to them. An app looks like push channel because of the notifications, but it starts as a very big pull. Somebody has to download it on a personal phone, remember a password, and leave notifications turned on.
No one wakes up thinking “I can’t wait to download my employer’s app today!” They have a job to do. And even if time tracking or time off or shift schedules are a natural part of your app, a dedicated app for THAT is often a better fit. Typically, employees aren’t stopping to browse news in an app while they’re clocking in, submitting requests, etc.) So all in all, each step loses a few people, and the folks who drop off tend to be the same ones you bought the app to reach.
Then there’s the rollout: posters with QR codes, managers reminding their teams, a help desk queue for login resets, and a second push a month later for everyone who missed the first one. But again: plenty of teams pull it off! You’re just signing up for an adoption campaign on top of your regular communications, and it helps to know that going in.
The biggest thing to consider: An app is a feed, and a feed has to stay fresh to be worth opening. Somebody is writing posts, updating what lives inside it, clearing out what’s stale and answering comments, every week, for as long as you have it. Texting asks a lot less of you. You send when a specific group needs to know something, and you stay out of the way the rest of the time.
Frontline employees seem to agree. When theEMPLOYEEapp (a company that literally sells an employee communications app, funny enough) surveyed 1,000 frontline workers, 51% said they wanted to hear from their company by text. Only 19% said they wanted an employee app.
3. What reaching frontline employees takes
Here’s the approach I’d put next to the app: push with the channels your employees already check, and give them one easy place to pull the details from.
- Text messages push the urgent and the short comms. There’s no download and no login. A weather closure or a shift change arrives on the phone they already carry, with a link to the details.
- Email pushes the stories and the substance. It’s still the foundation of internal comms for anyone with an inbox, and it’s where the newsletter and the leadership update belong. For frontline teams, you can still deliver these kinds of updates with occasional texts, or pop up QR codes in the break room for surveys and events.
- Try landing pages as ‘hubs’ for frontline teams. The PTO policy, the holiday schedule, the benefits FAQ, the form everyone asks about. Texts and emails can both point to a page, so the information has one home and you’re never pasting a handbook into a text message.
In Workshop, text messaging, email and pages all run from the same place. You write the message, choose who gets it by text or email (or both), and see who opened and clicked across all of it. That last part helps a lot in the stakeholder conversation, because “did the frontline team see this?” becomes a question you can answer with a chart.
Silver Eagle Distributors in Houston is a great example. They send email and text to about 1,100 employees, and only around 40% of them have a company email address. Their team noticed that frontline employees on a break check their texts before their inbox, so every company email now gets cross-posted to their text list, including a weekly update video every Monday. Read their story.
4. You don’t have to decide on the app today
None of this has to be either/or. Plenty of teams text and email today and add an app down the road, and the two get along well!
Texting is a great way to establish the reach and the behavior first. An app is a huge investment, in budget and in your team’s time, and a few months of texts and emails will show you who’s reading, what they click and which locations are hard to reach before you commit to it.
If the app does arrive, texts and emails are what get people to download it (the same way email is the #1 source of traffic for most intranets), and they keep reaching everyone who never does.
5. Questions to bring to the stakeholder conversation
If you’re in the middle of this decision right now, these are the questions I’d bring to the group. They’re useful whichever way you end up going!
- Who are we trying to reach, and what do they already check every day?
- How many employees would need to download something, and who owns getting them there?
- What’s the plan for the people who never download it? (Put another way: will we still need texting anyway?)
- How quickly does an urgent message need to arrive?
- Where will longer information live, and how do people get back to it?
- How will we know it worked, across every channel?
You may get through the list and still want an app, and that’s a perfectly good outcome! You’ll go in knowing what the rollout takes. 🙂
Start with the phones already in their pockets
Every one of your employees already knows how to read a text and open a link. That’s a pretty great starting point, and it means you can reach your frontline team this month instead of after a long, months-long rollout!
If you want to see how email, text and landing pages work together in Workshop, take a look at frontline messaging or grab a demo and we’ll walk you through it.
FAQs
What is an employee communication app?
It’s a mobile app a company uses to send news and updates to employees, usually with a feed, push notifications and a place to find documents. Employees download it and log in, often on their personal phones.
What’s the difference between an employee app and an intranet?
They’re cousins. Both are places employees go to find company information. An app adds push notifications and is easier to reach from a phone, and it still depends on employees downloading it and coming back.
Do employees have to download an app to get company updates on their phones?
No. Text messages and email both reach a phone with no download and no login, and they can link to a page with the full details.
Is texting better than an employee app for frontline employees?
For reach, usually yes. In theEMPLOYEEapp’s survey of 1,000 frontline workers, 51% wanted company communication by text and 19% wanted an employee app. An app can still be a good fit when employees already open it every day and your team has the capacity to keep it fresh.
Can you use text messages and an employee app together?
Yes, and they help each other. Texts and emails get people to download the app and bring them back to it, and they keep reaching everyone who never does.




