Renewal Journeys
Part of Renewal communication journeys
Coordinating renewal messages across account contacts
Map renewal roles to a specific agreement, share one decision state and check each contact’s need and eligibility before sending.
Coordinate renewal outreach at the agreement level, then decide what each contact receives. Several people may influence a contract; sending the same decision request to every user can confuse them or disclose terms to the wrong person.
Map roles to this agreement
Record the people involved in the current renewal, not only their general job titles. An account may have a service lead, procurement contact, finance contact and authorised signatory.
One person can hold several roles or work with more than one account. Confirm each relationship and authority before sharing contract details.
A recipient map can guide the decision:
| Communication | Possible recipient | Check before sending |
|---|---|---|
| Service continuity | Operational contact | Does this person manage the service now? |
| Proposed commercial terms | Named negotiation contact | Is this the approved proposal and recipient? |
| Signature request | Authorised signatory | Has authority been verified for this agreement? |
| Outcome confirmation | Contacts with a follow-up task | Does each person need this information? |
This map does not establish who can legally sign for a customer.
Share the agreement state, check each person
The decision belongs to the agreement. If procurement records a decline, the service lead should not keep receiving requests to renew the same agreement.
If the signatory completes it, other contacts should receive only the follow-up they need. Use a shared agreement ID and decision state so each contact journey sees the outcome.
Still check each recipient’s current role, address and eligibility for the proposed content and channel. Check the applicable requirements before sending commercial electronic marketing.
Assess a factual account notice and a commercial proposal on their own content and purpose.
Prevent crossed conversations
Give the account owner a view of planned messages by contact and date. If procurement is discussing revised terms, review generic commercial reminders to other contacts before they go out.
Send any operational update only if its content remains accurate and the recipient needs it. Route replies from any contact to the person managing the agreement and reflect material changes in the shared record.
A matching company email domain does not prove that two people belong to the same contracting entity. Subsidiaries, consultants and shared services can complicate the relationship. Hold contract-specific details for review when identity or authority is uncertain.
Review an account history
Walk through an example with a service lead, procurement contact and signatory. Have procurement request revised terms, then have the signatory accept the final document. Check what each person would receive before and after those events. Repeat with a departed contact and someone attached to two accounts.
The desired result is one current set of terms, one recorded decision and follow-up each contact can act on. Check that the organisation’s actual records and messaging setup support it before sending.
