Anchor every delay to the original event, not the last touch
A common mistake: each follow-up message resets the clock, so a lead who doesn't respond gets messaged more and more frequently as time passes. The better model anchors every touchpoint's delay to the original trigger — the first unanswered message or missed call — so "follow up at 24 hours" always means 24 hours after the original event, regardless of what fired in between.
A cadence that works for most B2C and SMB sales
- 5 minutes: a near-instant nudge while the lead still remembers filling out the form or sending the message.
- 2 hours: a second touch for anyone who didn't see the first one, still same-day.
- 24 hours: a final, lower-pressure check-in before the lead is considered cold.
Longer sales cycles (real estate, education admissions, enterprise deals) extend this with additional tiers at 2 days, a week, and beyond — the principle stays the same: decreasing frequency, anchored to the original event.
Vary the message, not just the timing
Sending the identical message three times reads as a broken bot, not persistence. Each touchpoint should acknowledge that it's a follow-up and add something — a different angle, a direct question, or an offer to answer whatever's holding them back — rather than repeating the original pitch verbatim.
Stop the sequence the moment they respond
This sounds obvious, but it's the most common implementation bug: a scheduled follow-up firing after the lead already replied, because the system checked the schedule instead of the current conversation state. Every touchpoint needs to re-check whether it's still relevant right before it sends, not just at the time it was originally scheduled.
How Lira handles this
Sequences are configurable per agent, per channel — set your own delays and instructions for each touchpoint, anchored to the original trigger automatically, with no risk of a stale message firing after the lead has already replied.
See Lead Follow-Up →