Existing ownership
MailCalm checks whether a support email already belongs with someone before deciding whether it should enter general round robin.
Support email assignment
Fair round-robin distribution for incoming support requests.
MailCalm fairly distributes genuinely new support emails across the eligible team while preserving ownership where appropriate. It is built for customer emails arriving into a Microsoft 365 team mailbox such as support@, service@, help@ or another customer-facing inbox.
The team gets the right email and carries on working. MailCalm gives you the routing part without replacing the way your team handles email.
Clear ownership
Fair distribution of incoming support requests.
New unowned support requests can enter fair round robin. Existing ownership is checked first, replies can remain with the person already handling the conversation, and returning customers can be routed according to ownership history where applicable.
Specialist emails can be routed differently, and a team member who is unavailable can stop receiving new requests. Existing conversations remain intact.
Normal inbox workflow
Clear ownership without another helpdesk.
Allocated emails are forwarded into each person's configured normal inbox. Ordinary support staff do not install MailCalm or log into another platform. The manager or person responsible for the team inbox controls routing.
Routing flow
MailCalm routes genuinely new support requests after checking context.
01
Support inbox
→02
MailCalm checks ownership and routing rules
→03
Fair round robin for genuinely new requests
→04
Next eligible team member
→05
Person's normal inbox
What MailCalm checks
Fair support email distribution needs more than simply choosing the next person.
Replies and returning customers
Replies can remain with the person already handling the conversation, and returning customers can be routed according to ownership history where applicable.
Specialist requests
Emails matching configured specialist senders, subjects, recipients or keywords can route differently before general support rotation is used.
Eligibility
Individual schedules and Active, Available and Off controls affect who receives new support requests.
Useful fit
Built for customer emails arriving in a Microsoft 365 team inbox.
•
Customer emails arriving in support@, service@ or help@.
•
Teams that need clearer ownership for a shared support inbox.
•
New unowned requests that should be distributed fairly.
•
Replies that should stay with the person already handling the issue.
•
Specialist requests that should go to a suitable eligible person.
•
Managers who want routing control without moving staff into another workspace.
Not a ticketing platform
MailCalm is for teams that want email routed fairly while staying in their existing inboxes.
MailCalm is not a ticketing or helpdesk platform. If a team needs ticket numbers, omnichannel support, customer portals, SLAs, knowledge-base workflows or full helpdesk reporting, a dedicated helpdesk may be more appropriate.
MailCalm is for teams whose main requirement is simply to route incoming email fairly and clearly while staying in their existing inboxes.
Ticket numbers.
Omnichannel support.
Customer portals.
SLA workflows.
Knowledge-base workflows.
Full helpdesk reporting.
Frequently asked questions
Support email assignment questions.
How does round-robin support email assignment work?
MailCalm checks the incoming Microsoft 365 team-inbox email, applies ownership and routing rules, then uses fair round robin for genuinely new support requests when no stronger rule applies.
Does every support email enter round robin?
No. Existing ownership, replies, returning customers, specialist rules, schedules and availability are checked before a new request enters general round robin.
Can replies stay with the same person?
Yes. Replies can remain with the person already handling the conversation where MailCalm's ownership rules identify that owner.
What happens when someone is off or unavailable?
MailCalm uses individual schedules and Active, Available and Off controls when deciding who is eligible. Someone who is off or unavailable stops receiving new requests.
Do support staff need another dashboard?
No. Ordinary support staff do not install MailCalm or log into another dashboard. The manager configures routing, and staff receive allocated emails in their normal inboxes.
Where does the allocated support email appear?
MailCalm forwards each allocated support email to the selected person's configured normal inbox, so the team can carry on handling email in its usual workflow.
Is MailCalm a helpdesk?
No. MailCalm is not a ticketing or helpdesk platform. It provides the routing part for teams whose main requirement is to distribute incoming email fairly and clearly.
Does MailCalm require a formal Microsoft Shared Mailbox?
No. The source inbox must be Microsoft 365, but it can be a formal Microsoft Shared Mailbox or another Microsoft 365 mailbox used as a customer-facing team inbox.
Route incoming support email fairly without replacing the team's email workflow.
Configure the Microsoft 365 inbox, people, schedules and routing rules, then forward each allocation to the right person's normal inbox.