Private Messaging That Lives In The Inbox
Asynchronous, inbox-resident, email-like private messaging, distinct from synchronous Chat. Admins govern who can start a thread, whether messaging is allowed, and how long it lives.
What Messages Does
Message One-to-One
Start a private 1:1 with any teammate, manager, or report. Threads auto-dedupe per pair — messaging someone you already message reopens the existing thread instead of fragmenting the history.
Spin Up A Small Group
Create a private group thread of up to 10 participants for a specific task or huddle, with searchable history. Group messaging is admin-toggleable per business.
Live In The Inbox
Every active thread surfaces in the unified Inbox under a single "Messages" folder, with search across participants and message bodies. Read state is tracked per participant, independent of notification read-state.
Attach Files And Voice Notes
Drive-backed file attachments and record-and-send voice notes on any message — voice notes are transcribed automatically. Attachments are admin-toggleable per business.
Mention And Notify
@mention a participant inside a thread and they get a notification. Messages deliver live, so a thread updates in real time the moment a reply lands.
Archive And Clean Up
Archive a thread to drop it out of the active list without losing the record. Authors can soft-delete their own message — read/unread accounting and the audit record survive.
A Separate, Independently-Governed Messaging Track
Asynchronous And Inbox-Resident — Not Another Chat Window
Messages is built on its own dedicated data model, separate from notifications, so it does not piggyback on the notification system. It is the async, "like email" half of communication that complements synchronous Chat. Conversations wait in the Inbox until the recipient is ready, with per-participant read state driving accurate unread badges.
- Dedicated data model — messages, threads, and participants are modeled separately from notifications.
- One Inbox folder — every active thread in the unified Inbox, searchable across participants and bodies.
- Per-participant read state — a read timestamp per person, independent of any notification read flag.
- Live delivery — new messages reach thread participants in real time.
Governed On Its Own Track, Separate From Chat
Because Messages is governed independently, an admin can disable private messaging org-wide while keeping channels — the Microsoft Teams "No Private Chats" parity — restrict who is allowed to start a thread, and set a retention window that applies to messages only. None of those controls touch Chat. That separation is what regulated and frontline organizations need to shut down ungoverned back-channels or keep history for review.
- Master gate — enable or disable private messaging org-wide without affecting channels.
- Who-can-initiate — everyone, or admins and managers only, may open a new thread.
- Group and attachment toggles — turn small-group threads or file uploads on or off per business.
- Message-only retention — auto-purge after N days, governed separately from channel retention.
Messages In Practice
A practical scope check: what the app covers, which controls matter, and the conversations teams usually run first.
Core capability
Private 1:1 and small-group threads on a dedicated messaging layer that surfaces in the unified Inbox — not an extension of the notification system.
Controls that matter
Four governance toggles: master enable gate, group messages on/off, file uploads on/off, and who can start a thread (everyone, or admins and managers) — plus a message-only retention window in days.
Scope and specs
Useful specs: thread kinds: 2 (one-to-one, group); group participant cap: 10; read state: per-participant read timestamp; default retention: keep forever, configurable per tenant.
Quick coordination
An employee messages a teammate privately from the user directory or org chart without leaving the platform. The thread lands in the recipient's Inbox and updates live when they reply.
Small-group huddle
A lead spins up a private group thread of up to 10 people for a specific task, shares a file and a voice note, and keeps the searchable history in one place.
Manager ↔ frontline check-in
A manager reaches a frontline employee directly; where compliance requires, an admin governs or disables these private back-channels independently of channels.
Connected To The Rest Of MangoApps
→ Inbox
Messages surface as a single "Messages" folder in the unified Inbox, alongside notifications, broadcasts, and agent messages — one place to triage everything.
→ Chat
Chat owns synchronous real-time channels and rooms; Messages owns async private threads. The two are governed separately — disable one without touching the other.
→ Drive
File attachments on a message are Drive-backed, so shared files live in the same store as the rest of the platform — with the same permissions and audit trail.
→ Org Chart & Directory
"Message this person" entry points hang off the user directory and the org chart — start a private thread straight from where you find the person.
→ Performance Reviews
Start a private message from a performance review or self-assessment, so a manager-and-report conversation stays in context and in the Inbox.
→ Voice Notes
Record-and-send voice notes attach to any message and are transcribed with the same pipeline used elsewhere on the platform.
REPLACES POINT TOOLS
One governed messaging track in place of ungoverned back-channels
Most organizations let private 1:1s scatter across Teams chat, Slack DMs, and personal email — three separate stores, three retention policies, and no single admin control. Messages folds internal private correspondence into one governed, inbox-resident track.
Microsoft Teams private chat
1:1 and group chat inside Teams
- Same login and Inbox as Shifts, Tasks, and HR — private messages live where employees already work, not in a separate chat client
- Async, inbox-resident by design — threads wait for the recipient instead of demanding a real-time response like a chat window
- "No Private Chats" parity without the M365 admin center — disable private messaging org-wide with one app gate while channels stay on
Slack DMs
Direct messages inside Slack
- Restrict who can start a thread (everyone vs. admins & managers) — a control Slack reserves for higher Enterprise tiers
- Message-only retention governed separately from channels — keep or purge private history without touching public conversation
- One per-employee platform login covers messaging plus shifts, pay, and tasks — not a second seat in a separate workspace
Personal email for internal 1:1s
Outlook / Gmail for internal back-channels
- Internal private correspondence stays inside the tenant-isolated platform, not scattered across personal inboxes IT can't govern
- Per-participant read state and live delivery — you know a message was seen, which email never tells you reliably
- Searchable threads with @mentions, Drive-backed files, and voice notes in one place — not an email chain with lost attachments
PLATFORM ADVANTAGE
Messages inherits everything else MangoApps already does
A standalone messaging tool has to build, buy, or integrate each of these. Messages gets them for free because the platform already runs them.
Identity & SSO
Inherits your SAML/OIDC SSO, MFA, and SCIM provisioning. Employees message a colleague with the same login they used to clock in.
HRIS-synced rosters
Recipients, the directory, and the org chart come from the live org chart — no separate messaging contact list drifting out of date.
Drive-backed attachments
Files on a message live in the platform Drive, under the same permissions and storage as the rest of the platform.
Tenant isolation
Threads and messages live under the same business-scoping and tenant isolation as every other record — nothing leaks across tenants.
Audit & retention
Soft-deleted messages keep the record, and a per-tenant retention window governs private history on its own track for review.
Voice transcription
Voice notes are transcribed with the same pipeline that powers voice across Chat and other surfaces.
INDUSTRY FIT
Built for organizations that have to govern private messaging
Messages fits any employer, but it earns its keep where compliance, regulators, or a deskless workforce make ungoverned back-channels a real risk.
Financial Services
Disable ungoverned private messaging or retain message history on its own track for review — independently of channels — to meet recordkeeping expectations.
Healthcare
Keep private staff coordination inside a tenant-isolated platform with a retention window, instead of personal text threads and email no one can govern.
Manufacturing
Give plant supervisors a direct line to frontline workers in the same app they use for shifts and pay — with admin control over who can start a thread.
Retail
Store managers reach associates 1:1 or in a small group from the Inbox, while corporate keeps a single org-wide control over private messaging.
Logistics & Transportation
Dispatchers and drivers coordinate in private threads that wait in the Inbox — async by design, so a driver isn't pulled into a live chat on the road.
Public Sector
Records-conscious agencies keep internal private correspondence inside the platform with a governed retention window, not on personal email accounts.
WHY MANGOAPPS WINS
One platform beats a stack of point solutions on every axis
The argument IT, communications, security, and compliance all share — and the one a standalone chat or DM tool structurally cannot answer.
Cheaper than the stack
Private messaging is a platform-included capability — not a second seat in Teams or Slack and not a metered add-on. The bill doesn't grow per messaging user.
More secure
One identity perimeter, one audit log, one tenant-isolation model across every private thread — nothing for security to re-certify in a separate chat tool.
Easier to deploy
Already deployed if you have MangoApps. Turn the app on, set the four governance toggles, and employees message from the Inbox the same day.
Easier to use
Private messages live in the same Inbox employees already check for everything else — no second app, no separate workspace to learn.
Easier to manage
Recipients and the directory come from the HRIS, and one master gate turns private messaging on or off org-wide — without touching channels.
Governed independently
Disable private messaging, restrict who can start a thread, or set a message-only retention window — all on a track separate from Chat. Teams and Slack parity, without the separate admin center.
Customer Success
How Customers Use It
Customer Case Studies
Video Case Studies
Customer Case Studies
Customer Case Studies
Customer Case Studies
Customer Case Studies
At our head office within HR, marketing, and finance, we use ChatGPT quite a bit, and MangoApps AI Helper is a useful tool for us. As I go around to the stores, I’ve been showing them how the AI Intranet Helper can find things and answer plain language questions about our resources, and they’re quite excited about that.
Alison van Zijl
Head of Human Resources
Full House
Frequently Asked Questions
Messages owns the asynchronous, inbox-resident private 1:1 and small-group messaging — conversations that wait in your Inbox like email. Chat owns synchronous, real-time channels and rooms. They are different modalities on different, independently-governed tracks, so an admin can disable private messaging while keeping channels (or the reverse) without affecting the other.
Primarily in the unified Inbox under a single "Messages" folder, which lists every active thread with search across participants and message bodies. You can also start a message from the user directory, the org chart, and a performance review or self-assessment. New conversations open in a composer.
Yes. The app's master gate is the org-wide switch — disable Messages for a tenant and private messaging turns off everywhere, while channels and announcements keep working. This mirrors Microsoft Teams' "No Private Chats" messaging policy. Admins can also restrict who can start a thread to admins and managers only.
Read state is tracked per participant via a last_read_at timestamp on each person's participant record — independent of the notification read flag. That drives accurate unread counts in the Inbox folder, and it survives when an author soft-deletes one of their own messages.
Yes. Messages support Drive-backed file attachments and record-and-send voice notes, with voice notes transcribed via Whisper. Both attachments and group messaging are admin-toggleable per business, so a tenant can allow or block them.
Messages live in PostgreSQL (the platform_direct_message tables) under the same tenant isolation as the rest of the platform. By default history is kept forever; a per-tenant retention window (in days) auto-purges older messages on a track governed separately from channel retention. Author-only soft-delete removes a single message while preserving the audit record.
No. Messages is a platform-included capability — it is not metered and not sold as a standalone line. Private 1:1 and small-group messaging comes with the platform.
Let's Talk
Since 2008, we've been building the employee platform for the frontline, earning the trust of 2 million+ users and an NPS of 78.
Why Choose Us?
- AI-Ready Platform: One intelligent place for every employee and workflow.
- Top Security: HITRUST, ISO & SOC 2 certified.
- Exceptional UX: Delightful on mobile and desktop.
- Proven Results: 98% customer retention rate.
Trusted by Legendary Companies:
Prefer to explore first? Ask AI about Messages →