Renewal Journeys
Part of Renewal communication journeys
Pausing renewal outreach after a contract decision
Define a verified contract decision, review queued renewal requests and check other channels before outdated outreach reaches the customer.
When a contract decision is recorded, identify every waiting message that still asks for that decision. Verify the outcome, then stop or review those sends. Keep only the confirmation or account information that remains appropriate.
Define the outcome event
Record a signed renewal, decline, cancellation or any other outcome the contract team recognises. A viewed proposal or completed meeting is progress, not necessarily a decision. Tie the outcome to the agreement ID, and note its time, effective date, supporting document or system, and authorised owner.
Keep pending verification separate from renewed. If someone reports agreement but the required document has not arrived, hold deadline claims for review and do not state that a new term is in force. Give disputed outcomes an exception state and an owner.
Key Compliance and Process Metrics for Renewal Outreach
- Verified Agreement ID Required
- Yes
- Effective Date Must Be Recorded
- Yes
- Authorised Owner Assigned
- Yes
- Pending Verification Kept Separate
- Yes
Review every waiting send
A state check near dispatch can catch a decision made while a message was waiting. Look beyond the main automation: a scheduled campaign, sales sequence or manually queued email may carry the same outdated request. Decide which sends to cancel, hold or rewrite.
| Current state | Response to waiting renewal outreach |
|---|---|
| Renewed and verified | Stop decision requests; send an approved confirmation and operational handover where needed. |
| Declined or cancelled | Stop requests based on the old agreement; handle necessary closing information separately. |
| Negotiation or verification pending | Hold claims that the decision is overdue or complete for owner review. |
| Outcome corrected or reversed | Reassess the current agreement instead of replaying an old queue. |
Customer.io documents configurable automation exit criteria based on profile attributes, events and segments. An exit condition in one automation does not establish what happens in other campaigns, sales tools or manually scheduled sends.
Keep a decline distinct from retention marketing
A decline state does not itself trigger a promotional win-back sequence. See the sibling article on retention marketing.
Check what happened
Review example records where a decision arrives before entry, during a wait and just before dispatch. Include a corrected decision and a message that has already sent. For each, specify the expected state, queued-send action and owner response. Inspect the behaviour in the actual systems before use.
Monitor messages delivered after decisions. If one slips through, preserve the decision and send times and check for a late update, wrong agreement ID or missing state check. Fix the control that failed.
