← Field Notes

One Shared Inbox, Five Jobs: Why Field Service Email Needs Sorting by Type

In many field service businesses, one mailbox does the work of five. Customers, subcontractors, suppliers, quote requests and internal updates all land in the same place, and whoever opens it first becomes the sorting system.

One inbox, five different jobs

Picture the shared inbox at 8am on a Monday. Five messages sit next to each other:

  • A customer asking to move a visit.
  • A subcontractor confirming they can attend on Thursday.
  • A supplier saying a part is delayed.
  • A request for a quote on new work.
  • An internal note about site access.

Five different owners, five different levels of urgency. In the inbox list they look the same: a sender, a subject line and a preview.

Why it keeps happening

Email is the one channel everyone already uses, so everything flows into it. But a mailbox has no idea what a message is for. The sorting happens in someone’s head.

That makes it depend on who is in, who has been there longest and how busy the day is. The fastest reader becomes an unofficial dispatcher. When they go on holiday or leave, the sorting knowledge goes with them.

What it costs

Nothing dramatic goes wrong on any single day. It shows up as small, repeated losses:

  • Messages answered by the wrong person, or twice, or not at all.
  • Urgent items waiting behind routine ones.
  • New starters taking months to learn rules that nobody wrote down.

If you want to see what that adds up to for your business, our calculator takes a minute.

Sort by type, not by who reads fastest

The first automation worth building here is small. Each incoming message is tagged with a type (customer request, subcontractor update, supplier message, quote request or internal) and a suggested owner. It is then routed to the right person or queue.

Type and urgency are separate things. A customer asking to move a visit next month and a customer reporting that an essential system has failed are both customer requests, but they shouldn’t wait in the same queue. Where useful, the workflow can also flag time-sensitive messages separately from their type, so an urgent customer request doesn’t sit alongside a routine update.

Anything the system is unsure about goes to a person to sort. Nothing is sent to anyone outside your business, and no replies go out automatically. Your team can override any tag, and those corrections are how the rules improve.

The inbox can stay shared. The sorting just shouldn’t depend on who happens to open it first.

Frequently Asked Questions

What is email routing for field service businesses?

It is a workflow that reads incoming messages, works out what each one is (a customer request, a subcontractor update, a supplier message and so on), and sends it to the right person or queue.

Do we need to replace our shared inbox?

In many cases, no. The workflow can be designed around your existing email and job management tools, depending on the integrations and access available.

What if a message fits more than one type?

It can carry more than one tag, or be flagged for a person to decide. The goal is a sensible first sort, not a perfect one.

Does it reply to customers automatically?

No. It tags and routes. Your team decides what gets said and when.

Who owns the system once it’s built?

You own everything we build, including the workflows and your data. Hosting, access and any ongoing running costs are agreed in writing before anything is built. We design solutions so you can keep running them, modify them or hand them over without being dependent on us.

If this sounds familiar

If sorting is the problem, you might also find these useful:

For more on how we approach automation in this industry, visit our field service page.

Next step

If one inbox is doing too many jobs, we can look at it with you.

In a free audit we look at how messages actually reach your team and where they get lost or stuck. You decide what, if anything, is worth automating.