Drip journeys

Work with the right context

Create a reviewed sequence with an explicit admission rule, delay and exit policy. Each subscriber follows the version they joined, so changing a future journey does not silently rewrite an active customer’s schedule. Keep the next due step visible to the team.

Keep the next action clear

Check preference changes and configured exit events before sending the next message. A reply or acknowledged CRM conversion can end follow-up when the approved policy says it should. An uncertain provider result holds its step for reconciliation instead of scheduling the same message again.

Coordinate the workflow

Run drip journey. Submit the journey version and exit policy for Campaign Approver approval. Enroll each subscriber once per admission occurrence. Before each due step, check current permission, exit events and journey state; reserve that step once. A verified reply or configured CRM conversion can exit the journey without fabricating a sales outcome.

Honor preferences. Apply a preference change to its explicit list or global scope and stop unsent queued work that is no longer eligible. The dispatch-time check closes the race with an earlier audience snapshot. A request cannot recall a message already accepted by the provider. Suppression removal requires an independent approved review and never restores a withdrawn purpose by itself. A ListSpecific unsubscribe updates only its named list and purpose and creates no global suppression; unrelated still-permitted lists remain eligible. Global unsubscribe blocks all lists in its stated scope.

Reconcile provider state. Investigate Unknown dispatches with the original provider idempotency key and message reference. Confirm acceptance or failure before releasing any retry. Revoked credentials stop new dispatch, while configured inbound reconciliation can record verified outcomes for prior messages. Keep unmatched events visible for scoped investigation.

Drip campaigns. An enrolled subscriber advances only after the prior step is resolved. Pause, unsubscribe or verified exit prevents future messages and retries cannot repeat a step.

CRM contact sync. A repeated contact update reconciles to the same subscriber. Sales-record existence cannot grant email permission or expose unrelated contacts.

Follow a subscriber through a sequence

A welcome journey might begin with an introduction and schedule a later follow-up after a defined delay. The enrollment records the approved journey version and the subscriber’s admission occurrence. Replaying that same admission should find the existing enrollment rather than start another copy of the sequence.

Before the next step, check the subscriber’s current permission and the journey’s exit conditions. A verified reply or a confirmed CRM conversion can end the sequence when the approved policy says it should. An unverified event or a locally submitted conversion request cannot establish that exit by itself.