Partners and API / Inbound email
The mailbox becomes an intake lane
Documents and notices arriving by email are read into the platform, extracted, and presented as a draft for review — rather than living in somebody’s inbox.
A claim document sitting in a personal mailbox is invisible to the operation. That is the single most common way information fails to reach a file.
Forward us a real emailWhat happens to documents that arrive by email today?
In most operations, they sit in an individual’s mailbox until that person forwards or uploads them — which means the file is incomplete for as long as that person is busy, on leave, or unaware it mattered. Inbound email removes the human relay.
Relay removed
From mailbox to file
- 01
Mail arrives at the platform
A monitored address receives notices and documents directly, so arrival does not depend on anybody forwarding anything.
- 02
Content is read and matched
Attachments and body text are extracted; references are matched against existing claims where they exist.
- 03
A draft is presented
New notices become a draft intake for review. Documents for existing claims are proposed against the matched file.
- 04
It lands on the file
On confirmation the document is attached to the claim with its provenance, rather than existing as a forwarded copy of a copy.
The failure it removes
Where emailed documents go wrong
Every row is a routine failure in operations that rely on people forwarding mail into the system.
Document sits unforwarded
Arrival is not gated on a person noticing
Adjuster on leave
The lane does not depend on one mailbox owner
Attached to the wrong claim
References are matched, and the match is confirmed by a reviewer
No record of when it arrived
Arrival time is recorded with the document
Personal data in a mail archive
The document lives on the encrypted file, not in an inbox
Email is still email
This lane makes a messy channel usable. It does not make it a good protocol.
Matching can be wrong
A reviewer confirms the claim match. Automatic attachment without review would put documents on the wrong files at scale.
Spam and noise arrive too
A monitored address receives everything sent to it. Filtering is configuration work at setup.
Not a substitute for a portal
For customers, the upload route lands directly on the file and is better. Email exists because the outside world uses it anyway.