From email threads to a reviewable intake in Litify.
We built an intake workflow that turns incoming email and document content into structured Salesforce/Litify records, giving the intake team a prepared record to review and correct.
Workflow overview
From correspondence to a reviewable intake.
Microsoft 365
Messages and documents supply the intake context.
AI extraction
Relevant information is extracted for the record.
Salesforce / Litify
The workflow creates an intake in the existing system.
Team review
People review the record and decide the next action.
The operating problem.
Corporate and litigation intake information arrived in long email chains and attachments. Staff had to identify the client, matter details and relevant parties, then map that information into the fields and linked records used by Salesforce and Litify.
What we built.
A connected workflow for core intake creation. It retrieves incoming material, structures the information, maps it to the destination system and creates an intake for the team to review.
The implementation was deployed to the client's Salesforce/Litify organization for testing. The client's team tested the workflow and provided feedback on the generated records and review process.
From source material to team review.
-
Receive the source material
Microsoft Graph retrieves intake messages from a dedicated Microsoft 365 inbox. The original email and attachments are preserved in AWS S3.
-
Extract and organize the information
The parser reads the message and supported documents, then structures client, matter and party information. Relevant attachment details are combined with the email context.
-
Match the destination system
The connector maps information to the Litify schema. Salesforce lookups resolve identifiers and allowed field values. Warnings and processing status are recorded for investigation.
-
Create the intake record
The system creates a Litify intake and associated records supporting party and conflict review.
-
People review and advance
The intake team reviews the created record, corrects the generated content and determines how the intake progresses.
What keeps the workflow inspectable.
Record creation is one step in intake. People retain responsibility for reviewing the information and deciding what happens next.
- Retained source material The original email and documents are stored separately from extracted information.
- Visible processing status Processing records connect an intake to its source and show completion or failure.
- Identifiable generated content Designated generated fields are marked for the reviewer.
- Review after creation Application rules map data into the destination system. People review incomplete or defaulted information and make corrections.
Built and deployed for client testing.
The workflow was deployed to the client’s Salesforce/Litify organization for testing. The intake team could inspect the generated records, correct the information and provide feedback on the review process.
How to judge a workflow like this
Track correction effort, failed processing and time to a completed intake. A record created successfully may still need substantial review. Those measures help determine which inputs to automate next and which should continue to receive closer attention.
The same questions show up in other operations.
When an order, request or application begins in an inbox, the engineering questions are familiar: what information is present, where it belongs, what can be automated and who resolves the exceptions. The workflow and controls need to fit each business's systems and responsibilities.
How we build workflows with human reviewHave a workflow like this?
Show us a representative input, the destination system and the decisions people need to retain.