A drip is a delivery pattern: each person starts at the beginning and advances through timed messages. Choose software by how it handles entry, delays, current contact data and exits, not by promises of automatic conversions.
Repli Email is an admin-only private beta. Creating an account or upgrading a plan does not unlock email sending. No public email allowance, price or launch date is offered here.
Write the entry rule first. A person who requests a guide today and a person who requests it next month should both receive the first relevant message, not join halfway through a calendar campaign. Decide how repeated entry requests are treated.
Then define the wait before each next action. A two-day wait after the first message is different from sending every Tuesday. Ask what happens to overdue steps, failed sends and paused sequences; timing labels alone do not answer those questions.
A tag condition only knows the tags present when it is evaluated. A customer-field condition only knows the stored value. Neither proves a purchase, reply or click unless an actual source updates that value and the next step reads it correctly.
The inspected Repli beta runner has delay, saved-template send, tag/contact-field condition, tag changes and exit actions. It does not establish universal reply-, open-, click- or purchase-driven cancellation. This guide explains the evaluation task rather than selling those behaviors as a live feature.
Give each message one useful purpose. For a requested guide, the arc might be delivery, explanation and a final invitation. Example waits are planning choices, not claimed default recipes, performance advice or guaranteed optimal timings.
Drip describes the timing mechanics. Lead nurturing describes helping a prospect make a decision; welcome describes the first stage after signup. Those narrower guides own their own examples. Repli Email remains private beta with no public sequence allowance or purchasable sending plan.
Send the requested guide through the chosen eligible email system.
Explain one practical use of the guide, provided the person chose ongoing updates.
Use a verified preference or customer field, then end the sequence rather than assuming conversion.
Choose the real source and what repeat requests should do.
Record which current field controls each decision and who updates it.
Evaluate pauses, suppressions, failures and exits before relying on the sequence.
No. Drip describes timed delivery; nurture describes the goal of answering a prospect’s questions. A nurture program can use a drip.
No. A purchase must reach the relevant contact state, and the sender must evaluate an appropriate stop rule. A delay alone does not cancel queued mail.
Repli Email is an admin-only private beta. Creating an account or upgrading a plan does not unlock email sending. No public email allowance, price or launch date is offered here.
How to evaluate email automation software
Welcome email automation for a real signup
Lead nurturing email automation for chat-origin inquiries
Email automation: Repli private beta