Reply received
The prospect replies to one of the sequence's emails, it stops immediately.
Sequences
A call goes unanswered? The prospect automatically enters an email follow-up sequence. The moment they reply, book a meeting, or pick up, the sequence stops, without you having to think about it.
Most email sequence tools are triggered manually, or follow logic disconnected from your calls. At Lea, enrollment comes directly from a call's outcome: no answer, and the prospect enters a sequence, with no extra action on your part.
No configuration to redo for every call, once the sequence is created.
From /settings/sequences: the subject and body of each step, the delay between them, up to 10 steps.
You log the call's outcome as usual. If the result matches, enrollment triggers automatically.
The first follow-up goes out about 10 minutes after the call, the next ones at the delays you configured (in days).
Reply received, meeting booked, call answered, deal closed, or unsubscribe: the sequence stops immediately, not one email too many.
A sequence that keeps going after the prospect has replied is the best way to annoy them. Lea checks these 5 signals continuously.
The prospect replies to one of the sequence's emails, it stops immediately.
A meeting is scheduled with this contact or this deal, no need to follow up anymore.
You manage to reach the prospect on a later call, the sequence no longer serves a purpose.
The linked deal flips to won or lost, the follow-up stops on its own.
The recipient clicks the unsubscribe link, they'll never receive another sequence email again.
Every sequence email includes a 1-click unsubscribe link compliant with the RFC 8058 standard (List-Unsubscribe-Post), natively recognized by Gmail and Outlook. Fewer spam complaints, better deliverability over the long run.
Email sequences exist elsewhere. Automatic triggering from a call's outcome is rarer.
| Feature | Lea | Pipedrive | HubSpot | Zoho |
|---|---|---|---|---|
| Automatic enrollment from an unanswered call | ✓ | ✗ | Workflows Pro+ | Partial |
| Automatic multi-signal stop (5 conditions) | ✓ | Basic | ✓ | Basic |
| RFC 8058 1-click unsubscribe | ✓ | Depends on config | ✓ | Depends on config |
| Up to 10 steps per sequence | ✓ | ✓ | ✓ | ✓ |