All workflows

Claude workflow

Follow up on stalled deals with Claude

Find the open deals that have gone quiet and get a short, specific follow-up for each, written from the last real conversation.

Oksana Tkachenko
Oksana T.
Writer

What does this workflow do?

Deals rarely die in a meeting. They go quiet. This workflow lists open deals with no contact for two weeks, reads the latest activity and email for each, and drafts a follow-up in your style. You see every draft in one table and send only the ones you approve.

The prompt

Copy it into a chat with Lumenbase turned on. Fields in square brackets are yours to fill in.

Prompt
Use the Lumenbase connector.
1. Call fetch_quiet_deals with quiet_days 14 and limit 5, sorted by amount.
2. For each deal, read its recent activities and the latest email thread with the main contact (fetch_activities, fetch_mail_conversations, fetch_mail_thread).
3. Call fetch_writing_style once with channel "email".
4. For each deal, write a short follow-up in that style. Refer to something real from the last conversation. Never invent facts, prices or dates.
5. Show me every draft in a table: deal, contact, last touch, draft. Do not send anything yet.
6. Send only the drafts I approve, with send_email, as a reply in the existing thread when there is one.

Run it as /follow_up_stalled_deals in Claude.

Fields you can fill in

  • quiet_days (optional): Days without contact before a deal counts as stalled. Default 14.
  • limit (optional): How many deals to work through. Default 5.

Tools it calls

In the order the prompt uses them.

  1. List quiet or stalled deals · Read

    Find open deals with no recent communication touch (email, call, meeting, LinkedIn message).

  2. List activities · Read

    Fetch activities from the CRM with optional filters.

  3. List email conversations · Read

    List CRM-linked email conversations from the user's synced mailbox.

  4. Read email thread · Read

    Read a bounded email thread page, then follow cursor for older messages or message_id/body_offset/body_revision for omitted body text.

  5. Read your learned writing style · Read

    Read the logged-in user's analyzed writing style for the current workspace, learned only from mail they sent in this workspace: core tone description, channel notes, and up to five real examples per channel (only examples the user may already see through the mail tools).

  6. Send email · Send

    Draft and send an email to a contact from the user's connected mailbox (Gmail, Outlook, or SMTP).

What to check before you approve

  • Each draft refers to something that really happened in the last conversation.
  • No price, date or promise appears that is not in the record.
  • Replies go into the existing email thread, to the right contact.

Make it recurring

This job comes back every week. Ask Claude to turn it into a Routine and it runs in Lumenbase on its own schedule, as a draft you review and switch on.

Turn a workflow into a Routine

Common questions

An open deal with no email, call, meeting or LinkedIn message for 14 days. Change quiet_days to use another threshold.

No. The prompt shows every draft first and sends only the ones you approve.

Sources and scope

The prompt and its tool list come from the Lumenbase MCP workflow catalog, the same list the connector serves.

Claude is a trademark of Anthropic. ChatGPT is a trademark of OpenAI. Cursor is a trademark of Anysphere. Lumenbase is not affiliated with, sponsored by or endorsed by these companies.

Keep exploring

Claude workflows for client salesLumenbase for ClaudeIs it safe to connect Claude to your CRM?

Try the full workspace free for 30 days. No credit card required.