Lead reactivation campaigns
Older leads accumulate for many reasons: the buyer delayed a project, the team never reached them, their budget changed, or the original request is no longer relevant. Calling the entire backlog with the original pitch treats stale information as current intent. It can also send representatives into conversations without the source, date, or consent context needed to explain why the business is calling.
A lead reactivation phone agent can make a bounded first pass through records the business has reviewed and approved. It identifies the company and the original inquiry, asks whether the need still exists, refreshes a few qualification fields, and records the next step. The agent should not treat a connected call as renewed interest. Its job is to distinguish active opportunities from closed, deferred, wrong-party, and opt-out records.
A concrete call walkthrough
Imagine Casey requested information about an office move several months ago but did not schedule an estimate. The CRM supplies the original request category and date.
Agent: Hello, may I speak with Casey? I am the AI phone assistant for Northline Moving. You contacted us earlier about a possible office move. Is it all right if I ask whether that project is still active?
Caller: It is, but the move has shifted to November.
Agent: Thank you. I can update the timing. Is the move still for a commercial space, and would you like to schedule an estimate or have a coordinator call you later?
If Casey wants an appointment, the agent can use approved Cal.com or Google Calendar availability and repeat the selected time. If Casey wants a person now, the agent can attempt a cold or attended warm transfer. In warm mode on an eligible production number, it privately briefs the recipient before connecting. If the recipient does not accept, the agent returns to Casey with the configured fallback.
If Casey says the project is complete or asks not to be contacted, the agent records that disposition and ends the workflow. That is different from speed-to-lead callbacks, where the inquiry is new and the main operational concern is a prompt first response. It is also different from customer win-back calls, which concern people who previously bought from the business.
How to set it up on ThunderPhone
Start in the system of record. HubSpot or Salesforce can filter the backlog and provide the original source, request date, known need, owner, last contact, and current suppression status. Google Sheets can support a small reviewed campaign. For a custom database, REST or webhooks can send the limited call context and receive the final disposition.
Write a prompt that assumes the record may be wrong. Include:
- the business identity, AI disclosure, and honest reason for the call;
- how to confirm the intended person without disclosing unnecessary details;
- the minimum questions needed to refresh timing, need, and preferred next step;
- rules for outdated requests, wrong parties, and people who do not remember the inquiry;
- approved scheduling and transfer conditions;
- voicemail wording and retry handling; and
- immediate handling of a request not to continue.
Use a verified imported production number for outbound calls. Demo U.S. numbers are inbound-only and are not intended for production. If the campaign reaches voicemail, ThunderPhone can let the prompt decide, hang up, or leave a configured message. Campaigns can retry voicemail outcomes according to their retry policy. Keep voicemail language general enough for the business's privacy rules, and do not count a left message as a reactivated lead.
Connect Slack when a newly active lead should alert its owner. A remote Zapier MCP connection can expose selected actions from an existing workflow; ThunderPhone adds remote MCP servers by URL, synchronizes their tools, and attaches them to agents. Webhook endpoints can use separate secrets and event subscriptions, retry non-blocking deliveries, and sign requests with HMAC-SHA256.
Test the paths most likely to expose bad assumptions: a forgotten inquiry, a changed phone owner, an already-completed purchase, an immediate opt-out, voicemail, missing source data, conflicting CRM fields, no available appointment, and a failed transfer. ThunderPhone provides AI-caller simulations, reusable scenarios, graded call logs, regression suites with pass-rate gates, and A/B experiments. Simulations are billable real calls, with the charge shown before a run.
What to measure
Measure whether the backlog becomes more accurate and actionable:
- intended-person contacts versus voicemail, no answer, and wrong party;
- active, deferred, completed, not-interested, and opt-out dispositions;
- qualification fields refreshed per connected call;
- appointments booked or human follow-ups requested;
- warm transfers attempted and accepted;
- stale records discovered and corrected; and
- downstream outcomes by original lead source and reactivation disposition.
Use the same definition of lead qualification across the agent and sales team. Otherwise, a “reactivated” record may simply mean that someone answered the phone.
Honest limits
An old lead record is not proof of current consent, current identity, or continuing interest. The customer remains responsible for deciding who is eligible to call and for configuring calling windows, notices, recordings, data handling, suppression rules, and opt-out management for its obligations. The agent should stop when the person declines, not search for a more persuasive version of the same pitch.
Complex pricing, negotiations, changed project scope, complaints about the earlier sales process, and strategic accounts require a human. The source system also needs a clear owner for failed writes and contradictory data. Use the agent to sort and refresh an approved backlog, then let a representative handle judgment-heavy conversations.
Configure a ThunderPhone agent for lead reactivation campaigns