E-commerce
August 11, 2026
"I ordered yesterday, my points still aren't showing up." "My friend referred me, I didn't receive anything." "I had 800 points, now there are only 200 left." Three loyalty-related tickets that arrive every week, even though the program is documented somewhere.
Antavo reports that 49% of consumers cite rewards taking too long to obtain as their primary loyalty program frustration, and that opacity surrounding point credits fuels program abandonment (Antavo, 2026 Loyalty Report). LoyaltyLion estimates that 64% leave a program if the balance or credit rules remain unclear (LoyaltyLion, Loyalty 2026).
This guide #374 covers how to handle customer inquiries about missing loyalty points: PTS-REC investigation, agent macros, Smile.io/Yotpo sync, and the loyalty_incident_rate KPI. This is distinct from pre-launch loyalty questions (anticipating go-live) and the upcoming #375 loyalty bot: here, we focus on missing or incorrect points incidents post-purchase, not general program FAQs.
Summary
Why do missing points tickets overload loyalty customer service?
Missing loyalty points tickets often represent 20 to 35% of the loyalty customer support volume on DTC stores using Smile.io, Yotpo Loyalty, or LoyaltyLion once the post-launch peak has passed.
Five Customer Frustrations
Opaque credit delay: "how many days before I get my points?"
Guest checkout vs. guest account: points are not linked
Excluded promo not understood: sales or 20% off codes exclude points
Partial return: poorly explained points clawback
POS/Web sync: in-store purchase invisible online
US Tech Automations identifies invisible balances during shopping as a major friction point (63% of poorly configured programs) and a source of recurring "missing points" tickets (US Tech Automations, 2026 Loyalty Friction).
Angle #374
The pre-launch loyalty questions guide anticipates go-live FAQs. #374 isolates operational incidents regarding missing or incorrect points: investigation workflow, manual crediting, and recurrence prevention.
DTC Example
Fashion brand, 86 pts_missing tickets/month before PTS-REC. After macros + visible credit delay in account + bot intent: loyalty_incident_rate -41%, first_contact_resolution pts 78%, loyalty CSAT 4.4/5.
Cost of a Poorly Handled Ticket
Agent double-credits = lost margin. Agent wrongly refuses = "points scam" review + program churn. Structured investigation = 6-10 min vs 20 min email thread.
Standard Delay Window
Document official credit delay (e.g., D+3 post-shipping, D+14 eligible return window). 80% of "missing" tickets = customer too impatient vs actual bug.
Weak vs. Strong Signal
Weak: "Where are my points?" order placed D+1 before policy delay.
Common Support Error
Crediting points without checking promo exclusions: customer orders with -30%, policy = 0 points, agent adjusts 150 pts out of empathy. Financial audit impossible.
Retention Impact
A customer resolved within 24 hours with a clear explanation remains subscribed to the program. An ignored customer for 5 days churns at 68% according to Antavo post-incident benchmarks.
Typical Post-Launch Volume
Week 1 go-live: 3x peak in loyalty tickets. Month 3 stabilized: pts_missing = 25-35% of loyalty volume if self-service is low.
How does it differ from the loyalty questions and bot #375?
Seven neighboring pieces of content, seven roles on loyalty and support.
Pre-launch loyalty questions
Loyalty questions: Go-live FAQ, promo accumulation. #374 = post-purchase incident with missing points, not anticipation of launch.
Future loyalty bot (#375)
#375 will cover balance, rewards, and rules via AI. #374 = customer service process manual credit investigation when points are missing.
Credit note vs refund
Credit note vs refund: post-return value. #374: program points, not store return credit.
Goodwill gestures (#238)
Goodwill gestures (#238): customer service discount for incident. #374: due points credit, not discretionary gesture.
VIP Escalation
VIP Escalation: gold+ tier complex incident. #374 provides the investigation basis prior to escalation.
Omnichannel POS Support
Omnichannel POS: store/web sync. Frequent source of cross-channel pts_missing.
Promise #374
PTS-REC framework, typology of causes, LOY-PTS-* macros, loyalty apps sync, loyalty_incident_resolution KPI.
Which causes of missing points should be mapped?
Mapping the missing point causes guides the investigation without blind crediting.
Ten causes of pts_missing
Credit delay not elapsed: policy D+3 post-ship
Guest checkout: email does not match loyalty account
Product/order excluded: sales, gift card, shipping only
Promo code cumulative prohibition: -20% = 0 points
Return / refund: automatic clawback
Loyalty app bug: Shopify webhook failed
Double account: points on another email
Referral not validated: referee has not ordered yet
POS not synchronized: store purchase off-account
Annual tier reset: customer confuses expiration vs missing
Helpdesk tags
pts_missing, pts_clawback_query, pts_referral_missing, pts_pos_sync, pts_delay_faq. Distinct from loyalty_general and redemption_help.
Mining 90-day tickets
Export pts + "missing", "not received", "disappeared". Quantify cause #1. Prioritize FAQ and bot on top 3.
Cause → action matrix
Delay → explain policy + expected credit date. Guest → merge account + retro credit. Exclusion → cite rule + no credit. Bug → manual credit + ops ticket.
60 min Workshop
Support + Smile ops: read 40 pts_missing tickets, check causes, validate macros by cause.
How to apply the PTS-REC framework in seven steps?
The PTS-REC framework (Points Recovery) structures investigation and resolution into seven auditable steps.
Seven PTS-REC Steps
PR-1 Identify: account email, Shopify order ID
PR-2 Verify eligibility: products, promotions, fulfilled order status
PR-3 Calculate expected points: €/point rate from official policy
PR-4 Consult app history: Smile/Yotpo activity log
PR-5 Diagnose cause: delay, exclusion, bug, duplicate account
PR-6 Resolve: explain, manual credit adjust, account merge
PR-7 Confirm to customer: summary email with points + current balance
Calculate expected points
Example: €89 excl. tax eligible × 1 pt/€ = 89 pts. Exclude €6 shipping and gift card line item. Document formula in Notion agents.
Smile.io adjust points
Admin → Customer → Adjust points → reason "Support correction PR-6" + order ID note. Never adjust without PR-3 calculation.
Yotpo / LoyaltyLion
Same logic: activity log, manual point adjustment, reason code support_pts_rec.
Manual credit limit per agent
L1 Agent: adjust up to 500 pts or 1 order. Beyond that: manager + ops. Double-credit prevention: check adjust for same order within 30 days.
SLA pts_missing
First response 4 h, resolution 24 business hours. Priority P3 except VIP Gold+ → P2.
Detailed PR-3 Example
Order #7842: dress €79 + shipping €5.90 + code WELCOME -15%. Eligible base = €79 - €11.85 = €67.15. Rate 2 pts/€ = 134 expected points. Smile activity log: 0 → adjust 134 + order note.
Double credit prevention
Before adjust: search order ID in Smile notes for last 30 days. If adjust already exists for same amount: explain to customer, no second credit.
Which self-service diverts delivery time and guest tickets?
The loyalty points self-service deflects tickets before agent escalation if delays and rules are visible.
Page /fidelite delays section
« Points credited within 3 business days after shipment. Returns: clawback within 48 hours of refund. » Table of excluded products.
Customer account balance widget
Display balance + « next expected credit: order #4521, +89 pts on [date] » if app permits. Reduces delay tickets by 30 to 50%.
FAQ accordion pts_missing
8 Q&A: delay, guest merge, promo stacking, return, referral, POS, expiration, support contact.
Post-purchase email
Transactional D+0: « You will earn X pts upon shipment. Delay: 3 days. » Loyalty account link.
Bot intent pts_delay_faq
Customer « missing points » + order < delay policy: bot states expected credit date without handoff. Feeds future #375.
Merge guest account flow
Self-service « link guest order »: order email + verification code. Reduces guest pts_missing by 40%.
Which LOY-PTS macros for agents?
Standard LOY-PTS-* agent macros standardize responses without unauthorized credit.
Six LOY-PTS macros
LOY-PTS-DELAY-01: delay not elapsed, credit date expected
LOY-PTS-EXCL-01: excluded product/promo, rule cited
LOY-PTS-CREDIT-01: manual credit performed + new balance
LOY-PTS-GUEST-01: account merge + retro credit
LOY-PTS-CLAW-01: return = clawback of points, calculation detail
LOY-PTS-REF-01: referral pending referral's first order
45-min Agent Training
PR-3 calculation mandatory before LOY-PTS-CREDIT-01. Never promise future points not guaranteed by policy.
Ticket Documentation
Fields: order_id, pts_expected, pts_credited, cause_code, adjust_id Smile. Feeds KPIs and financial audit.
Ops Bug Escalation
Webhook failed for the same order ×3 customers/week: ops ticket + manual batch credit. No 50 isolated adjustments without a product alert.
VIP tier
Gold+ pts_missing: 2-hour SLA, manager notify if adjust > L1 cap. Link VIP escalation.
Empathy Script LOY-PTS-CREDIT
"Thank you for your patience. I checked order #7842: 134 points were manually credited. Your current balance: 412 points. Sorry for the delay."
Handoff bot → agent
Bot calculates PR-3 and detects gap: pre-filled ticket pts_expected, probable webhook bug cause. Agent validates within 2 mins.
How to align Smile.io, webhooks, and ops exclusions?
The ops apps loyalty alignment prevents recurrence of missing points incidents.
Shopify → Smile Webhook
Verify orders/fulfilled trigger active. Monitor failed webhooks dashboard Smile. Slack alert if > 5 fails/day.
Documented exclusion rules
Metafield product loyalty_eligible false on final sales. PDP badge "Not eligible for loyalty points" if excluded.
Promo accumulation policy
Smile setting: points on discounted orders yes/no. Align marketing (promo email) and support (EXCL macro).
Returns clawback
Return processed → auto deduct points. Customer email "X pts deducted following refund #RMA". Reduces clawback query tickets.
Shopify POS sync
Customer identifies email at checkout before payment. Staff training: "Your points on this account?"
Loyalty release checklist
Each change in points rate or exclusion: update FAQ, macros, bot corpus, email ops same day.
Which loyalty_incident KPIs should be measured?
Measuring loyalty point incidents proves PTS-REC and self-service ROI.
Seven Key Metrics
loyalty_incident_rate: pts_missing tickets / eligible orders/month
pts_missing_fcr: resolved 1st contact / pts tickets
manual_adjust_count: manual credits / month
manual_adjust_pts_value: € value of points credited by support
pts_delay_faq_deflection: bot resolves delay without agent
cause_mix_pts_missing: breakdown of 10 causes
loyalty_csat_post_incident: survey after pts resolution
DTC Benchmark
Target loyalty_incident_rate down 30% post-PTS-REC, pts_missing_fcr > 75%, manual_adjust < 2% of orders.
Weekly Dashboard
pts_missing volume, top cause, manual adjusts, webhook fails. Share to #support + #loyalty-marketing.
Excessive Adjust Cost
manual_adjust_pts_value × margin = program cost. If bug causes > 40% of adjusts: priority ops fix vs training agents.
Content Loop
Top verbatim → FAQ Q&A. Link questions to content.
Webhook Alert
If manual_adjust_count +30% week and bug cause > 25%: P1 ops incident, not agent training.
Self-Service Delay ROI
44% deflection pts_delay = 32 tickets/month avoided × 8 min × €0.35/min = €89/month + CSAT.
Which edge cases should be treated differently?
Six missing edge case points require specific PTS-REC rules.
Partially returned order
Proportional line items clawback. Explain PR-3 calculation on the net retained amount.
Expired vs. missing points
Customer confuses 12-month expiration with a bug. Show activity log expiration date, do not perform retro credit.
Amazon Marketplace order
Excluded from the DTC program. Marketplace redirect policy, do not adjust Smile.
B2B wholesale account
B2C loyalty program only. Macro wholesale redirect.
Points farming fraud
Multiple accounts at the same address: manual review before adjustment. Link to order fraud.
Loyalty app migration
Smile → Yotpo change: historical points migrated? Proactive communication + temporary pts_missing file.
Which support mistakes cost credits and trust?
Five pts_missing anti-patterns worsen incidents and loyalty program costs.
Crediting without investigation
Blind adjustments to close tickets = double crediting or fraud. PR-3 is mandatory.
Refusal without explanation
"Not eligible" without citing the rule = negative review. Always use LOY-PTS-EXCL-01 with a FAQ link.
Promising unsecured future points
Agent stating "you will get your points tomorrow" without verifying the webhook: CSAT drops if wrong.
Ignoring guest merge
Forcing a new registration instead of merging = customer loses tier history.
Adjustment without ticket log
Finance cannot audit. adjust_id + order_id are mandatory.
How does Qstomy handle pts_missing intents?
Qstomy processes pts_missing intents: check delay, calculation expected and handoff adjust if bug confirmed.
pts_missing capabilities
pts_balance_lookup: balance + activity log via Shopify email
pts_delay_faq: policy delay + expected credit date order
pts_eligibility_check: promo/SKU exclusions on order
pts_expected_calc: eligible amount × policy rate
pts_handoff_agent: bug or adjust ceiling → PR-6 agent
guest_merge_guide: self-service link order linking
Quantified DTC Scenario
Smile.io beauty brand, 72 pts_missing tickets/month, pts_missing_fcr 52% before bot.
After Qstomy intents: pts_delay_faq_deflection 44%, pts_missing_fcr 79%, manual_adjust_count -22% (fewer abusive credits).
Explore AI support, Shopify, request a demo.
Future Add-on #375
#374 = missing points incidents. #375 = bot balance, rewards and general program rules.
What is the checklist for deploying PTS-REC?
PTS-REC Checklist (10 steps)
Audit pts_missing tickets for 90 days and causes
Document workflow PR-1 to PR-7
Publish credit delay and exclusions /fidelite
Create 6 LOY-PTS agent macros
Configure balance widget + next credit customer account
Monitor Smile webhooks failed daily
Train agents on PR-3 calculation (45 mins)
Bot intent pts_delay_faq
Weekly loyalty_incident_rate dashboard
Quarterly review cause_mix + ops fixes
In short
#374 = missing points incidents, not loyalty go-live FAQ
PTS-REC: 7 steps identify → confirm credit
80% of tickets are often delay or exclusion, not a bug
PR-3 calculation mandatory before manual adjust
KPI pts_missing_fcr: target > 75%
FAQ
Difference with pre-launch loyalty questions?
Pre-launch = anticipating go-live FAQ. #374 = resolving post-purchase missing points incident.
Credit without checking order?
No. PR-3 calculation + activity log before any adjust.
Guest checkout without account?
Merge account or retro credit after checking order email.
Relationship with bot #375?
#374 = incident investigation. #375 = balance and program rules via AI.
Points removed after return?
Normal clawback. Macro LOY-PTS-CLAW-01 with calculation details.
Going further
Test mystery shop: eligible test order, check delay displayed in customer account and agent macro if D+4 credit simulated.
Share this guide #374 with support and loyalty ops: a structured PTS-REC investigation turns points frustration into program trust.
Enzo
August 11, 2026
