A communications professional reviewing a dashboard that maps message types to channels such as email, intranet, chat and face-to-face, with reach figures shown per department and country.

By · Published October 2026 · 10 min read

In short

Email, the intranet, Viva Engage, Teams, managers and face-to-face each reach a different audience. We break down which channel fits which message, why managers and frontline staff need their own plan, and how to check reach by department, country and role before you hit send.

Key takeaways

  • Only 31% of organisations have a channel framework, so most IC teams pick channels message by message instead of by design.
  • Managers account for at least 70% of the variance in team engagement, making them a channel that needs briefing and support.
  • 63% of frontline workers say messages from leadership never reach them, so desk-based channels alone miss most of the workforce.
  • Frontline workers represent 80% of the global workforce, yet most channel plans are built around employees with a desk.
  • Give each message one primary channel and one backup, then check reach by department, country and role before you send.

Which channels do internal communicators have?

If you run internal communication in a Microsoft 365 organisation, your channel list is longer than your message list. Outlook email, SharePoint intranet pages and news posts, Viva Engage communities, Microsoft Teams, Viva Connections, town halls, people managers, and increasingly frontline options such as mobile employee apps. Most of us did not choose this landscape deliberately. Channels accumulated with every platform rollout, and today the routing decision for many messages is habit: the newsletter goes out because it always goes out.

  • Push channels: email newsletters and Teams announcements, where you deliver the message to employees whether they were looking for it or not.
  • Pull channels: SharePoint intranet pages and news posts, where employees find content when they need it and can return to it later.
  • Social channels: Viva Engage communities, where employees can reply publicly, ask questions and shape the conversation.
  • In-person channels: meetings, town halls and people managers, where tone, nuance and context travel face to face.

These are not interchangeable. Microsoft's own guidance on distribution channels treats Outlook, SharePoint, Teams and Viva Engage as distinct formats, each with different strengths, and points out that identifying which format works best for each message improves engagement across your organization[1]. In other words, the question is not which channel is best, but which channel is best for this message and this audience.

The problem is that channel choice today is usually habit, not design. When you route messages by routine instead of by audience and message type, you cannot say why a message went where it went, and you cannot spot the segments your mix quietly misses. Getting the landscape sorted first makes every later decision easier, and our tips for cross-channel internal communication are a practical place to start.

What is each channel best at?

Start with email. Microsoft describes it as the right fit for regularly scheduled, formal messages that affect multiple groups of people, such as business updates and new employee introductions. The trade-offs are just as clear: an email is static once sent, cannot be corrected without a follow-up, and can be filtered out of an inbox before anyone reads it[1]. Email earns its place for formal, record-worthy communication, not for anything that will change by Friday.

SharePoint plays a different role. Pages support dynamic content that can change often, which makes them the natural home for policy changes, ongoing projects and event information that needs updating. A SharePoint news post goes one step further: it surfaces in the Viva Connections feed and on pages that use the news web part, and you can target it to specific audiences such as a Marketing team or Executive leadership[1]. That combination of updatability and targeting is exactly what a formal email cannot offer.

Microsoft Teams and Viva Engage cover the human layer. Teams suits quick notices and short-lived conversation where people already work, though it is worth knowing what Teams silently loses as a communication channel, such as post-level reach, which we cover in our guide to what Teams loses. Viva Engage is where open, cross-community discussion belongs: questions, ideas and culture topics that benefit from visible replies rather than one-way delivery.

Message type Primary channel Why it fits
Formal updates Outlook email Suits regularly scheduled, formal messages that affect multiple groups
Quick notices Microsoft Teams Arrives in real time, where people already work
Conversation and Q&A Viva Engage Open discussion with visible replies across communities
Reference content SharePoint pages Dynamic content you can update as details change
Events and policy changes SharePoint news posts Surfaces in the Viva Connections feed and can be targeted to demographics

Why are people managers a channel of their own?

