Email triage automation for FYI
How email triage automation sorts a shared inbox by type and urgency, with staff keeping control of every reply sent.
Updated 2026-02-16
Email triage automation with FYI
Firms that keep their files in FYI still receive much of their work by email, usually in a shared mailbox that sits outside the platform. For accounting firms, financial planners, mortgage brokers and legal services offices, one morning's inbox can hold a new enquiry, a lender notice, a court letter and a supplier invoice. An email triage build reads each message as it arrives, applies agreed categories and urgency labels, and routes it to the person who should see it first. Where a matter already has a record in FYI, staff can then open the related file with the right context. The first release leaves outgoing replies with the team, so the owner keeps control of what is sent. Ideas grow from there, such as a morning digest of what came in overnight or a flag on anything from a lender.
How it works
Agree the message categories with the owner, such as new enquiry, invoice, lender correspondence or court letter, and name the staff member who receives each one.
Connect the shared mailbox through the mail provider's standard interface, using a workflow tool such as Power Automate or Zapier, so incoming messages are read as they arrive.
Send each message's sender, subject line and any stated deadline to Claude, which returns a category and an urgency label for the workflow to record.
Route each labelled message to its folder or team queue, and keep an audit log of the label and rule applied to every message.
Compile a daily summary of open urgent messages for the owner, so that flagged items are visible without anyone opening the whole inbox.
Where a message concerns an existing matter, have staff check the related record in FYI, and test what the connected tool can read before go-live.
Frequently asked questions
- Which tools sit between an email triage automation and FYI?
- The mailbox side usually runs through a workflow tool such as Power Automate or Zapier, using the mail provider's standard interface. Claude can then return a category and urgency label for each message. Staff link a message to its matter record by hand, and the label gives them a head start, so the person who picks it up knows straight away what it is and how urgent it looks.
- Is an email triage automation right for a small FYI team?
- Yes, provided the inbox volume justifies the setup and the team agrees on categories before anything is built. A small team with one shared mailbox often gains most from a daily summary of urgent messages, since it shows what needs attention without anyone reading every item first. If volume is low, manual filing rules inside the mail client may be enough. The owner should decide that before committing to the build.
- Does an email triage automation change how my team uses FYI?
- No, day-to-day work in FYI stays as it is. Staff keep filing, tracking tasks and holding correspondence in FYI as they do now, because the first release sorts mail rather than changing records. What changes is that labelled messages reach the right person sooner, and the audit log shows which rule sorted each one. Your team also gets to choose how a matter reference from an email is recorded in FYI, a small decision that makes everyday work smoother.
- How do I measure an email triage automation on FYI?
- Begin by recording how long urgent messages wait before a person opens them, using the audit log alongside each message's arrival time. Compare that with the counts in the daily summary to check whether urgent items are being caught. Ask staff to note every label they correct, since those corrections show where the rules need work. Set no targets until that baseline has been recorded.
- What does an email triage automation read from FYI?
- The first release reads the mailbox and leaves FYI untouched, so it needs no access to client files to sort messages. Sender, subject line and any stated deadline are what the classifier uses. Where a firm later wants the tool to read records or documents from FYI, it should first confirm what export or connection is permitted and test what a connected tool can see against the firm's access rules.
Related
read these nextUp a level
More with FYI
- Client onboarding automation with FYI for staff-reviewed intake
- Contract generation automation with FYI
- Document filing automation with FYI
- Document Q&A assistant with FYI: how the build works
- AI adoption for FYI: training and rollout for professional services teams
- AI strategy for FYI users in professional services firms
- Custom development for FYI firms
- Product idea for FYI users: scoping a first version with AI
- Workflow automation for FYI practice management
