Why loyalty pages need a source card
Loyalty and rewards programs sound friendly, but they often involve exclusions, expiration dates, non-cash value rules, tier thresholds, fraud review, refunds, third-party apps, and region-specific terms. AI tools can turn a stale campaign email or old FAQ into a confident answer that promises points, discounts, member status, cash redemption, or an exception the business has not approved.
Copy/paste loyalty and rewards source card
Program name: [approved loyalty/rewards/member program name]
Source owner: [person/team responsible for policy]
Canonical policy URL or document: [link]
Last verified date: [date]
Who is eligible: [customer type, location, account type, age/ID if relevant]
How points/rewards are earned: [purchase types, rates, exclusions]
How rewards are redeemed: [online/in-store/support/manual approval]
Tier or status rules: [thresholds, benefits, review period]
Expiration / inactivity rule: [exact wording + date logic]
Refund/cancellation impact: [points reversal, credit removal, exceptions]
Cash value / transferability / stacking: [approved public wording]
Manual review triggers: [fraud, abuse, missing purchase, expired reward, edge case]
Customer-safe summary: [approved 2-3 sentence answer]
Do-not-say list: [unapproved offers, expired promos, unsupported exceptions]
AI/search audit owner: [who checks generated answers]
Customer-safe reply snippets
Thanks for asking. The current approved loyalty policy is here: [policy link]. Rewards are earned and redeemed according to that page, and edge cases such as expired rewards, refunds, account issues, or missing points need team review before we promise an adjustment.
I do not want to guess about your reward balance or eligibility. Please send [order/account detail], and our team will check the official record before confirming points, credits, expiration, or redemption options.
Internal note: Loyalty/rewards question. Verify canonical policy, account record, purchase history, tier status, refund history, and expiration rule before publishing or sending a final answer.
AI audit prompt
You are reviewing a small-business loyalty or rewards policy for AI-search accuracy. Use only the approved source card below. Identify any draft claims about points, tiers, redemption, expiration, credits, discounts, referrals, refunds, birthday rewards, cash value, transferability, or exceptions that are unsupported or ambiguous. Return: (1) safe public answer, (2) risky claims to remove, (3) source gaps to verify, and (4) STOP PUBLISHING triggers.
Approved source card:
[paste source card]Review before publishing
- Does the public page match the loyalty app/admin settings, current terms, and latest promotion calendar?
- Does the answer avoid promising points, credits, refunds, or exceptions that require account review?
- Are old campaign pages, email snippets, PDFs, and support macros redirected to the canonical policy?
- Is there a clear human owner for expired rewards, missing points, fraud/abuse flags, and refund reversals?
SEO After AI tie-in: this is the kind of source-control worksheet the full playbook uses to keep AI search answers truthful, current, and conversion-safe.
Start with the free AI search visibility audit View SEO After AI