E-commerce
July 1, 2026
A loyalty card seems simple as long as it works. As soon as the customer cannot find their number, does not see their points, or thinks they have lost a benefit, frustration quickly sets in.
The chatbot must help find the card, explain the balance, distinguish between points, rewards, and statuses, and then transfer cases where synchronization or identity verification is required.
This guide explains how to manage loyalty card-related requests with an AI chatbot, without exposing account data.
Summary
Why is the loyalty card sensitive?
The loyalty card sometimes contains a value: points, benefits, discounts, customer level, or purchase history. If the customer thinks this value has disappeared, they expect a precise answer.
The chatbot must therefore treat the card as a customer account element. It can guide, but it must verify before displaying or modifying personal information.
For the customer, lost points often feel like lost money.
Convert over 2,000 customers on average per month with Qstomy.
The world’s 1st Shopify AI dedicated to customer conversion
Empowering 200+ e-commerce merchants
Which requests should be recognized?
Frequent requests concern a lost card number, a points balance, an unrecognized card, missing points after purchase, a lost physical card, or a synchronization between store and online account.
The bot must distinguish loyalty card, customer account, gift card, and coupon. These words are sometimes mixed up by customers.
How to find a card?
The chatbot may request the account email, the associated phone number, the connected account, or a recent order reference according to the established procedure.
It should avoid displaying the full card number if it is not necessary. A masked number or a secure link may suffice.
How do you explain the balance?
The balance may include available points, pending points, expired rewards, or a loyalty tier. The bot must explain these categories in simple language.
If points from a recent purchase are not yet visible, it must specify the synchronization delay if this information is known.
What to do in case of missing points?
The bot must verify the order, the date, the account used, the exclusions, and the credit timeframe. Some purchases do not generate points or credit them later.
If the timeframe is exceeded or if the customer provides proof, it must be transferred with context rather than credited automatically.
Which flow to follow?
The flow must find the card and explain the visible value.
Identify if the request concerns a card, points, reward, or account.
Verify the customer with the minimum necessary information.
Explain the balance, pending points, expiration, or synchronization.
Guide towards retrieving or linking the card.
Transfer disputed points, sensitive lost cards, and blocked synchronizations.
Which messages should be used?
To find: "I can help you find your card with the information associated with the account, without displaying more data than necessary."
For points: "Some points may appear after a synchronization delay. I am checking the visible status."
For a dispute: "I am forwarding your request with the relevant order to check the missing points."
When to transfer?
Transfer is necessary if points are disputed, if the card is associated with another account, if a reward has expired, if the customer requests a manual credit, or if the store-web synchronization is blocked.
The bot must transmit account, masked card, order, date, expected points, and any potential proof.
Which KPIs should be monitored?
Track recovered cards, missing points, synchronizations, expired rewards, manual credits, and loyalty transfers.
These indicators show whether the program is understood and if points are visible at the right time.
Which mistakes should be avoided?
Avoid displaying too much account information, crediting points without verification, confusing loyalty cards and gift cards, or ignoring synchronization delays.
The chatbot must reassure the customer while protecting the value associated with their account.
How can Qstomy help?
Qstomy can connect the chatbot to the catalog, stock, orders, customer account, support rules, and useful context to respond clearly, then transfer sensitive cases with an actionable summary.
The chatbot helps the customer move forward without exposing unnecessary data or promising an action that still depends on human or operational validation.
Explore AI support, the AI sales agent, or request a demo.
Key takeaways
Takeaways
A loyalty card must be treated as account data with customer value.
What the customer needs to understand
The customer must understand where to find their card, how to read their balance, and why points might be pending.
The chatbot's correct boundary
The chatbot can guide and explain, but it must hand over contested points, manual credits, and sensitive synchronizations.
Enzo
July 1, 2026
