AI intake triage means an AI reads every incoming request, turns it into a well-formed task, and routes it to the right person or agent, so nothing sits in a shared inbox waiting for someone to notice. Done well, it cuts the time between "a customer asked" and "someone is on it". In AlianHub, requests arrive through Email to Task, agents like the Request Sorter and Intake sort and break them down, and anything risky waits for a person in the AI Inbox.
Key takeaways
- The slowest part of most requests is the wait before anyone reads them.
- Triage is sorting, not deciding. AI is good at sorting.
- Route to agents only when the work has a clear shape.
- Keep assignment and priority changes behind an approval.
- Every triaged request should end up as a task with an owner.
What intake triage involves
Intake is everything that happens between a request arriving and work starting. For most teams, it looks like this:
- A request arrives by email, form, chat or a colleague's message.
- Someone reads it and works out what it is.
- They decide which project and list it belongs to.
- They set priority and pick an owner.
- They break it into steps or ask clarifying questions.
Steps 2, 3 and 5 are reading and sorting. That is exactly what AI handles well. Step 4 often needs judgement, so it is the step to keep human, or at least approved.
The AlianHub features behind AI intake triage
AlianHub is a free, open-source, self-hosted project management platform with AI agents built in. Several features combine for intake.
| Feature | What it does in triage |
|---|---|
| Email to Task | A unique address per project turns emails into tasks |
| Request Sorter agent | Sorts new requests; shown in a Front Desk role |
| Intake skill (brief.parse) | Reads a brief and proposes subtasks with estimates and open questions |
| Router | Proposes an agent per task and refuses those that need a person |
| Automations | Rules such as raising priority for matching tasks |
| AI Inbox | Holds wider changes until a person approves |
Email to Task
Each project can have its own Email to Task address. Customer emails become tasks automatically, so they are visible and trackable from the first minute. See integrations.
Intake: brief to breakdown
The Intake skill reads a task brief and proposes the breakdown: subtasks with estimates, plus the open questions. It is rated low risk, and you can run it as a dry run that shows what it would do with nothing written.
The router
Select several tasks and the router proposes an agent for each, and refuses those that need a person. Tasks with no obvious shape are not offered to an agent until someone gives them a brief.
Good triage knows when to say "this one needs a human".
How to do this in AlianHub
- Turn on Email to Task for the project that receives requests, and share its address.
- Open AI, then the Agents tab, and pick the agent with the Intake skill (brief.parse).
- Set it to L2, so low-risk actions like creating subtasks and commenting with open questions run with Undo, while wider changes wait.
- Run the skill as a dry run on a sample request to check the breakdown. Nothing is written.
- Add a Request Sorter agent and give it a daily action limit and a monthly spend cap.
- Select new tasks and use the router to propose an agent per task. Hand the ones it refuses to a person.
- Check the AI Inbox daily to approve assignments and moves between lists. Every change goes to the audit log.
Tip: Write a one-line brief template for each request type. The router only offers tasks with a clear shape to agents, so a good brief template means more requests get triaged automatically.
A business scenario: a clinic front desk
A clinic's administration team receives appointment changes, document requests and supplier questions by email. Staff checked a shared inbox between other jobs, and some requests waited longer than they should.
With Email to Task, each email becomes a task. A Front Desk Request Sorter proposes the right list for each, the Intake skill breaks bigger requests into steps with open questions, and the router flags anything that needs a person. The team lead approves assignments in the AI Inbox.
The result: requests are visible from the moment they arrive, fewer slip through the cracks, and staff spend their time on patients and replies rather than sorting mail. AlianHub's team packs include a clinic administration blueprint for this kind of team.
What AI triage should never do
Triage agents read a lot and touch a lot of tasks, so limits matter. In AlianHub, some actions do not exist for any agent:
- Delete a task or project.
- Remove a member or change permissions.
- Anything to do with billing.
- Mark a task Done.
These are not switches that can be flipped. Even a stolen token cannot reach them. Read more on the AI controls page.
Handling edge cases
Unclear requests
If a request is too vague to triage, the Intake skill can comment with open questions instead of guessing. The task stays visible until someone answers.
Urgent requests
Use an automation alongside the agent. AlianHub shows rules like "when a task matches project and priority, set priority to High". Starter automations ship switched off, so you turn on only what you need.
Agent declines
An agent can decline an assignment before starting. The status stays, the task returns to its assigner, and nothing is spent.
Measuring whether triage works
You do not need new dashboards. Watch three things:
- How long new tasks sit before they have an owner.
- How many triaged tasks get moved again later.
- How many AI Inbox proposals you decline, and why.
Decline reasons are visible to the agent, so a steady stream of declines is a signal to adjust its skill or scope. For the bigger picture on agents, read AI agents for project management.
FAQ
What is AI intake triage?
It is using AI to read incoming requests, turn them into structured tasks and route them to the right person or agent. It speeds up the step between a request arriving and work starting.
Can AlianHub turn emails into tasks?
Yes. Email to Task gives each project a unique address, and incoming emails become tasks in that project.
Will the triage agent assign work without asking?
Not unless you allow it. Assigning a task and moving between lists are wider changes that wait in the AI Inbox for approval.
What if a request needs a human?
The router refuses tasks that need a person, and tasks with no clear shape are not offered to an agent until someone writes a brief.
Stop letting requests wait
Pick one inbox your team checks too often and turn it into a triaged project. Try the agents in the live demo, read about the AI features, and self-host AlianHub free. Share this with the person who sorts your shared inbox.