From email threads to a reviewable intake in Litify.
Xivic built a workflow that turns email and document content into structured Salesforce/Litify records. The intake team receives a prepared record to review, correct and advance.
The information was there. Preparing the record took work.
Corporate and litigation intake 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.
The task was to prepare that information inside the existing system while keeping people responsible for reviewing it and deciding what happens next.
One connected path, with people at the final handoff.
Receive
Microsoft Graph retrieves messages and attachments from a dedicated Microsoft 365 inbox.
Extract
The parser combines the email and supported documents into client, matter and party information.
Create
The connector maps fields to Litify, resolves Salesforce identifiers and allowed values, and creates the intake and associated records for party and conflict review.
Review
The intake team checks the generated record, corrects it and decides how the intake progresses.
Keep the source and the decisions visible.
Successful record creation is only one part of intake. Reviewers need to recognize generated content, inspect the source and investigate processing problems.
The original email and attachments are preserved in AWS S3, separately from the extracted information.
Trace processing to its source
Processing records connect the intake to its input. Completion, failure and warnings are recorded for investigation.
Identify generated content
Designated generated fields are marked for the reviewer.
Correct before advancing
Application rules map data into the destination system. People review incomplete or defaulted information and make corrections.
Client testing informs the next decision.
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.
The same engineering questions apply beyond intake.
When an order, request or application begins in an inbox, the work starts with its source information, destination system and exception owner. The workflow and controls must fit that business’s responsibilities.
Explore AI assistants and automationHave a workflow like this?
Show us a representative input, the destination system and the decisions people need to retain.