"We Already Have Something": Six Objections to a Frontline Communication Platform, Answered Honestly

Most organizations already run an intranet, a chat tool, a newsletter, and an HR suite, and each does the job it was bought to do. The question is not whether those tools work. It is whether any of them reaches an employee with no inbox and proves the message landed. Here are six versions of that conversation, and the honest answer to each.

Somewhere in the second meeting, someone says it. We already have something.

They're usually right. Nobody is starting from nothing. The intranet was a real project with a real budget, the chat tool is open on every laptop at headquarters, and the newsletter goes out on schedule and gets read. The HR suite may have gone live last quarter after a year of work. None of those decisions was a mistake, and anyone who suggests otherwise has not been in the room when they were made.

So the objection deserves a straight answer rather than a pitch. The test that runs through every answer below is the same, and it has nothing to do with whether your current tools work. It is whether any of them was built for the part of the workforce where sending is not reaching: the associate, the line worker, the nurse at shift change, the technician in the van.

We just bought a workforce management or HR suite. Do we have to replace it?

No. You integrate.

Those systems remain the source of truth for the employee record, and they feed a frontline communication platform through native integration. Nothing gets ripped out, and you keep the investment. A platform with 200+ integrations should connect to the HR, workforce management, payroll, and learning systems you already run, so that a role change or a site transfer in HR updates the employee's audiences and access automatically. Nobody reconciles two lists by hand.

That connection is also what makes provisioning work at frontline turnover rates. When a new hire appears in the HR system, they should appear in the right site, shift, language, and audience in the communication platform without a ticket. The HR suite does the hiring. The platform does the reaching.

What those systems don't do is reach a worker with no inbox and prove the message landed. That is a different job. An HR suite is built to hold the record and run the transactions around it, and it does both well. It was never designed to put a safety notice on a warehouse picker's personal phone, in their own language, and then show you an hour before the shift which sites haven't opened it.

The two sit side by side, and the integration between them is built during the connect phase of a rollout, before any employee sees anything.

We already have an intranet. Isn't that enough?

Then you have solved this for the people with a desk.

The question worth asking is what share of your workforce logged into the intranet last week, and whether you can answer that by site. Most organizations can answer it for headquarters. Far fewer can answer it for the distribution centers, the stores, or the night shift, and the ones who can rarely like the number.

An intranet is not the wrong tool. It is a tool built for a different user, as a destination website visited from a computer during working hours. Making it responsive puts that website on a smaller screen, but it is still reached through a sign-in built for a desk identity and still organized for someone browsing rather than someone checking between tasks. The differences between a mobile intranet and a frontline employee app run deeper than screen size.

None of this means switching the intranet off. It keeps serving the people it was built for. The frontline app carries what workers need on shift, the intranet carries what desk teams need at a desk, and the two can run side by side. The decision isn't which one to keep. It's whether the frontline has a front door at all.

We already have a chat tool. Isn't chat enough?

Chat is necessary and not sufficient.

It carries conversation well. It carries governed, targeted, acknowledged communication poorly, because it was built for people talking to each other rather than for an organization making sure a specific message reached a specific group and can be proven to have done so.

Two questions settle it quickly. Can you require acknowledgment on a safety notice, and then evidence it by site and shift? And can a worker with no corporate account be reached at all? A tool that requires a company identity cannot reach someone who was never given one. If the answer to the second question is no, the first one doesn't matter.

There is a second risk hiding in the chat conversation. When the sanctioned channel does not reach frontline teams, they coordinate in personal messaging groups the company does not own and cannot produce in an audit. Combined SEC and CFTC fines for work conducted on unapproved personal messaging channels passed $2.5 billion (SEC and CFTC enforcement actions, 2021 to 2024).

The answer is not less chat. It is chat inside a governed platform, with retention and eDiscovery applied, and with broadcast and acknowledgment sitting beside it rather than improvised on top of it.

Our newsletter gets good open rates. Doesn't that mean communication is working?

Open rates measure the people who received it.

The question is what fraction of the frontline is in that denominator. Roughly 80% of the global workforce is deskless (Emergence Capital, 2018; share reconfirmed by BCG, 2024), and most of those people have no corporate inbox for a newsletter to land in. When Microsoft asked frontline workers directly, 63% said messages from company leadership do not reach them (Microsoft Work Trend Index Special Report, 2022). Not that the messages were unclear or badly timed. That they did not arrive.

So a strong open rate can be completely accurate and still describe the wrong population. In a frontline-heavy organization, the newsletter is often performing well among the desk-based minority who were never the problem, while the people on the floor sit outside the measurement entirely.

