- Industry
- Retail
- Department
- Customer
- Team
- Customer Lifecycle
- Kind
- Decision-maker
- Approver
- Customer Service Manager
- Code
- CUS-18
It manages the loyalty programme day to day: points adjustments, missing-points claims, tier changes, reward expiry and personalised retention offers, deciding each within the programme rules and the points budget. It posts the adjustments and proposes offers whose cost and expected lift it has forecast.
How it works
7 steps, and a person signs off before step 7.
- 01Looks it up
Finds the record the request is about in the loyalty and CRM platform: members' points ledger, tier, transactions from the point-of-sale and order systems, and the month's offer spend..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Forecasts, when it decides
Projects what each option will cost or return before it recommends one.
- 05Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 06Asks a person
Hands the work to Customer Service Manager with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the loyalty and CRM platform: it posts the points adjustments, tier changes and approved offers to each member's account. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The loyalty programme rules: earn and burn rates, tier thresholds, points expiry, missing-points claim rules, the offer catalogue and its costs, the points liability budget, and the fraud indicators for points abuse.
Reads from
the loyalty and CRM platform: members' points ledger, tier, transactions from the point-of-sale and order systems, and the month's offer spend.
Acts in
the loyalty and CRM platform: it posts the points adjustments, tier changes and approved offers to each member's account.
Hands back
A list with one entry per member, each with loyalty_id, decision (credit, refuse, adjust, tier_change, offer or refer_loss_prevention), points, offer (type and value, or null), expected_lift_percent, cost and reason.
Asks a person when
An adjustment exceeds 500 points, an offer would take the month past 20000, or a tier is extended outside the thresholds.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Points earned per dollar | 1 | The base earn rate used to check claims. |
| Missing-points claims allowed within (days) | 60 | Claims older than this are refused. |
| Most points it may add by hand | 500 | Adjustments above this need the approver. |
| Retention offer budget a month (USD) | 20000 | Offers stop when their expected cost reaches this. |
| Lowest expected spend lift for an offer (%) | 10 | An offer forecast to lift spend less than this is not made. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Credit missing points only for a transaction found in the point-of-sale or order system, within 60 days, at 1 points per dollar paid after discounts and returns.
- Never credit points twice for one transaction; reverse points on returned items.
- Adjustments above 500 points need the Customer Service Manager.
- Make a retention offer only when it is forecast to lift spend by 10 percent or more, and stop when the month's offers reach 20000.
- Tier changes follow the tier thresholds exactly; a tier extension is an offer and is costed like one.
- Send members with repeated claims for transactions not on their account to loss prevention.
See the Loyalty Program Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.