> ## Documentation Index
> Fetch the complete documentation index at: https://klipy.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# How do I revive a stalled deal?

> Ask Claude to find deals that went quiet, read each one's history, and draft a personal re-engagement note you review and send.

Your pipeline has deals that were promising a few weeks ago and then just stopped — a follow-up slipped, and neither side picked it back up. Reviving them properly means re-reading each history so the note does not sound like a canned "just checking in." Connect Claude to Klipy and it reads each deal's real history and drafts a tailored re-open for every one.

## Example prompt

Copy this into Claude once it is connected to Klipy:

```text theme={null}
Look at my sales pipeline, find the deals with no recent activity, read
each one's history, and draft a short, personal re-engagement email for
each — referencing where we actually left off.
```

## What happens

**1. Claude resolves your pipeline**

Deals live inside a pipeline, so Claude calls `list_pipelines` first to get a valid pipeline id and its stages.

**2. It lists the deals**

Claude calls `list_crm_records` for the `deal` type in that pipeline to pull the deals it can work through, then judges from each timeline which ones have gone quiet.

**3. It reads each deal's history**

For each deal, Claude calls `get_record_timeline` to read the interactions and open items — so every draft references the real last exchange, not a template.

**4. It drafts a note per deal**

Claude calls `draft_email_message` for each deal, queuing a personal re-engagement email. Nothing sends — each draft waits for your review.

**5. You review and send**

Open each draft, edit if you want, and approve the ones you want to send through Klipy's gated handshake.

Tokens are consumed only when you accept a send — listing, reading histories, and drafting are free.

## Good to know

* **"Went quiet" is judged from the timeline, not a status field.** There is no built-in "stalled" flag. Claude infers which deals are cold by reading recent activity per deal, so it works best when you point it at a specific pipeline.
* **Drafting the notes needs a connected email account.** `draft_email_message` requires a connected mailbox and a recipient who already exists as a CRM contact. Without a mailbox it returns a blocked status with guidance.
* **Point Claude at the right pipeline.** Listing deals requires a pipeline id. If you run several pipelines, name the one you mean so Claude scopes to it.

## Related

> [card] [Pipeline forecast](https://klipy.ai/docs/guides/mcp/use-cases/pipeline-forecast.md)
>
> See the whole pipeline weighted into a best/likely/worst forecast.

> [card] [Follow-up emails](https://klipy.ai/docs/guides/mcp/use-cases/follow-up-emails.md)
>
> Draft a follow-up while a fresh conversation is still warm.

> [card] [Tool reference](https://klipy.ai/docs/guides/mcp/tools.md)
>
> Every tool Claude can call, grouped by scope.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.