Start a conversation A matter platform needs structured records. Incoming correspondence arrives as threads, documents and references to related parties. Xivic connects those inputs to intake records, with source context and unresolved questions available to the people responsible for review.
Relevant client work
Email and document content becomes a prepared Salesforce/Litify intake. The team reviews and corrects the record before deciding what happens next.
Explore the Legal intake workMicrosoft 365 to Salesforce/Litify. Deployed for client testing.
A potential matter can arrive as a long email chain with several attachments and references to people who need separate records. An intake team must identify what is relevant, map it to the fields the matter platform expects and resolve missing or ambiguous details. We can connect those steps so the team reviews a prepared intake with its source context available. The design needs to distinguish extracted facts, generated text and unresolved questions, while leaving matter acceptance, conflicts and other professional decisions with the people responsible for them.
Start with one intake type and approved sample correspondence. Include a straightforward request, a duplicate contact, contradictory details and an attachment the system cannot read. Reviewers should be able to trace each populated field to its source, correct it and leave unresolved questions visible. Matter acceptance and conflicts review stay in the existing professional review process.
Map client, matter and party details from incoming material into the fields the intake system requires. Keep source facts, generated text and missing information distinguishable.
Connect approved inboxes, attachments, document storage and matter records. Define record matching, access and what happens when required details cannot be found.
Give reviewers the information and status they need to correct an intake. Keep matter acceptance, conflicts and other professional decisions with the responsible people.
Decide which intake fields can be prepared, which need confirmation and how a reviewer returns to the original message or attachment. Make corrections part of the workflow so staff do not have to maintain a second set of records outside the matter platform.
Name the approved inboxes, access roles, retention requirements and system owner. Define a manual route for unreadable material or a failed update, and test that route with the intake team before expanding the volume.
Bring an approved, anonymized email chain, the required intake fields and the review steps. We will map what can be prepared automatically and what needs a person's review.