A cadence should know when to continue—and when to stop

Build around a reason to follow up

Start with the context that justifies a message: a requested conversation, a relevant business change, or an action the person chose to begin. Define the audience and the expected next step before writing copy. A cadence should have an owner and a finite end.

Example sequence (illustrative)

1. Day 1: answer the question or introduce one specific reason for contact.
2. Day 4: add useful context or a concise resource.
3. Day 9: ask whether the topic is still relevant, then close the loop.

This is an example for planning, not a Cadensy schedule or delivery feature. In a real implementation, permitted weekdays, local time, volume caps, entry criteria and exits would be explicit. A reply, unsubscribe, invalid address, changed status or competing workflow should stop or route the sequence.

Review before launch

Check the source and accuracy of each personalization field. Confirm that the message fits the original purpose, that an owner can handle replies, and that suppression rules are current. Cadence automation is a product direction under development; the contact page is the current route for discussing it.