Write the purpose before the schedule
Begin with the outcome you want from the next conversation: understand a need, answer a question, share a proposal, or confirm a decision. Avoid adding touchpoints simply to fill a calendar.
For a warm lead, an example is a discovery call, a proposal task two days after that call is completed, and a question-checking follow-up three days after the proposal task is completed. These are illustrative intervals, not a universal cadence. Adjust them to what the customer expects.
Choose what starts the clock
A delay can be measured from enrollment, a fixed date, or completion of a previous step. Those rules produce different results when someone is away or a task runs late.
Relavoy schedules the first sequence task relative to a chosen start time. Later delays begin when the previous task is completed. That keeps an unfinished step from silently triggering the next one.
- Give each step a concrete action: call, email, SMS, or general task.
- Include enough instructions for another teammate to understand the context.
- State whether a delay begins at enrollment or after completion.
Pause deliberately and keep the history
A customer may need more time, the opportunity may no longer be relevant, or a teammate may take over. Pause or cancel pending work instead of leaving outdated tasks in someone’s queue.
In the Relavoy preview, assignment copies the sequence. Editing the library changes future assignments rather than rewriting steps already assigned to a lead. Canceling removes the pending generated task while completed task history stays available.
A task sequence is not an automatic send sequence
The current implementation creates tasks for people to review and complete. It does not automatically send messages, detect replies, or attach documents. A task may ask someone to share a flyer through an external email account, but the task itself does not deliver it.
Keep that boundary clear when measuring results. Completing a task records work done; it does not prove a customer received or replied to a message. Log completed outreach separately, using the time it actually happened.