Conversations, Folders, Tags & Categories
Threads with reply, reply all, forward, drafts and attachments; fixed and custom folders; one colored tag per thread; company categories; starred and flagged views; live updates.
Employees write to HR and HR writes back — inside the platform, next to the employee's record. The inbox sorts what matters, reads the tone and the risk, drafts a reply, and turns a message into a help-desk ticket in one click.
My Inbox is the message center of the employee experience. An employee opens it from Employee Home, writes to the benefits team, files and tags conversations, and gets an answer — as an in-app message and, if they prefer, as an email too. On the HR side, every conversation opens with a card that says how the employee feels, how urgent it is and whether there is a compliance risk, with suggested replies ready to send. When a message is really a problem to solve, Create Ticket hands it to BR Resolve with the story already filled in and a check that nobody has raised it before.
"Most benefits questions arrive as email to a shared HR mailbox: no link to the employee's record, no way to tell an angry, time-critical message from a thank-you, and a copy-and-paste into the help desk when it turns out to be a problem. Benefits Reimagined keeps the conversation inside the platform. The employee writes from their own home page; HR opens the thread next to that employee's coverage and to-dos; the platform sorts, reads and drafts; and a ticket is one click away — with the proof that it is not a duplicate."
What is shared, what is personal, what the platform decides and what it only suggests.
Behaviour as implemented in Benefits Reimagined, September 2026. Names and counts in the illustrations are examples.
Follow one message — "My spouse was dropped from medical" — from the employee's inbox, through the reading the platform adds, to the ticket it becomes; then see the directory and the calendar HR works from, and the same inbox on a phone.
Everyone lands in Mail. The sidebar holds the fixed folders — Inbox, Outbox, Drafts, Archived, Trash — then the folders a person creates, each with its own icon and a favorite mark. Below them sit the person's tags, one color each, and the company's categories, which carry a color and an icon and are attached when a conversation starts. The list itself is split into Focused and Other, decided once when a message is sent from the subject, the wording, who sent it, how many people received it and whether there is an attachment; drafts are never sorted. Open a conversation and the whole thread appears, oldest first, with the sender and recipient chips, attachments kept in the document store, and reply, reply-all and forward. New messages and updated counts appear as they happen, without a refresh.
The message is shared; the housekeeping is personal. Two people on the same thread each keep their own folders, tags and read state.
Quick filters for unread, with-attachment and compliance-flagged conversations are on the roadmap; the date-range filter is live today.
When an administrator opens a conversation, a card at the top says three things about it: the tone of the employee — upset, neutral, pleased — how urgent it is, and a compliance-risk level of high, medium or low with a short reason on hover. Under the card sit two or three suggested replies written for this thread; clicking one opens a reply with that text ready to edit. Each reading is made once per conversation and is advisory: the platform never sends, files, tags or closes anything on its own. The Focused and Other decision made at send time uses the same kind of reading, so the urgent, personal, single-recipient message lands in Focused and the newsletter lands in Other.
HR reads a hundred threads a day in open enrollment; the card says which ten to open first and why.
All readings are suggestions. Nothing is sent, filed or created until a person clicks.
Some messages are questions; some are problems that need a team. For those, the administrator presses Create Ticket on the thread. The platform reads the conversation and proposes a subject, a category and a priority, with how confident it is. Before anything is created it checks for a similar ticket — the same employee, the same problem, recently — and offers to open that one instead, so the help desk never works the same case twice. Then the ticket form from BR Resolve opens with the employee already set from the conversation and, for administrators, the routing section to choose who works it. The administrator reviews, adjusts and creates; from there the ticket follows the help desk's own rules, can become a case, and the thread stays in the inbox for the reply.
The story is already written in the thread; nobody should have to type it a second time into a ticket.
Create Task and Create Event buttons on a message are previews in this release; the ticket path is live.
Contacts is a live directory of employees — search by name, ID or email, filter by department, division, location, state, country and status, select one or more people and press Compose to start a pre-addressed message. For an administrator each row also opens the employee's record, their audit history, payroll and deduction checks in BR ReVerge, carrier reconciliation, their open high-priority to-dos from Employee Home, and the history of earlier conversations with them — the context to answer well, one click from the message. Calendar, for administrators only, shows the benefits communications scheduled from Communication Hub — reminders, notices, nudges — by month, week or day, colored by the kind of offer, with a status filter and the details of each send. It is a window, not a workbench: schedules are made and changed in Communication Hub.
Answering "why was my spouse dropped?" well means seeing the record, the audit trail and the last three conversations — without leaving the message.
The Tasks tab is a preview in this release and does not keep tasks; it is not part of what we promise today.
My Inbox is in the BR Mobile App with the same folders, tags, categories and Focused and Other views as the desktop, and the same rules: the housekeeping is personal, the message is shared, and a draft saved at a desk is sent from the bus. A new message arrives as a push notification that names the sender and opens the thread after unlock; a reply can carry a photographed attachment; and when the employee's preferences include email, the same message reaches their email as a second copy. Contacts works the same way on the phone — search a colleague, press Compose — and administrators keep their shortcuts into the employee's record and the calendar of scheduled communications. The app signs in through the HR system, then with a fingerprint or face, and it opens from the same Employee Home screen the employee already uses.
The upset, urgent message is answered from the phone during the shift, not from a desk at the end of the week.
Push notifications never carry the message text; they say who wrote and the app shows the rest after unlock.
A secure inbox, the readings the platform adds, and the shortcuts that connect a message to the record, the help desk and the calendar.
Threads with reply, reply all, forward, drafts and attachments; fixed and custom folders; one colored tag per thread; company categories; starred and flagged views; live updates.
Decided once at send time from the subject, wording, sender, recipient count and attachment, so urgent personal messages are separated from broadcasts.
Tone, urgency and a compliance-risk level with its reason on every opened thread, plus two or three replies drafted for it — all advisory.
A proposed subject, category and priority, a duplicate check, and the BR Resolve form pre-filled with the employee.
A filterable live directory with pre-addressed Compose; administrators also open the record, audit history, payroll checks, to-dos and past conversations.
A read-only calendar of scheduled communications by offer type and status; a second copy by email when the employee prefers it.
Most benefits questions still arrive as email to hr@ or benefits@. Here is what changes when the conversation lives inside the benefits platform.
| Moment | Shared HR mailbox | Benefits Reimagined My Inbox |
|---|---|---|
| Where the message sits | In an email client, apart from the employee's record. | Next to the record — coverage, to-dos and past conversations one click away. |
| Which to open first | Newest on top; the angry one is somewhere in the pile. | Tone, urgency and compliance risk on every thread; Focused and Other from the start. |
| Writing the reply | From scratch, or from a personal template file. | Two or three suggested replies for this thread, ready to edit. |
| Turning it into a ticket | Copy, paste, retype the employee's details. | One click: subject, category and priority proposed, employee filled in, duplicate checked. |
| Filing and labels | Shared folders everyone fights over. | Your own folders and tags; the message stays shared, the housekeeping is yours. |
| Knowing what HR already sent | Search the sent folder and hope. | A calendar of scheduled communications by offer type and status. |
| Reaching the employee | Whatever address they used last. | The directory, and a second copy by email when they prefer it. |
| On a phone | Email on a personal phone, or nothing. | The same inbox in the BR Mobile App, with a push that opens the message. |
Three readings sit on every opened conversation in My Inbox: the tone of the employee, how urgent it is and whether there is a compliance risk — and two or three suggested replies beneath them. The same intelligence that powers Athena on Employee Home writes these readings from the thread itself, and BR Intelligence proposes the subject, category and priority when the thread becomes a ticket. Everything it produces is a suggestion; the reply, the tag and the ticket are always a person's click. Here is one thread as an administrator sees it.
Every benefits message, reply and attachment sits next to the employee's coverage and to-dos, not in a shared mailbox.
Tone, urgency and compliance risk on every thread; Focused and Other decided at send time.
Two or three suggested replies for the thread that is open, to edit and send.
Subject, category and priority proposed, employee filled in, similar ticket checked, BR Resolve form ready.
Record, audit history, payroll checks, to-dos and past conversations for the person who wrote.
The same folders, tags and readings in the BR Mobile App, with a push that opens the message.
Because every conversation is a record, HR can see the inbox as a whole: how many threads, how many Focused, how many carry a high compliance risk, how many became tickets — and what people are writing about, in what tone. During open enrollment that is an early-warning system: a spike in upset messages about dependent coverage says something about the verification queue before the tickets do. Athena reads the picture and points at the threads to check first; the reply, and any reminder sent through Communication Hub, is a person's decision.
We will load a sample of your benefits mailbox into My Inbox on your own portal, show you which threads the platform flags first and why, turn one into a BR Resolve ticket with the similar-ticket check, and open the calendar of your own scheduled communications — on your portal, with your people.
Every benefits conversation next to the employee's record — on the desktop and on the phone.