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.
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.
What does this prompt do?
- 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 do I need to use this?
- 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
How can I customize it?
- 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
FAQs
Does this message my leads automatically?
What counts as a stale deal?
Will this work if we run several pipelines?
Who gets the follow-up task?
What happens on a week when nothing is stale?
Related templates
When someone leaves, we check which shared passwords they used in their final months and post a ranked rotation list to your security channel.
Every Monday, check every S3 bucket for public exposure, missing encryption and weak backup settings, then get the risks ranked in Slack.
Twice every weekday, the conversations from your social inbox land on the right HubSpot contact timelines, with a Slack recap for sales.
Every morning, find the addresses that hard bounced or filed a spam complaint, update the matching HubSpot contacts, and post a short Slack recap.
Every weekday at 4pm, spot the threads that went quiet, stage a ready-to-send nudge in your mailbox, and get a ranked Slack recap.
When you merge a fix in GitHub, this agent checks the matching dead-letter queue, replays the failed messages, and reports back on the pull request and in Slack.
Stop losing deals to silence.
Give every rep a prioritised list of the deals that went quiet and a ready-to-send message for each one, every Monday morning.