# Weekly stale pipeline report that tells reps what to say

> Every Monday at 8am, find the deals that have gone quiet, draft a specific re-engagement message for each one, and post them ranked by value.

- Workflow type: agent
- Services: LeadConnector, Slack Bot
- Categories: Sales
- Published: 2026-08-07

## What it does

- Scans your whole open pipeline every Monday morning and keeps only the deals with no update in the last 14 days
- Reads each deal's contact record and writes a short, specific re-engagement message that references the stage, the deal value, and how long it has been quiet
- Creates a follow-up task on each contact assigned to the rep who owns the deal, so the work lands in their queue even if nobody reads the digest
- Posts one Slack summary ranked by deal value with every drafted message inline, ready to copy, tweak, and send

## What you'll need

- A LeadConnector (GoHighLevel) account with opportunities and pipelines already in use
- A Slack workspace and a channel where the weekly digest should land
- Deal owners assigned on your opportunities, so follow-up tasks reach the right rep

## Prompt

Every Monday at 8am, run a stale pipeline review for my sales team and post one digest in Slack. The goal is not just to list which deals are rotting, it is to tell each rep exactly what to say to revive them.

Start in LeadConnector. Use Search Opportunities to pull every open opportunity across the account, paging through all results. Use Get Pipelines to load the pipelines and their stages so you can resolve pipeline and stage IDs into readable names. Then keep only the opportunities with no update in the last 14 days, and record how many days each one has been quiet.

For each stale opportunity, use Get Contact to load the associated contact, including their name, contact details, tags, and custom fields. Combine that with the opportunity record itself: the stage name, the monetary value, the assigned owner, and the date of the last update.

Now draft a short re-engagement message for each deal, two to four sentences, written so the rep can send it directly. Every message must be specific to that deal. Reference the stage the deal is sitting in, the deal value, and how long it has been quiet, and use anything in the contact record that gives a natural reason to reach out. No generic check-in copy, and no two messages that read the same. Vary the angle by stage: a deal that never got past the first conversation needs a different opener than one that stalled after a proposal was sent.

Create a follow-up task on each contact with Create Contact Task. Assign it to the owner of the opportunity, set a due date within the next few days, and put the drafted message and the deal context in the task body so the rep can act on it without leaving LeadConnector. If an opportunity has no owner assigned, still create the task and flag that deal as unassigned in the digest.

Finally, post a single message into my sales channel using the Slack Bot Send a Message action. Rank the deals by value, highest first. For each deal include the contact name, the deal value, the pipeline and stage name, how many days it has been quiet, the owner, and the full drafted message inline as a quote or code block so reps can copy it, tweak it, and send it. Open with a one line headline giving the number of stale deals and the total value at risk. If there are more than 15 stale deals, include the full drafted copy for the top 15 by value and list the remainder compactly at the bottom with name, value, and days quiet. If nothing is stale, post a short all clear so the team knows the check ran.

One critical rule: never message, email, or text any contact automatically. This workflow drafts and assigns only. Reviving a cold deal is a judgement call that belongs to the rep, so every message must wait for a human to review, edit, and send it.

## How to customize

- Change the quiet period from 14 days to whatever counts as stale for your sales cycle
- Move the schedule or the destination, for example a different day and time or a private channel for sales leadership
- Narrow the scope to a single pipeline, a minimum deal value, or one rep's deals

## FAQ

### Does this message my leads automatically?

No. It only drafts. Every message waits for a rep to review, edit, and send it, because deciding how to revive a cold deal is a judgement call that belongs to the person who owns the relationship.

### What counts as a stale deal?

Any open opportunity with no update in the last 14 days. You can raise or lower that threshold to match your sales cycle, for example 7 days for fast transactional deals or 30 days for long enterprise cycles.

### Will this work if we run several pipelines?

Yes. It looks across every open opportunity and labels each deal with its pipeline and stage name, so a proposal that stalled reads differently from a brand new lead. You can also restrict it to one pipeline.

### Who gets the follow-up task?

The rep who owns the opportunity. If a deal has no owner assigned, the task is still created and the deal is flagged as unassigned in the digest so a manager can pick it up.

### What happens on a week when nothing is stale?

It posts a short all clear message, so the team knows the check actually ran rather than wondering if it failed silently.

Use this prompt in General Input: https://www.generalinput.com/prompts/weekly-stale-pipeline-report-that-tells-reps-what-to-say