Email-to-File Intake Guide
A practical approach to claim intake by email: what to standardize, what to automate, and how to keep an assignment from sitting unread in one person's mailbox.
The intake problem
For most claim operations, work arrives as email. A carrier sends an assignment, a public adjuster forwards a demand, a contractor refers a homeowner. The message contains everything needed to open a file — and then it sits in a mailbox, where it is visible to exactly one person and countable by nobody.
Every downstream problem in a claim operation traces back to this moment. If the file does not exist, the task does not exist, the deadline is not tracked, and the assignment is being managed by whoever happens to remember it.
Step 1 — Move intake off personal mailboxes
The single highest-value change most firms can make is to stop routing assignments to individuals. Use a shared, monitored address for intake.
- One address per intake channel where the channels genuinely differ — carrier assignments and homeowner enquiries are not the same work
- Ask senders to use it, and redirect the ones who don't
- Never let intake depend on one person being at their desk
Step 2 — Decide what identifies a file
Automation of any kind depends on being able to answer one question from a message: which file is this? Decide the answer deliberately.
- Claim number is the strongest identifier, when the sender includes it
- Sender domain reliably identifies the client, even when the claim number is missing
- Insured name plus property address identifies the file when the claim number has not been issued yet
- Subject-line conventions help, but only for senders you can influence
Step 3 — Define what happens on arrival
Write down the intake sequence before automating any of it. If the sequence is not clear enough to write down, it is not clear enough to automate.
- Identify the client from the sender
- Match the message to an existing claim, or open a new one
- Capture the attachments onto the file's documents
- Store the message itself on the file, not just in the mailbox
- Route the file into the correct workflow for that client type
- Create the opening task and assign an owner
- Set the first deadline
Step 4 — Handle the messages that don't match
Some percentage of intake will always be ambiguous: a reply with no claim number, a forward from an unfamiliar address, a message that could belong to two open files. Plan for these rather than treating them as failures.
- Route unmatched messages to a review queue, never to nowhere
- Give the queue an owner and a daily check
- Track how often matching fails, and why — it will tell you which sender conventions to fix
Step 5 — Keep the thread with the file
Intake is not a one-time event. Replies, supplements, revised estimates, and scheduling messages all arrive against a file that already exists. If only the first message is captured, the record is incomplete in exactly the way that matters during a dispute.
The standard to hold yourself to: someone who opens the file six months from now should be able to read the complete correspondence without asking anyone for a mailbox export.
What good intake looks like
- No assignment is known only to one person
- Time from arrival to file creation is measured in minutes, not days
- Every attachment is on the file it belongs to
- Every file has an owner and a next action from the moment it opens
- Nobody creates a folder by hand