A better measure starts with the whole workforce as the denominator. For your last critical message, can you name the sites where acknowledgment fell below target? If the reporting can only tell you who opened an email, it can't tell you who was never sent one.

Won't our frontline resist another app?

They will, and that is the right instinct.

Every additional app is another login, another interface, and another reason for a worker with three minutes to give up. Consolidation is usually presented as an IT saving. On a frontline, it is an adoption strategy.

It is also why a frontline Employee Platform should consolidate rather than add. The schedule, pay, training, and answers belong in the same app that carries the news. The schedule alone changes the math, because it is the single most reliable reason a frontline employee opens an app, and everything else in that app benefits from the visit. MangoApps customers average more than 90% adoption within 90 days, and the reason is not persuasion. The app is where something they need already lives.

The Kansas City Chiefs show the pattern with a workforce that scales up and turns over every season. Their branded app, Huddle, reached 90% adoption among more than 600 game-day event staff, up from a 40% average adoption rate organization-wide. The adoption playbook behind numbers like that has more to do with what the app holds than how it is launched.

Download Frontline Worker Communication & Engagement. It lays out the six reach gaps and the cost model behind each objection answered here. Get the book

There's no budget for a new platform this year. Where would we start?

Start with the gap that costs the most, and run the model with your own numbers.

Most organizations find the turnover line alone exceeds the software cost by an order of magnitude. Take an illustrative employer with 4,000 frontline workers at 40% annual turnover. That is 1,600 separations a year, and at a replacement cost of roughly $12,500 each, about $20 million. Retail frontline turnover runs above 60% a year (McKinsey, 2024), so 40% is deliberately conservative. Bringing turnover down three points, to 37%, returns about $1.5 million a year in the same model. The duplicate software in the same model costs closer to a quarter of a million a year.

The second line changes what the net cost actually is. Most customers retire four to five existing point solutions within eighteen months, covering tools for communication, recognition, engagement, and knowledge that each carry their own contract and security review. The budget for a platform is often already being spent, just in several places.

The business case for frontline communication walks through every line of the model, including supervisor time and compliance exposure. Bring your own headcount and turnover rate, and the conversation with finance changes shape.

The one question underneath all six

Every objection above comes back to one question. Does anything you run today reach an employee with no inbox and prove the message landed?

If the answer is yes, you may not need this. If the answer is no, the tools you have are not wrong. They are incomplete, and the part they leave out is the part of the workforce that serves the customer, treats the patient, and runs the line.

That gap doesn't close by working harder inside the existing channels. It closes when the frontline stops being the part of the workforce that gets reached later.

Score the six reach gaps in your own operation first.

Download the book, or talk to someone who knows your industry.

The AI Platform for the Frontline Workforce.

Frequently asked questions

Do we have to replace our HR or workforce management suite to add a frontline communication platform?

No, you integrate it. The HR and workforce management systems stay the source of truth for the employee record and feed the platform through native integration. Role and site changes then update audiences and access automatically, and nothing gets ripped out.

Is an intranet enough to reach frontline employees?

An intranet solves communication for employees with a desk, but rarely for the frontline. It was built as a destination website visited from a computer, reached through a sign-in that assumes a corporate identity. Check what share of your workforce logged in last week, by site, to see where it stops reaching.

Is a chat tool enough for internal communications?

Chat is necessary but not sufficient. It handles conversation well and handles governed, targeted, acknowledged communication poorly. A chat tool that requires a corporate account also cannot reach a worker who has never been given one.

Do good newsletter open rates mean frontline communication is working?

No, because open rates only measure the people who received the newsletter. Most frontline workers have no corporate inbox, so they sit outside the denominator entirely. Acknowledgment by site on critical messages is a more honest measure.

Will frontline employees use another app?

They will use one that holds something they need on every shift. A platform that brings the schedule, pay, training, and answers into the same app as company news consolidates tools rather than adding one. That is why MangoApps customers average more than 90% adoption within 90 days.

How can we fund a frontline communication platform without new budget?

Start with the gap that costs the most and model it with your own numbers. In most organizations the turnover line alone exceeds the software cost by an order of magnitude. Retiring existing point solutions then offsets much of the software cost itself.

Does an employee app replace the intranet?

Not necessarily. The intranet can keep serving employees at a desk, while the frontline app carries what workers need on shift. The two can run side by side, because the real decision is whether the frontline has a front door at all.

How long before existing tools can be retired?

Most customers retire four to five point solutions within the first eighteen months. The usual candidates are separate tools for communication, recognition, engagement, and knowledge. Each one retired also removes a contract, an integration to maintain, and a security review.