Skip to content
Use case · Admin

Inbox & Request Triage

Inbox and request triage means every email and form request is read, sorted and sent to the right place without anyone sorting by hand. Standard requests get an answer straight away from your templates, urgent ones rise to the top, the rest reach the right person with a summary, and follow-up reminders are set automatically.

Read and categorised
Every message
Ordered by priority
Urgent first
Categories and auto-replies agreed with you
Your rules

What is AI inbox triage?

AI inbox triage is an automation that reads each new email or web form submission, works out what it is, how urgent it is and who should deal with it, then acts on it. Standard requests get an automatic reply, everything else is routed with a short summary, and reminders make sure nothing that needs a reply is forgotten.

It covers requests that arrive by email and web forms. If an AI chat agent already handles your customer support, it sorts and routes chat enquiries as part of that job.

Why do requests get lost in a shared inbox?

Requests get lost in a shared inbox because someone has to read every message just to work out what it is, who owns it and how urgent it is. Enquiries, complaints, support requests and promotions all arrive together. Simple questions wait as long as complicated ones, and urgent messages sink under newsletters.

  1. Sorting by hand

    Every message has to be opened and read before anyone knows what to do with it.
  2. Urgent mail gets buried

    A complaint or a time-sensitive request sits under promotional emails until someone scrolls far enough.
  3. Forwarded twice, or not at all

    Requests bounce between people, and follow-ups depend on someone remembering.

How does AI triage an inbox?

AI triages an inbox in five steps. It reads and classifies each message into the categories you define, answers the standard ones from your templates and knowledge base, routes the rest to the right person through your CRM or project management tool with a summary, orders everything by urgency, and sets follow-up reminders.

With AI automations

A new email in your inbox, or a new submission from a web form

  1. Read and classify

    AI sorts each message into the categories you define, such as enquiry, complaint, support request, urgent, promotional or social. For requests, the category is recorded in your CRM.
  2. Answer the standard ones

    Common requests get an automatic reply from your templates and knowledge base. Where scoped, they can also get a status update from your systems.
  3. Route the rest

    Everything else goes to the right department or person through your CRM or project management tool, with a short summary attached.
  4. Prioritise

    Messages are ordered by urgency, so the ones that matter most are handled first. Where scoped, priority can also weigh response times and each person's workload.
  5. Set reminders

    Follow-up reminders are set automatically, so nothing that needs a reply is forgotten.

Request routing or inbox sorting: where should you start?

Most teams start with one of two builds. Request routing takes enquiries, complaints and support requests from forms and email, answers the standard ones and sends the rest to the right team. Inbox sorting works on everything arriving in a busy inbox. Both run on the same AI classification step, so the other can be added later.

Request routing · Inbox sorting
Request routingInbox sorting
What comes inRequests from web forms and email: enquiries, complaints, support requestsEverything arriving in a busy inbox
Main jobClassify each request, answer the standard ones and send the rest to the right teamCategorise and prioritise mail, reply to specific types automatically and set follow-up reminders
Where results goYour CRM or project management toolYour inbox, with categories, priorities and reminders

Which systems deliver it?

Inbox and request triage is delivered by AI automations, built on tools such as Make.com, n8n or Claude routines, which read, classify, answer and route each message. Requests that arrive by chat are handled by an AI chat agent instead, which sorts and routes chat enquiries as part of customer support.

System · Trigger · What it does · Package note
SystemTriggerWhat it doesPackage note
AI AutomationsA new email or web form submissionClassifies each message, answers standard requests, routes the rest with a summary, prioritises and sets remindersStart with request routing or inbox sorting; add the other on the same classification step
AI Chat AgentsA chat enquiry on your website or messaging channelsAnswers, sorts and routes chat enquiries, escalating with the context attachedPart of a customer support build

Where is it used?

Inbox triage suits any team where requests arrive by email and forms faster than someone can sort them. Professional services firms use it on shared inboxes, online shops on customer service email, real estate branches to separate sales, lettings and maintenance requests, and education providers on admissions inboxes.

Same job, their words

The shared practice inbox. New enquiries, client questions, invoices and promotions are separated, new-client enquiries go to whoever handles intake, and routine document requests get an answer from your templates.

What should you know before you start?

Inbox triage follows your rules. We agree the categories, the routing rules and which replies can go out automatically during discovery, and anything outside those rules goes to a person. Most teams switch on automatic replies for a few common request types first, then add more once they trust the output.

  • The rules are yours. Categories, routing and approved auto-replies are agreed with you, and anything outside them goes to a person.
  • Automatic replies can start small. A few common request types first, more once you trust the output.
  • Chat is covered separately. If a chat agent handles your customer support, it already sorts and routes chat enquiries. This covers email and web forms.
  • Sales leads have their own route. New leads from forms, email and social DMs can be pulled into one CRM through lead capture & routing.

How would we build it for you?

We haven't published an inbox triage case study yet. Here's how a build would run: we look at a sample of what arrives in your inbox and forms, agree the categories, routing rules and approved replies with you, connect your inbox to your CRM or project management tool, then test it on real messages before automatic replies are switched on.

  1. Email receivedshared inbox
  2. Classifiedsupport request
  3. Priority seturgent
  4. Summary writtentwo lines
  5. Routed to ownerCRM task
  6. Reminder setreply due

Frequently asked questions

Questions

Answer

Will the AI send replies without us checking?

Only the replies you've approved. During discovery, we agree which request types can get an automatic answer from your templates and knowledge base. Everything else is routed to a person with a summary, not answered. Most teams start with a few common requests, such as opening hours or document requests, and switch on more once they trust the output.

Stop sorting the inbox by hand

Free · 30 min · No commitment

Thirty minutes on how your business runs today. You leave with a straight read on where AI pays off, and where it doesn't.