Retention Operations
Retention programme operations
Set up the operating records, contact checks, escalation owners and review decisions that keep a retention programme coherent.
Run a retention programme from a shared record of what is live, who can receive each contact, which customer problems need attention and what decision each review will make. Without those controls, a campaign can send an outdated offer, collide with another incentive or leave a recurring service problem without an owner.
Keep one operating record
For each live or scheduled activity, record its purpose, owner, audience rule, channel, message or offer version, start and end dates, exclusions, intended outcome and next review. Include automated flows, manual sends and public promotions that could affect the same customers. Link to the approved configuration where the organisation's systems allow it.
An entry marked “live” should have a confirmed activation date. A paused entry should say what was paused and who can restart it. Keep old versions available for interpreting earlier decisions, while removing them from the active view.
Record the programme structure
Record the programme structure that governs live activities: the eligibility segments in use, the channels in scope, the launch stage and active countries or regions, and any reward or tier rule that affects who can receive a contact.
For a staged launch, list the initial channels, the channels to be introduced later and the date each becomes active. Keep planned changes in the same operating record so reviews can distinguish live activity from future activity.
Set precedence for conflicting contacts
Agree what happens when a customer qualifies for several activities. For example, an active service case may call for a promotional hold; a recent relevant order may make a win-back message inappropriate; and a recorded contact preference should be checked before a promotional send. Record the rule and the team responsible for applying it across channels.
An exclusion checked when an audience was built may be stale by dispatch. Recheck the available order, service and contact state as close to sending as the process permits. If a required check cannot be applied reliably, hold the affected promotional path for review. Continue necessary service updates through the appropriate process.
Record the basis on which each recipient can be contacted before a promotional send. Where the Australian Privacy Principles apply, take reasonable steps to ensure personal information used for a decision is suitable for that purpose and protected from unauthorised access.
Pre-Send Contact Validation Checklist
- Is the customer in an active service case?If yes, apply promotional hold per precedence rule
- Has the customer made a recent relevant order?If yes, avoid win-back messages
- Are contact preferences recorded?Verify before any promotional send
- Is data still valid at time of dispatch?Recheck order, service and contact state as close to send as possible
Apply APP 10 to decision records
Under Australian Privacy Principle 10, an APP entity must take reasonable steps to ensure the personal information it collects is accurate, up-to-date and complete. For information it uses or discloses, it must be accurate, up-to-date, complete and relevant to the purpose of the use or disclosure.
The requirement applies at two distinct points: when information is collected and when it is used or disclosed. Regular reviews at other times may help ensure quality at the point of use. Reasonable steps depend on the sensitivity of the information, the entity’s size, resources and business model, the possible adverse consequences for individuals, and practicability including time and cost.
APP 10 vs APP 11: Key Requirements for Data Quality and Protection
- Australian Privacy Principle 10 (Quality of Personal Information)Ensure personal information is accurate, up-to-date, complete and relevant at point of collection and use.
- Australian Privacy Principle 11 (Security of Personal Information)Take reasonable steps to protect personal information from misuse, interference, loss, and unauthorised access or disclosure.
Bring the right evidence to each review
| Question | Record to inspect | Decision |
|---|---|---|
| What is running? | Activity inventory and current configuration | Continue, correct or pause |
| Why did this person receive an offer? | Rule version, decision inputs and send record | Explain or correct the assignment |
| Could benefits combine? | Offer terms and checkout outcome | Change precedence or stacking rules |
| What customer problem recurs? | Issue evidence, owner and repair status | Escalate or verify a fix |
| Did an activity add value? | Agreed outcome and suitable comparison | Extend, narrow or stop |
A redemption shows that a benefit was used; it does not show that the activity added a purchase. A complaint count shows recorded cases; it does not establish why every customer stopped buying. Keep those limits in the decision record.
Retention Programme Review Process
- What is running?Inspect activity inventory and current configuration
- Why did this person receive an offer?Review rule version, decision inputs and send record
- Could benefits combine?Check offer terms and checkout outcome
- What customer problem recurs?Review issue evidence, owner and repair status
- Did an activity add value?Compare agreed outcome with actual results
Protect and dispose of data under APP 11
Australian Privacy Principle 11 requires reasonable steps to protect personal information from misuse, interference and loss, and from unauthorised access, modification or disclosure. Those steps include technical and organisational measures. An entity holds personal information if it has possession or control of a record that contains it.
When personal information is no longer needed for any purpose for which it may be used or disclosed under the APPs, an APP entity must take such steps as are reasonable in the circumstances to destroy it or ensure it is de-identified. This requirement does not apply where the information is part of a Commonwealth record or where an Australian law or court/tribunal order requires retention.
Close reviews with an action
Review imminent sends and new exceptions early enough to act. Set review frequency according to how quickly activities, customer state and operational risk can change; check more often when changes may affect imminent contact or materially affect customers.
Bring reviews forward for significant exceptions, repeated service issues, material rule or configuration changes, or unexpected results. Decide whether each activity continues, needs correction, pauses pending evidence or ends. Record the reason, effective date, owner and next check. Escalate recurring customer problems to the team able to address their cause.
When a rule changes, identify the customers and queued sends it could affect. Check representative records for a recent repurchase, an open complaint, overlapping offers and an opt-out. Confirm the resulting send and checkout behaviour in the organisation's systems before treating the change as implemented.
In this guide
- Keeping an inventory of active retention testsRecord test ownership, assignment, live exposure, changes and follow-up so retention experiments can be operated and interpreted.
- Recording why a customer received a win-back offerBuild an explainable offer-decision record with the eligibility rule, send checks, offer version and actual outcome.
- Reviewing overlapping retention incentivesCheck stacking, checkout outcomes, contribution and customer-facing claims when retention incentives overlap.
- Assigning owners to the root causes of customer lossTurn a suspected customer-loss cause into a bounded issue with an accountable owner, evidence check, repair and review date.
