Loyalty Program Customer Service: A Missing-Points Workflow

The short version: Loyalty program customer service needs a decision system, not more policy prose. Define evidence, deterministic checks, remedies, authority, deadlines, and measurable escalation triggers for each claim category.

Turn policy into an executable decision record

Terms explain what members may receive. Agents need a record that tells them what to inspect and what action follows. Create these fields for every claim category: category, required_evidence, checks, pending_until, permitted_remedy, authority_limit, resolution_target, escalation_rule, and owner.

Start with eight categories: missing purchase points, delayed promotional bonuses, failed redemptions, expired rewards, account mismatches, returns or cancellations, partner transactions, and suspected abuse. Add another category only when it requires different evidence, checks, remedy, or ownership. Otherwise reporting fragments without changing the decision.

For missing purchase points, require an order ID or another unique transaction reference. Verify member identity, eligible amount, payment status, enrollment timing, exclusions, returns, posting window, and existing ledger events. Mark the case pending while the published posting window remains open; after that boundary, correct a confirmed missing event or deny an ineligible claim.

Queue contamination: routing everything into “missing points” mixes normal delays, campaign errors, duplicate accounts, partner-file failures, and ledger defects. Agents compensate cases that should have gone to campaign operations, platform operations, or a partner owner.

Verify the transaction, rule, and ledger

First verify the transaction. Match the member, order or receipt ID, date, channel, eligible amount, payment status, returns, and cancellations. If no receipt exists, accept another unique record such as authenticated order history, an order confirmation, payment reference, or partner transaction ID; a balance screenshot proves no purchase.

Next verify the rule that applied on the transaction date. Check enrollment timing, eligible products, minimum spend, coupon exclusions, activation requirements, channel restrictions, earning caps, and the promised posting window. Preserve versioned offer terms because current rules cannot establish what applied 90 days earlier.

Then reconcile the ledger. Search for the expected earn event, pending entry, reversal, expiry, redemption, and manual adjustment. Transaction-ID matching, arithmetic, balance reconstruction, and referential integrity are deterministic system checks; agent judgement belongs only where evidence remains incomplete or policy explicitly permits discretion.

Balance-only correction: an agent sees a low balance and adds points. The original earn is actually pending, attached to a duplicate account, or reversed after a return. The manual credit duplicates value while concealing the real cause.

Test the decision record before launch. Use an illustrative coverage sample of 24 masked cases: three from each of the eight categories, including approved, denied, and pending outcomes across the full set. This is a workflow test, not statistical validation; replace 24 with enough cases to cover every material branch in your program.

Have two agents decide each case independently, then compare both answers with an operations-approved answer key. Record eligibility disagreements separately from remedy disagreements. Require 100% agreement on deterministic facts and escalation routing; investigate every miss rather than averaging it away. Shared disagreement with the answer key exposes a bad instruction, while disagreement between agents exposes ambiguity.

Control adjustments without blocking ordinary cases

Separate standard corrections, goodwill credits, reward restoration, account merges, and high-value adjustments. A correction repairs an established ledger error. Goodwill resolves uncertainty within policy. Mixing those reason codes makes defect rates and program liability harder to interpret.

Illustrative authority limits could allow a frontline agent to issue value equal to one ordinary transaction, a team lead up to five, and program operations above that. These are not benchmarks. Set actual boundaries after inspecting your claim-value distribution, reward cost, confirmed abuse, and approval workload.

Use value, frequency, and policy override status—not the visual points number. Ten thousand points may represent £10 in one program and £100 in another. Require approval when an adjustment materially changes liability, restores expired value outside policy, or combines multiple accounts.

Before writing an adjustment, search the transaction ID, case ID, offer ID, member history, and prior credits. Use an idempotency key where supported. Exact matching will not detect split claims, changed identifiers, or linked accounts, so route those patterns through account-linkage rules or manual fraud review rather than pretending one search closes the risk.

Set separate acknowledgement and resolution targets. Illustrative targets are 1 business day for acknowledgement, 3 business days for ordinary owned-channel claims, and 10 business days for partner investigations. Replace them with targets supported by staffing, posting schedules, and partner contracts. Apply the financial controls described in Loyalty Points Liability: Build Controls Before Campaigns.

Value-blind authority: one universal points limit permits expensive adjustments in high-value currencies while delaying harmless corrections in low-value currencies. Control economic exposure instead.

Trace failed redemptions and escalate measurable patterns

Consider a member whose reward order failed after checkout. The agent confirms the authenticated order, then finds a completed ledger debit but no fulfilled order and no automatic reversal. A prior-adjustment search returns nothing, so the agent writes one corrective credit using the failed order ID as the idempotency key.

The new event records the reason code, evidence reference, original debit ID, before-and-after balance, adjustment value, agent ID, timestamp, linked case, and approval where required. The original debit remains untouched. If a retry later arrives with the same key, the platform rejects the duplicate correction.

Every manual change needs that audit trail. Overwriting ledger history destroys the evidence needed for member disputes, finance reconciliation, and defect investigation. Corrections should create compensating events.

Route defects by mechanism: ledger mismatches to platform operations, incorrect offer rules to campaign operations, absent partner files to the partner owner, linked-account claims to fraud review, and material aggregate adjustments to finance. Review weekly counts and adjustment value by reason code, campaign, partner, channel, and agent.

Use rates, not counts alone. One illustrative alert is at least five claims from one offer or partner during the review window and at least three times its trailing eight-week claims per 1,000 eligible transactions. These thresholds are operating examples, not findings; replace them after measuring normal variation, transaction volume, and investigation capacity. Manually review low-volume programs because a rate can swing on one claim.

Goodwill masking: repeated credits close tickets while a campaign rule or partner feed remains broken. Keep goodwill separate, alert on recurring mechanisms, and apply the account controls in Loyalty Program Fraud Prevention: Six Minimum Controls.

Key takeaways

• Define decision fields: evidence, checks, boundary, remedy, authority, deadline, trigger, owner.
• Reconcile before crediting: verify transaction, historical rule, then ledger event.
• Test covered branches: use masked, stratified cases plus an approved answer key.
• Control economic value: separate corrections from goodwill; preserve ledger history.
• Escalate measured patterns: combine minimum counts, rates, denominators, and owners.

Frequently asked questions

When are points pending rather than missing?

Points remain pending while the published posting window or a stated condition—payment settlement, delivery, stay completion, or return period—remains open. After that boundary passes without a matching ledger event, classify the claim as missing and investigate.

When should an agent issue goodwill?

Use goodwill when evidence is incomplete, policy permits discretion, and the value stays within documented authority. Record it separately from a correction so credited value does not hide earning defects.

How long should adjustment records remain accessible?

Keep them through the longest applicable points lifecycle, dispute period, finance audit requirement, or legal retention schedule. An illustrative floor is 24 months for a program with annual expiry; finance and legal owners must set the actual period.

When should repeated claims trigger fraud review?

Define thresholds from confirmed cases and a relevant comparison cohort. Measure reused transaction IDs, linked-account credits, missing-receipt frequency, and claims per completed transaction; never freeze an account merely because a member contacted support repeatedly.