People managers belong in your channel mix, not in the footnotes of it. Gallup finds that managers account for at least 70% of the variance in team engagement, which means the messenger often matters more than the medium[2]. The same message that skimmed past an inbox can land when a manager explains what it means for this team, on this site, this quarter.

  • They add local context: what the message means for this team's priorities, workload and deadlines.
  • They translate: corporate language becomes the team's own vocabulary, and for international teams, often their own language.
  • They create space for questions: employees ask a manager what they would never post under a company-wide announcement.
  • They sense the mood: a manager tells you when a message has landed badly long before any dashboard does.

The catch is that managerial reach is uneven unless you support it. Some managers brief their teams every week; others forward an email and consider it done. Treat managers the way you treat any channel: give them briefing packs and talking points on the messages that must land, build a feedback loop so they can report what they hear, and check whether their teams actually received and understood what you sent. A manager cascade you do not support and measure is a channel in name only.

How do you reach employees without a desk?

Frontline employees are where channel choice stops being a preference and becomes a reach problem. Microsoft's Work Trend Index special report on frontline workers puts them at 80% of the global workforce, and finds that 63% of them say messages from leadership do not make it to them[3]. Their managers fare no better: 69% of frontline managers say their higher-ups do not communicate effectively with them either[3]. If your channel mix leans on email and intranet news, a large share of your workforce is structurally out of reach.

This is not a niche gap. Frontline and deskless employees make up the majority of headcount in many enterprise organisations and are typically under-served by digital internal communication channels. The channels that work best for them share three traits:

  • Mobile-first delivery: Viva Connections puts your SharePoint news in a phone-friendly feed, which is where a shift worker can actually read it.
  • Shift-friendly formats: short, scannable posts beat the 900-word newsletter; save the detail for the linked page.
  • Face-to-face backup: team huddles and people managers remain the channel that must-land messages fall back on when screens are shared or absent.

Whichever combination you pick, measure it separately. Aggregate reach numbers happily hide the fact that your desk staff saw everything and your warehouse saw nothing. We cover how to segment and measure communications for frontline workers in more depth in our guide to measuring frontline communications.

Which channel reaches each segment best?

Here is the uncomfortable benchmark: only 31% of organisations have a channel framework, according to Gallagher's State of the Sector survey[4]. For most teams, that means nobody can answer a simple question from leadership: which channel reaches our sales teams, our plant in Lyon, our night shift? Without a framework, the honest answer is that messages go everywhere and reach whoever happens to be looking.

Building the framework starts with a message-to-channel matrix, then checking it against reality. Map your message types to primary channels as in the table above, then look at reach and response by department, country and role across email, intranet and Viva Engage, rather than reading each platform's native report in isolation; see our guide to measuring cross-channel communications. Audience segmentation is what turns a channel list into a channel plan.

Audience segment Channels that usually work hardest Common blind spot
Desk employees Email and SharePoint intranet Reach is assumed and rarely verified by department
Frontline and shift workers Viva Connections on mobile, team huddles Email newsletters and long intranet posts
People managers Manager briefings plus Teams One-size cascade with no talking points
International sites Segmented news posts and local managers One language, one message, sent to everyone

The point of the matrix is not the document itself. It is what it exposes: the segments your current mix structurally misses, such as the country where email open rates look fine overall but collapse for one language group. Once you know which combination of channel and segment underperforms, you can fix the routing instead of sending more of everything. Our guide to internal communication analytics walks through the four measurement questions to ask first.

Give each message a primary and a backup channel

The matrix becomes useful when you turn it into decision rules your whole team applies without debate. Four rules are enough to start:

  1. Assign every message type one primary channel, based on where its audience demonstrably is, not on where the message has always gone.
  2. Add one backup channel for must-see messages, so nothing critical depends on a single channel's open rate in a given week.
  3. Retire or repurpose channels that consistently reach too few of their target segment. Judge them on reach data, not on how attached the team is to the format.
  4. Review the matrix quarterly. Audiences shift, platforms change their features, and a channel that reached your frontline last year may not reach them now.

The backup rule deserves emphasis. For a restructuring announcement or a safety-critical update, a primary and a backup channel are not redundancy, they are insurance: if the email gets filtered, the news post and the manager briefing still carry it. And the retirement rule is where discipline pays off. Dropping a channel that reaches too few people frees budget and attention for the ones that work, and it is a decision you can defend to leadership with data rather than anecdote.

