
Renewal Journeys
Part of Renewal communication journeys
Working backwards from a renewal date to plan outreach
Plan renewal messages from the agreement’s real deadlines, account tasks and time zone, then update the schedule when contract dates change.
undefined
To plan renewal outreach, anchor the work to the earliest verified date that changes the customer's options, then place the decision and messages before it. That may be a notice deadline, not the day a new term begins. A CRM renewal field alone may be too late or out of date.
Establish the controlling dates
Read the current agreement and amendments. Record the term end, any notice deadline and the date a renewed term would take effect. Note the applicable time zone and whether the agreement specifies a time of day. Ask the contract owner to resolve any difference between the documents and the account record.
Do not calculate a notice deadline from an assumed standard period. Terms vary and may change after an amendment. If the wording is unclear, have the contract owner interpret it before a message states a firm deadline.
In its Sensis undertaking, the ACCC says automatic renewal terms must be prominently disclosed, along with all steps customers can take to cancel and any cancellation fees that may apply. It warned that traders who fail to adequately disclose key contract terms risk misleading customers and breaching the Australian Consumer Law (ACCC).
Work backwards from the renewal deadline
Start with the controlling deadline and work backwards. Identify the latest point by which the customer must act to preserve an option, then place any customer review and approval before that point. Schedule messages early enough for the customer to identify an owner, review terms, obtain approval and return a decision through the agreed route; use the actual process to set lead times, and send another reminder only when it adds useful information.
A planning record can include:
Record the agreement ID and current version to tie messages to the right terms, the notice deadline and time zone to show when an option may close, and the renewal effective date to show when agreed changes take effect. Also record the account owner and decision contact, plus the decision state and last verification time, so questions have a destination and the send check uses current information.
These fields are a suggested planning record, not a required database design.
Recalculate when dates change
An extension, amendment or data correction can invalidate a waiting message. Review or cancel sends based on the old date, rebuild the schedule and check what the customer has already received. Check for duplicate enrolment as well as contradictory wording.
Customer.io supports automations over time, including recurring automations for subscription renewals. Its troubleshooting guidance says to check trigger conditions and filters, and the frequency setting when investigating why a person did not enter an automation (Customer.io).
Those features schedule from the data supplied; they do not establish which contractual date is correct. Behaviour in another platform or a particular account configuration must be checked there.
Handle late or uncertain records
Do not release a backlog of reminders just because records arrived late. Hold each affected record from automated sends, compare the agreement and amendments with the account record, and ask the contract owner to confirm the current deadline and decision state. If the deadline has passed, do not send a routine deadline reminder; send only the appropriate outcome communication once the state is confirmed.
Near a deadline, review an uncertain record before making an automated claim of urgency. Test an ordinary term, an amended date, an unspecified time zone and a completed decision. Verify that each send follows the current controlling date, old sends are cancelled after a date change, uncertain time-zone records are held for verification, and a completed decision stops further reminders; inspect send times and content in the actual setup.
Pre-Deadline Review Checklist for Renewal Records
- Verify agreement vs. account recordCheck for discrepancies between documents and CRM data.
- Confirm current notice deadline with contract ownerDo not assume standard notice periods; clarify ambiguous wording.
- Hold automated sends if record is late or uncertainDo not send backlog of reminders without verification.
- Test edge cases in automation setupValidate sends for amended dates, unspecified time zones, and completed decisions.



