Stale lead reassignment board for your Follow Up Boss team

See every Follow Up Boss lead your agents have not called or texted in weeks, then bulk reassign them to someone who will actually work them.

App
Follow Up BossSlack BotSalesOperationsLead EnrichmentAI Reports
PromptCreate

I run a real estate team and I want an app I open for weekly pipeline cleanup: a lead reassignment desk built on Follow Up Boss. Leads sitting untouched in a busy agent's pipeline are my biggest source of wasted ad spend, and today I handle it by filtering the Follow Up Boss people screen and mass reassigning by hand. This is not an email drafting tool and it never contacts the lead directly. The only decision I make on this screen is who owns the lead next, so reassignment, pond routing, and an audit trail are the primary actions.

The main view is a board of stale leads. Pull leads with List People, and treat a lead as stale when there has been no outbound agent contact in the last N days, where N is a control at the top of the board that defaults to 14. Real contact means a logged call or a text message, checked per lead against List Calls and List Text Messages. Emails and automated drips do not count, so never use email activity to compute recency. Load the account's stages with List Stages, and load the team with List Users so every lead can be tied to the agent who owns it right now.

Group the board by the currently assigned agent, one collapsible section per agent, with a lead count and the worst days-since-contact in that agent's section header so I can see at a glance who is hoarding. Each row shows the lead name, lead source, stage, days since last real contact, and total lifetime activity count from their history. Give me filters for lead source and stage, and let me sort by days since contact. Rows have checkboxes, plus a select-all inside each agent group.

With rows selected I take one of two actions from a reassignment dialog. Reassign to a specific agent, chosen from a dropdown populated by List Users, or drop into a lead pond, chosen from a dropdown populated by List Ponds. Both are performed by changing the lead's owner with Update Person. Every move also writes an audit note on the lead with Create Note recording who moved it, the previous owner, the new owner or pond, the timestamp, and the reason I typed into the dialog. Every move also creates a first-touch task for the new owner with Create Task, due tomorrow, naming the lead and the reason it was reassigned.

Bulk reassignment is the core action and I routinely move twenty leads at a time, so build it as a throttled queue instead of firing everything at once. Follow Up Boss caps person updates at 25 per 10 second window and notes at 10 per 10 second window, so pace the writes under those limits, handle 429 responses by backing off and retrying, show a progress bar with counts of completed, remaining, and failed, and let me retry only the failures. Leads that moved successfully drop off the board or get marked as handled.

Every row also has a Draft revival plan button that kicks off a background agent on that single lead. The agent reads the lead's full history using List Notes, List Events, List Calls, and List Text Messages, works out why the lead went cold and what they were originally looking for, then writes a short revival plan: a summary of the history, the likely reason for the stall, what the lead actually wants, and a suggested opening message the new owner can send themselves. The agent saves that plan as a note on the lead with Create Note and creates a follow-up task with Create Task pointing the new owner at the note. The plan stays an in-CRM note for the new owner and is never sent to the lead. Show running, done, and failed state on the row, and let me read the finished plan without leaving the board.

When I finish a cleanup session there is an End session button that posts a summary to our team Slack channel using Slack Bot Send a Message. The summary covers how many leads moved, which agents they came from, which agents or ponds they went to, the staleness threshold I used, and how many revival plans were drafted. Let me pick the channel in the app.

Keep a session log in the app so I can look back at previous cleanups and see what moved and to whom. The user is a team lead or operations manager with visibility across the whole team, so the board is never scoped to just the viewer's own leads.

What does this prompt do?

  • Builds a board of every lead with no real agent contact, meaning a logged call or text rather than an automated email, in the last 14 days, and you can change that window
  • Groups leads by the agent who owns them today so you can see at a glance who is sitting on leads they will never get to
  • Lets you select twenty leads at once and move them to another agent or into a lead pond, writing a note on each record showing who moved it, when, and why
  • Creates a first-touch task due tomorrow for the new owner, and posts a summary of everything that moved to your team Slack channel when you finish

What do I need to use this?

  • A Follow Up Boss account with admin access so you can see and reassign leads across the whole team
  • A Slack workspace and a channel where your team gets pipeline updates
  • Your lead ponds already set up in Follow Up Boss, if you want to route leads into one

How can I customize it?

  • Change the no-contact window from the default of 14 days to whatever your team rule is
  • Filter the board down to specific lead sources or stages before you start moving people
  • Pick which Slack channel gets the end-of-session summary
  • Adjust the wording and due date of the first-touch task the new owner receives

FAQs

Does this send anything to my leads?
No. Nothing goes out to the lead from this app. Reassignment changes who owns the lead inside Follow Up Boss, and the revival plan is saved as a note on the lead record for the new owner to read. Any actual outreach is still sent by the agent.
What counts as contact?
A logged phone call or a text message from an agent. Automated drip emails do not count, which is the whole point: a lead can look busy in the CRM while nobody has actually picked up the phone in a month.
Can I move leads into a lead pond instead of a specific agent?
Yes. The board reads your existing ponds from Follow Up Boss and lets you route selected leads into one, which is what Follow Up Boss itself recommends for leads sitting with agents who are too busy to prospect them.
How many leads can I reassign at once?
As many as you select. Follow Up Boss limits how quickly records can be updated, so the app moves them through a paced queue with a progress bar instead of firing everything at once. Batches of twenty are comfortable.
Will there be a record of who moved what?
Every move writes a note on the lead showing the previous owner, the new owner, the time, and the reason you typed. At the end of a session the app posts a summary of the whole cleanup to your Slack channel.
Do I need to be an admin to use this?
You need Follow Up Boss access that can see and reassign leads across the team. The board is built for a team lead or operations manager, not for an individual agent looking at their own pipeline.

Related templates

Share of voice dashboard for your brand and competitors

See how your brand's news coverage and sentiment stack up against four competitors, then let an assistant write the weekly report for you.

GDELT
Notion
Slack Bot
App
Approval war room for every social post awaiting sign-off

One screen showing every social post waiting on approval, sorted by deadline, so reviewers can approve or reject without leaving the page.

Hootsuite
Slack Bot
App
Turn champion job changes into new pipeline in Attio

Every Monday, find the past champions and closed-won contacts who changed jobs, update Attio, and get the moves worth chasing in Slack.

Boomerang
Attio
Slack Bot
Agentic Task
Collect social post requests and schedule them in Hootsuite

Staff submit what happened, your social manager edits the copy, picks the accounts and puts it on the calendar without a single spreadsheet.

Hootsuite
Slack Bot
General Input Database
App
Voice agent QA review board for your Hume EVI calls

Open one board each morning, see which voice calls went badly, replay the exact moment the caller got frustrated, and file the fix.

Hume
Linear
Slack Bot
App
Clear your Guru verification backlog in one weekly app

A personal queue of every overdue Guru card, sorted by how late it is, with one-click verify, reassign, comment, and an agent that drafts the refresh for you.

Guru
Slack Bot
App

Stop hand filtering your pipeline every Monday.

Get a reassignment board that shows exactly which leads are going cold, who is sitting on them, and lets you move them all in one pass.