Forwarding that comes back
Forward the whole thread or a single message to a supplier or a colleague outside the tool, with a note of your own. Their reply threads straight back into the same conversation.
Shared inboxes
A queue your whole team can work.
Each team gets an inbox backed by one or more Microsoft 365 shared mailboxes. Everyone sees the same list, the same history, and the same answer to the only question that matters: who has this one?
Ownership, not guesswork.
Assign a conversation to a teammate in one click and everybody knows it’s handled. The assignee gets a notification, the thread shows up in their Assigned to me view, and anything nobody has picked up is one click away in Unassigned.
- Assign, reassign or unassign from the thread toolbar
- Cross-inbox views for your own queue, the unassigned pile, and threads shared with you
- Every change lands in the thread’s timeline: who did what, and when
- Live updates: new mail and status changes appear without a refresh
Four states, no filing system.
A conversation is Open while the ball is in your court, Replied once you’ve answered and are waiting on the customer, and Closed when it’s done. Nothing is ever lost to a folder nobody opens.
- Replied is set automatically when you send, so “waiting on us” and “waiting on them” stop looking the same
- Bin is a soft delete. Binned threads are recoverable for 30 days before they’re purged for good
- Per-inbox reply behaviour decides whether a new customer reply reopens a closed thread, or pulls one back out of the bin
- Optional retention automatically bins conversations that have been idle for longer than your policy allows
Reply like it’s email. Because it is.
Mail goes out through the same Microsoft 365 mailbox it arrived on, so the customer stays in one unbroken thread with an address they recognise. No no-reply relay, no rewritten sender.
- Inline quick reply for the short ones; a full composer for everything else
- Cc and Bcc, an editable subject, and file attachments
- Optionally quote the whole thread history, built at send time so the thread view stays readable
- Start a brand-new outbound conversation from any inbox with a connected mailbox
- Anything that fails to send can be re-queued from the thread
The bits you only notice when they’re missing.
Signatures that fill themselves in
Each inbox has its own signature, with tokens for the sender’s name, job title, company and division. One template, correct for everyone.
Clean previews
Exchange “caution: external sender” banners and other boilerplate are stripped from list previews, so you can actually read the first line.
Proper threading
Replies carry the right message-id and references chain, so conversations don’t fragment in the customer’s mail client.
Filters that fit your data
Narrow an inbox by assignee, tag, status, received or replied date, or by any custom field value you’ve defined.
Notifications that reach you
In-app bell plus desktop notifications for mentions, assignments, new mail and threads shared with your team.
One inbox, several mailboxes. A team inbox can be fed by more than one Microsoft 365 mailbox, useful when orders@ and invoices@ are handled by the same people but need to keep their own identities on the way out.
Put your shared mailboxes to work.
We’ll connect one of your mailboxes on the call and you can judge it on real mail.