Automate the parts that are repetitive and reversible; keep manual the parts that are consequential. In practice that means automating scheduling, follow-up cadence and tracking, while keeping the send decision and any factual claim about a prospect under human review. Teams that invert this rule lose domains.
Automation pays off where the task repeats identically across every prospect and a mistake costs little.
Anything where the cost of an unnoticed error compounds across the whole list.
A sequence works when each step adds a reason to reply rather than repeating the first ask in different words. A three-touch structure covers most cases:
| Step | Timing | Angle | Purpose |
|---|---|---|---|
| 1 | Day 0 | The opener: their context plus your specific value | Earn attention |
| 2 | Day 3–4 | A different angle — a concrete outcome or proof point | Give a second reason to reply |
| 3 | Day 7–10 | A short close-out with a light ask | Make replying easy, then stop |
Three patterns account for most damage, and all three are visible in the data before they are visible in the inbox.
Follow-up is opt-in per lead. When enabled, Mailor schedules each step, uses a different angle from the previous one, and halts the sequence immediately on reply. Unsubscribe is permanent at the account level — an unsubscribed lead cannot be emailed again or re-enrolled. The leads list shows how many emails each lead has received, so a runaway sequence is visible rather than silent.
Three touches is the common structure: an opener, one follow-up with a genuinely different angle, and a short close-out. Beyond that, marginal replies are usually outweighed by the risk of complaints — and every step must stop on reply.
Sending itself does not, if volume and cadence are credible. What hurts is repetitive content at high volume with no engagement, plus sending from unauthenticated domains. Distinct angles, modest cadence and authenticated sending keep automation neutral to reputation.
Three to four days between the first and second touch, and roughly a week before the close-out. The exact interval matters less than consistency — the failure mode is a sequence that stops after one email because nobody scheduled the second.
Yes, and the requirement is structural rather than stylistic: every message must include a working unsubscribe mechanism and accurately identify the sender. Automation must therefore honour opt-outs permanently; Mailor enforces the unsubscribe link and blocks re-enrolment of unsubscribed leads.