Stale lead reassignment board for your Follow Up Boss team

By General Input

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.

Integrations

  • Follow Up Boss
  • Slack Bot

Type

App

Categories

  • Sales
  • Operations

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.

Related prompts

Explore more prompts
A brand asset library your marketing team actually searchesTurn Mailjet email clicks into ranked HubSpot follow-upsClean out the Looker dashboards and Looks nobody opensLiveKit live operations console for room moderationWake up dormant Keap leads with a researched reasonLiveChat coverage board for planning next week's shiftsPhone routing control panel for LiveKit voice agentsLinkedIn Ads budget pacing dashboard for every client accountGive your team Looker numbers without buying more seatsPause marketing emails to escalated customers, then restore them