Overview
After every call, Lexidesk reads the transcript and generates a summary that appears on the lead record.
The default summary splits into two sections: Overview and Client Objectives. That works well for most firms out of the box.
The Summary Prompt lets you replace the default format with whatever structure your team actually needs. You'll find it in Agents → Configure → Analysis Prompts → Summary Prompt.
When to use a custom summary
Leave the default in place unless your team is regularly digging into the transcript to find specific details that aren't surfacing automatically.
The most common reason firms customise the summary is to pull out information the AI collects on calls but doesn't display in a dedicated field anywhere else in Lexidesk.
Things like:
Preferred callback time
Lead source ("How did you hear about us?")
Date of birth
Incident date or date of offence
Opposing party name
Whether the caller has legal aid or insurance
Case file or reference numbers
If your intake team processes a lot of leads and has to scroll or listen back to find the same two or three details every time, that's the signal to write a custom summary.
How it works
The AI reads the full call transcript alongside your prompt and produces a summary in exactly the format you describe. You're not filtering or scoring anything. You're just telling it how to present what was said.
Think of it as briefing a paralegal on how to write up every call so the next person who reads the note can act on it immediately.
How to write a good summary prompt
The mental model
The best prompts answer three questions before you write a single line:
Who is reading this? An attorney scanning between meetings needs something different from a receptionist deciding call-back order.
What do they need to act? Not everything said on the call, the specific facts that drive the next decision.
What should stay out? Filler, assumptions, anything that slows the read.
Use sections, not just fields
A flat list of fields works for simple cases. Once you have four or more things to surface, named sections scan faster and the AI produces more consistent output.
Good section patterns for law firms:
Matter overview — what kind of case, for whom, key status facts
Key facts — eligibility-relevant details, dates, relationships, prior filings
Urgency — court dates, deadlines, expiring documents. If none, say so explicitly
Client objectives — what they want from the firm
Red flags — anything that needs checking before the consultation. If none, say so
You don't need all of these. Pick the ones that map to decisions your team actually makes.
Conditional sections earn their place
Some sections only apply sometimes. Telling the AI to write "Not mentioned" when a section is empty is better than omitting the section entirely. It confirms the AI looked, not that it missed it.
Bake in rules, not just structure
The most useful prompts include a short rules block alongside the format:
Rules:
- Use only what the client said. No assumptions or filler.
- Do not include contact details, these are stored separately.
- If a section has nothing relevant, write: Not mentioned.
- Keep the whole summary short enough to scan in under 30 seconds.
This is especially valuable when multiple people at a firm use Lexidesk and you want summaries to look consistent regardless of how the call went.
Only ask for what's in the call
The AI works from the transcript only. If your agent doesn't collect something, don't put it in the summary prompt. A field your agent never asks about will always come back "Not mentioned", which adds noise, not value.
If a detail matters to your team, make sure your agent actually collects it on calls first.
Example: a family law firm
This firm's intake team needs to quickly assess each lead before calling back. They want a structured card, not a prose overview.
Generate a concise, attorney-ready summary based on what the prospective client shared during the call. Use only what the client said — no assumptions or filler.
### Matter type
- Type of matter (custody, divorce, domestic violence, other)
- Whether the call is for the client themselves or someone else
### Key facts
- Jurisdiction (state the matter is in)
- Children involved and ages if mentioned
- Opposing party name if mentioned
- Any court cases or prior legal proceedings mentioned
### Urgency
- Any court dates, hearings, or safety concerns mentioned
- If none: Not mentioned
### Client objectives
- What the caller wants to achieve
- Any specific concerns they raised
Rules:
- Do not include contact details, they arestored separately
- If a section has nothing relevant, write: Not mentioned
- Keep it short enough to scan in under 30 seconds
FAQs
Do I have to write a custom summary prompt?
No. The default summary (Overview + Client Objectives) works well for most firms. Only write a custom one if your team is consistently looking for details the default doesn't surface.
Will the AI make up details that weren't in the call?
No, provided your prompt tells it not to. Including a rules block with "use only what the client said" keeps the AI from filling gaps with assumptions. Without that instruction, some inference can creep in.
Can I mix prose sections with structured fields?
Yes. You can ask for a paragraph overview followed by specific fields, or specific fields followed by a free-text notes section. The AI follows whatever format you describe.
Does the summary replace the full transcript?
No. The full transcript is always available on the lead record. The summary sits above it as a quick-read version. Your team can always scroll down to the transcript if they need the full detail.
Can I use this to replace my CRM fields?
The summary is a display tool, not a sync mechanism. It shows the information on the lead record inside Lexidesk. If you need specific data points to flow into Clio, Lawmatics, HubSpot, or Salesforce as structured fields, that's handled by your CRM integration separately.