Renewal Journeys
Part of Renewal communication journeys
Separating reminder messages from renewal negotiations
Keep renewal process notices aligned with live negotiations using clear message purposes, a named owner and a recorded handover state.
A renewal process notice should give verified dates, the current process and a route for questions. A negotiation needs a named owner who can discuss proposed terms and record what has been agreed. Separate those jobs so automation does not contradict a live proposal or make an unapproved offer.
Set the message boundary
A process notice can identify the agreement and explain where the recipient can review relevant documents. It should not imply that a new price, term or concession has been accepted unless the change is approved and recorded. Avoid saying a renewal is ready while its proposal is still being revised.
Negotiation messages need the latest approved proposal version, an owner and a record of the customer's response. If the customer requests different terms, pause standard commercial messages and route the request to that owner. Review any waiting process notice too if its dates or description of the customer's options may now be inaccurate.
Record a handover the journey can use
A visible negotiation active state can identify the agreement, owner and next review point. Set it when a substantive terms discussion begins, rather than when someone merely opens an email. Name the person who clears it after a proposal is accepted, declined or withdrawn.
- Route a question about dates or process to the account owner; review whether any scheduled factual notice remains accurate.
- Route a request about price, scope or wording to the negotiation owner and pause automated offers.
- When an outcome is verified, close the negotiation state and begin the appropriate confirmation or closure process.
Check for crossed versions
Compare negotiation messages with the latest approved document before sending. An agreed extension can make a generic "decision due today" message misleading. If the customer has received two proposals, the owner should resolve which is current before further contract-specific outreach.
Review example histories in which a customer asks a deadline question, requests a price change, receives a revised proposal and then declines. For each event, decide which standard messages remain accurate and eligible. A suppression flag cannot fix inaccurate proposal content.
