Triage
A triage engine for anything that arrives
Triage is not a fixed email inbox. Register any object and its records become triageable items, worked through the same guided flow, whether they arrived as an email, a scanned letter or a record created by an integration
What you can do
Inbound work, understood before anyone opens it
Emails, scanned post and any other inbound record land in one inbox. AI suggests what each item is, pulls out the data and finds the matching record. A person confirms and moves on
Inbound email captured end to end
Mail is received, parsed into body, headers and attachments, and turned into a record automatically.
Any object, not just email
Register an object for triage and choose whether every new record, or only those matching a filter, reaches the inbox.
AI classification
The suggested communication type is pre-selected with a 0 to 100 confidence score.
Per-field extraction
The data-collection form is pre-filled from the item and its attachments, each value with its own confidence. Re-run extraction whenever you like.
Three-stage record matching
An exact match first, then a tidied-up match, then one that forgives the misreads a scanner makes. The last stage is deliberately cautious, so an ambiguous read never guesses.
Automatic sender identification
Exact or pattern rules map fields on the item to fields on your sender objects, so the sender is usually known before anyone looks.
A guided eight-step flow
Sender, type, parent record, child records, data collection, attachments, actions and tasks, save. Steps appear only when relevant.
Attachments become evidence
Files are attached to the right record, named by rule and typed by rule, and virus-scanned. Unscannable files are download-only behind a permission.
Follow-up actions and tasks
Create linked follow-up records as part of triage, so nothing is lost between the inbox and the work.
Inbox ergonomics
Saved filter folders with unread counts, read/unread marking, bulk re-typing, multi-select and a full history per item.
Configurable rendering
Decide what each object’s items look like in the list and in detail: fields, icons, dates, badges and conditional colour.
Feeds your workflows
Triage items are ordinary records, so any workflow trigger can fire on them, and monitor rules can flag items left unread too long.
How it works
Three steps, no tickets to engineering
1
Register what should be triaged
Inbound emails, scanned post, or any object of your own, optionally filtered.
2
Define the types
For each communication type, the form to complete, the records to link, the evidence rules and the follow-up actions.
3
Work the inbox
AI suggests type, data and matching record. The triager confirms, adjusts and saves, and workflows take it from there.
What makes it different
The AI is an accelerant under human control: classification with a confidence score, extraction with per-field confidence, and record matching that degrades gracefully instead of guessing. All of it lands as suggestions a person confirms.
Stronger together
Works With
Communications
Email, SMS, portal messages and campaigns, personalised and audited.
Explore further
See Triage on your kind of work
Bring a process you wish worked better. We will show you how it would be modelled, automated and reported on in Volume, with your objects and your language
Previous
Next
