> For the complete documentation index, see [llms.txt](https://themochi-app.gitbook.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://themochi-app.gitbook.io/documentation/module-4-ai-setup-and-intelligence/lead-summary.md).

# Lead Summary

## Lead Summary: AI-Generated Conversation Insights

**What it is** — Lead Summary reads a lead's full conversation and instantly surfaces the pain points, desires, key quotes, and red flags buried in it, so whoever picks up the conversation next can personalize a reply without re-reading the whole thread.

**Who can use it** — Anyone who can see a lead's conversation can view their summary. Customizing the underlying prompt is a `Settings > Intelligence` change, and like the rest of Settings, it's expected to be a **Creator/Manager** action. Available on **web and iOS**.

**Before you start** — A conversation needs some back-and-forth before there's anything meaningful to summarize. On iOS, the summary card only appears once AI is enabled for your org.

### How to view a lead's summary

**Web:**

1. Open the lead's conversation in the Inbox.
2. Click **Summarize** to generate or refresh their summary. It appears alongside the conversation.

**iOS:**

1. Open the lead's profile.
2. Look for the summary card (requires AI enabled for your org).

### What the summary includes

By default, Mochi surfaces:

* **Pain points** — what's actually bothering this lead.
* **Desires** — the outcome they're chasing.
* **Key quotes** — the lead's own words worth remembering.
* **Red flags** — anything that should make a setter or closer cautious.

Use it before replying to any conversation — including one that's gone cold for weeks — to personalize your message instead of sending something generic.

### Customize the summary prompt

The default fields work well out of the box, but you can extend them.

1. Go to `Settings > Intelligence > Lead Summary`.
2. Edit the prompt.
3. Save. This applies **organization-wide, for every setter** — it isn't a per-person setting.

Common customizations:

* Add a budget-qualification field.
* Flag a specific objection type you want surfaced explicitly.
* Pull out a specific detail relevant to your offer (for example, a specific skill a lead wants to monetize).
* Change the output format to match how your team likes to scan it.

Write the custom prompt the same way you'd write an AI tag prompt or a spam filter prompt: plain language, specific about what you want extracted.

### Why this matters for handoffs

A summary is one of the fastest ways to hand a conversation from a setter to a closer. Instead of the closer scrolling back through the whole thread before a call, the setter can copy the summary text and send it over, giving the closer a fast, accurate read on what's about to happen on the call.

### Tips

* Click Summarize before every reply, not just on new leads — it's just as useful for reviving a conversation that's gone quiet.
* If you're extending the prompt, test it on a few different leads before rolling it out. A field that reads well on one conversation can come back empty on another if the prompt isn't specific enough.
* Pair Lead Summary with AI Tags. A well-tagged inbox plus a sharp summary means a setter can triage and personalize in seconds.

### Common mistakes & fixes

| Mistake                                                           | Fix                                                                                                   |
| ----------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- |
| Skipping the summary on "boring" or old conversations             | Run it anyway — cold leads often have red flags or quotes worth revisiting before a follow-up.        |
| Writing a summary-prompt edit that's too vague                    | Be as specific as you would with an AI tag prompt — name the exact field and what should populate it. |
| Assuming a summary prompt edit is per-setter                      | It's organization-wide — one edit changes what every setter sees.                                     |
| Not re-running Summarize after a long new stretch of conversation | Refresh it — an old summary won't reflect messages sent since it was last generated.                  |

### Limits & good to know

* The custom prompt applies to the whole organization — there's no per-setter version.
* iOS shows the summary card only once AI is enabled for your org.
* A summary is only as good as the conversation behind it — very short threads won't produce much.

**Related:** Set Up Your AI: Setter Playbook & Creator DNA, AI Tags, Spam Filter. Also see **The Inbox** and **Lead Profiles & Timeline** (Module 03).