Email journey examples

See how MailCalm routeseach email to the right person.

Follow real shared-inbox scenarios from arrival to assignment. Each visual example shows what arrived, which MailCalm rules were checked, and why the email reached its final owner.

Round RobinSticky OwnershipSpecial RuleAvailabilityScheduleCustomer extractionReturn to rotation

Journey 01

New sales enquiry

New enquiry → fair allocation

Outcome

Assigned to Alex

No owner exists yet, so it goes to the next available person.

From: sarah@oakandstone.co.uk

To: sales@company.co.uk

Subject: Request for a product demonstration

Shared inbox

Email arrives

A brand-new enquiry lands in the shared inbox.

↓→

Sticky Ownership

Ownership check

No previous owner is found.

↓→

Availability + Schedule

Availability check

Available people are identified.

↓→

Round Robin

Fair allocation

Alex is next in the fair rotation.

Journey 02

Existing customer reply

Reply → keep the same owner

Outcome

Kept with Alex

MailCalm sees the returning customer and preserves ownership.

From: sarah@oakandstone.co.uk

To: sales@company.co.uk

Subject: Re: Request for a product demonstration

Shared inbox

Reply arrives

The customer replies into the shared mailbox.

↓→

Sticky Ownership

Owner found

Alex already owns this customer.

↓→

Availability + Schedule

Availability check

Alex is currently available.

↓→

Sticky Ownership

Ownership preserved

The reply stays with Alex.

Journey 03

Team member on holiday

Usual owner off → automatic reassignment

Outcome

Reassigned to Priya

Alex normally owns it, but is Off, so MailCalm safely finds cover.

From: sarah@oakandstone.co.uk

To: sales@company.co.uk

Subject: Need updated pricing today

Sticky Ownership

Customer recognised

MailCalm identifies the usual owner.

↓→

Availability

Owner unavailable

Alex is marked Off for holiday.

↓→

Schedule

Working team checked

Only eligible people remain.

↓→

Round Robin

Cover assigned

Priya is next available.

Journey 04

Priority customer complaint

Priority phrase found → manager route

Outcome

Sent to Dan

A priority phrase triggers a Special Rule, so the email bypasses general rotation.

From: customer@northstarservices.com

To: support@company.co.uk

Subject: Urgent: complaint requires manager review

Shared inbox

Email arrives

The request lands in the shared inbox.

↓→

Special Rule

Trigger detected

“complaint” is found.

↓→

Availability + Schedule

Manager checked

Dan is the designated manager and is currently available.

↓→

Special Rule

Direct route

The email is routed directly to Dan.

Journey 05

Holiday-cover workflow

Covered mailbox email → shared fairly

Outcome

Assigned to Sophie

Covered emails can still be distributed fairly across the team.

From: client@harbourgroup.co.uk

To: team@company.co.uk

Subject: Account query for Jordan

Shared inbox

Covered email arrives

An absent colleague’s email reaches the shared mailbox.

↓→

Sticky Ownership

Sticky exception

The absent colleague is excluded from creating a false owner match.

↓→

Availability + Schedule

Eligible team checked

Only working, available people remain.

↓→

Round Robin

Shared cover

Sophie is next in the rotation.

Journey 06

Website enquiry

Website notification → customer identified → routed

Outcome

Assigned to Priya

MailCalm identifies the real customer address so ownership can be tracked correctly.

From: notifications@websiteforms.com

To: sales@company.co.uk

Subject: New website enquiry

Shared inbox

Form alert arrives

The sender is the website platform, not the customer.

↓→

Customer extraction

Customer identified

MailCalm finds the real customer address inside the form.

↓→

Sticky Ownership

Ownership check

No previous owner is found.

↓→

Round Robin

Fair allocation

Priya is next available.

Journey 07

Incorrect Special Rule assignment

Wrong specialist → return to general rotation

Outcome

Reassigned to Sophie

The original Special Rule is bypassed for this return, and the email safely re-enters general rotation.

From: client@harbourgroup.co.uk

To: team@company.co.uk

Subject: Urgent artwork question for tomorrow

Special Rule

Special Rule matches

A trigger phrase sends the email to Dan, but the request is not actually for him.

↓→

Return to rotation

Email returned

Dan forwards the routed email back to the shared inbox. No marker needs to be typed or edited.

↓→

Return to rotation

Trapping rules bypassed

MailCalm ignores the original Special Rule, Sticky ownership and direct-person Filters for this routing pass.

↓→

Round Robin

Fair reassignment

Dan is excluded, eligible people are checked, and Sophie receives the email through normal rotation.

Simple routing logic. Clear outcomes.

MailCalm is not a black box. It follows clear routing rules, so your team can understand why each email was assigned.

Get in touch View plans