Measure which channel actually reached your audience

Every rule above depends on one input you cannot fake: knowing which channel actually reached which segment. Native reports cannot give you that answer. Outlook shows open rates, SharePoint shows page views, Viva Engage shows community activity, and each lives in its own tool with its own definitions. Stitching them together in a spreadsheet every month costs you time and still leaves the real question open: did the right people see this message, on the channel we chose for them?

This is where we built Communication Insights. It is an all-in-one cross-channel analytics platform that connects your email newsletters, your SharePoint intranet, Viva Connections and Viva Engage into one central dashboard, so you can compare channel reach by department, country and role in one place instead of reconciling native reports. In practice that means you can:

  • Compare reach per channel for each audience segment, side by side in one dashboard.
  • See which channel each segment actually reads and responds on, and adjust your matrix with evidence.
  • Spot the segments your current mix misses before leadership asks about them.
  • Report on communication impact without spending the first week of every month collecting KPIs.

If you want to see what your own channel mix looks like when every channel is measured in one place, book a 30-minute call with Hatim to see how Communication Insights compares channel reach by audience.

Frequently asked questions

What are the main internal communication channels?

The core mix on Microsoft 365 is email (Outlook), the intranet (SharePoint pages and news posts), enterprise social (Viva Engage), chat (Microsoft Teams) and Viva Connections, plus meetings, people managers and mobile or face-to-face options for frontline staff. Microsoft's guidance treats Outlook, SharePoint, Teams and Viva Engage as distinct formats with different strengths, not interchangeable pipes.

Which internal communication channel is best for formal announcements?

Email suits regularly scheduled, formal messages that affect multiple groups, according to Microsoft's channel guidance. But email is static, cannot be updated once sent, and can be filtered out of inboxes, so pair important announcements with a SharePoint news post that can be corrected or updated and that surfaces in the Viva Connections feed.

How do I reach frontline employees without a desk?

Start by accepting the gap: 63% of frontline workers say messages from leadership never make it to them, and frontline staff represent 80% of the global workforce, according to Microsoft's Work Trend Index. Use mobile-first delivery through Viva Connections, keep formats short and shift-friendly, and route must-land messages through people managers and team huddles.

How many internal communication channels should we use?

There is no fixed number; the goal is coverage without duplication. Only 31% of organisations have a channel framework, according to Gallagher's State of the Sector survey, so most teams default to pushing everything on every channel. A small set of channels, each with a defined message type, beats a long list nobody maintains.

What is an internal communication channel matrix?

A table that maps each message type to a primary channel and a backup channel, then checks actual reach and response by department, country and role. It turns channel choice from a habit into a design decision, and it shows which segments your current mix structurally misses.

Why are people managers considered a communication channel?

Because the messenger often matters as much as the medium. Gallup finds managers account for at least 70% of the variance in team engagement, and they are the only channel that can add local context, translate a corporate message and answer questions on the spot. Their reach is uneven unless you support them with briefing packs and talking points.

Should every message go out on every channel?

No. Blanket posting creates information overload and duplicate messages, and it hides which channel actually worked. Give each message one primary channel and one backup for must-see content, then retire channels that consistently reach too few of their target segment.

How do I know which channel reaches each audience segment?

Compare reach and response by department, country and role across email, the intranet and Viva Engage in one view. Native per-platform reports rarely answer this, because each shows only its own audience; cross-channel analytics that connects all your channels in a central dashboard closes that gap.

Sources

• support.microsoft.com

• gallup.com

• microsoft.com

• allthingsic.com

• ajg.com

Further reading

• Measuring Cross-Channel Internal Communications

• Viva Engage in the Internal Communication Mix, and When It Is the Wrong Channel

• When a Collaboration Platform Improves Internal Communication, and When It Just Adds a Channel

• What SharePoint Does Well as an Internal Communication Channel, and Where It Cannot Help

If you want to see what cross-channel reporting looks like against your real data, Tryane runs a 15-minute walkthrough with no slides. Book a slot with Jérémy.