Reactivate REsimpli dead leads with a drip campaign

1. In REsimpli, build the drip under Automations > Leads > Manual Assignment, choose day-based or delay-based timing, add the SMS, email or direct mail steps and set a fallback number on any step whose campaign has no tracking number.
2. Open All Leads, click Add Filter and narrow the Dead Leads by dead lead reason, or by Legacy Drip Campaigns for leads carried over from REsimpli 5.0.
3. Select the leads, click Add to Automation, choose the drip and confirm. REsimpli allows 100 records a day this way, counted across the whole account.
4. Check Automation Enrollment on the drip to see which leads are active and when each step is due.
5. The filter cannot tell a seller who sold last month from one who is still stuck, and a lead already in another drip gets a second sequence on top, so the list needs a read-through before every batch.

Find Dead Leads from the last two quarters whose reason was not "property sold", skip anyone already in an automation, and enroll up to 50 of them in my Reactivation drip this week. Tag them Reactivation Q4.

1. 01

   Check the drip before anyone is enrolled

   list_automations must show the drip you named as switched on. REsimpli restarts every enrolled lead at step one and sends broken merge fields as they are, so the agent asks you to confirm the drip was reviewed in REsimpli before the first enrollment of a new campaign.

2. 02

   Choose who deserves a second try

   The agent pulls Dead Leads with list_pipelines and list_leads, then reads each lead with get_lead. Leads whose activity shows a dead reason such as "property sold" or "listed with agent" are skipped, and so are sellers whose notes mention an opt-out or a request to stop.

3. 03

   Skip leads already in a sequence

   A REsimpli lead can sit in several automations at once and there is no pause button. Any lead that get_lead shows inside another automation stays out, so no seller gets two drips in the same week.

4. 04

   Enroll in daily batches, with your OK

   enroll_lead_in_automation reaches the seller through texts, emails or mail, so each batch is shown to you before it runs. The agent keeps a day's batch under REsimpli's 100-record bulk ceiling and carries the rest to the next run.

5. 05

   Mark the batch

   tag_lead adds the campaign tag you chose to every enrolled lead. The tag lets you filter the batch later and compare replies against the next one.

Dead Leads checked: 212 (Apr to Sep 2026).
Skipped 61: 38 "property sold", 9 "listed with agent", 6 asked to stop, 8 already in another automation.
Enrolled 50 in "Reactivation" after your OK, tagged Reactivation Q4.
First SMS goes out tomorrow 9:00 under the drip's day-based schedule.
Left for next week: 101 leads that pass the filter.
Example: 19 Cedar Ln (dead in May, "needs too much work") enrolled.

• REsimpli lets you bulk add existing records only to Manual Assignment automations, with a limit of 100 records per day across the whole account.
• A lead added to a REsimpli automation starts from the first step; a lead from a legacy drip cannot resume where it stopped, and its task cards reset.
• Turning on a REsimpli automation does not enroll records that already match it, because new-record, tag and status triggers only react to events after activation.
• REsimpli does not stop a drip when the seller replies unless Conversational SMS AI is on for the lead or you build Activity Trigger automations with Stop other automation for incoming SMS and incoming calls; those intent triggers need a Full AI Team subscription after the trial.
• A REsimpli drip sending from a marketing campaign without a tracking number has nothing to send from until you set a fallback number on the step.

enroll_lead_in_automation asks for your OK by default. To run it weekly without you, switch confirmation off for that tool in your dashboard.

Sources: REsimpli Help: Reactivate leads from a previous drip campaign · REsimpli Help: Manual automations for leads · REsimpli Help: Automation triggers for leads · REsimpli Help: Stop automations when a lead replies · REsimpli Help: Reactivate a dead lead

curl https://cotlet.dev/api/v1/resimpli/enroll_lead_in_automation \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"lead_id":"66f1c2a9e4b0a1d3c8f20417","automation_id":"65b7e0a3d2c4f1009e8a1b52"}'

{
  "lead_id": "66f1c2a9e4b0a1d3c8f20417",
  "automation_id": "65b7e0a3d2c4f1009e8a1b52",
  "status": "enrolled"
}

MCP: add https://cotlet.dev/mcp/v1 with the same key; the tool is resimpli_enroll_lead_in_automation. Example data.

• Update REsimpli lead statuses and notes after a calling session
• REsimpli API and MCP server: every tool
• All use cases