E-commerce
June 28, 2026
A customer may request a discount because they are hesitant, comparing prices, missed a promotion, or feel they deserve a gesture. The response must remain respectful without turning every support conversation into a negotiation.
The chatbot must distinguish between a public promo code, a commercial gesture, visual/volume discount, loyalty, pricing error, and exception. It must explain the available rules and transfer cases that require a human decision.
This guide shows how to handle discount requests without creating unfairness or degrading the margin.
Summary
Why must discount requests be structured?
If customers get a discount simply by asking, the brand creates an expectation of negotiation. Customers who do not ask may feel penalized, and agents become exposed to pressure.
The chatbot must therefore apply clear rules: public offers, loyalty conditions, planned gestures, or transfer when an exception is possible.
A fair discount must come from a clear rule, not from the level of customer insistence.
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 situations should be distinguished?
A distinction must be made between a promo code request, an expired promotion, a pricing error, a large shopping cart, a B2B order, a problem experienced, a loyal customer, and a comparison with a competitor.
These situations do not all require the same response. A gesture after an incident does not follow the same logic as a discount before purchase.
How do you respond without closing the door?
The bot can check available offers, recall public conditions, and propose a useful alternative such as a promotion alert, loyalty program, or choice guide. It must avoid cold phrases like "no discount possible" without context.
If the request falls outside the scope, it can explain that an advisor must validate it.
How to handle a missed promotion?
If the customer missed a promotion, the bot must check the period, the channel, the conditions, the country, and any potential screenshot. It must not extend an offer without a rule.
A screenshot of an active or contradictory offer must be forwarded, especially if it influences a purchasing decision.
How to handle rejections?
A refusal must be explained simply: the offer is expired, cannot be combined with other offers, is reserved for a specific segment, or is not applicable to the cart. The bot can offer other assistance but must not invent a compensation.
Tone matters: refusing a discount can still be a good experience if the customer understands the rule.
Which flow to follow?
The flow must verify before granting.
Identify reason, cart, customer, cited promotion, code, capture, and purchase context.
Verify public offers, terms, loyalty, volume, pricing errors, and history.
Offer only available discounts or benefits according to the rule.
Clearly explain refusal, limit, expiration, non-accumulation, or missing conditions.
Transfer pricing errors, goodwill gestures after incident, B2B, large carts, and disputed promises.
Which messages should be used?
To check: "First, I look at the available offers and the conditions applicable to your basket."
To refuse: "This promotion is no longer active, I cannot apply it without confirmed conditions."
To transfer: "Your request concerns an exception or a commercial gesture; I am forwarding the context to support."
When to transfer?
Transfer is necessary for pricing errors, conflicting offer captures, post-incident gestures, B2B clients, high volumes, special loyalty requests, or promises made by an agent.
The bot must transmit the cart, client, code, capture, consulted rule, request, and impact on the decision.
Which KPIs should be monitored?
Track discount requests, discounts granted, disputed rejections, commercial gestures, conversions after request, impacted margin, and repeated requests by campaign.
This data shows whether the commercial rules are clear and sustainable.
Which mistakes should be avoided?
Avoid granting discounts without rules, rewarding persistence, refusing without explanation, or mixing post-incident gestures with pre-purchase negotiation.
The chatbot must preserve fairness as much as the customer relationship.
How can Qstomy help?
Qstomy can connect the chatbot to business rules, orders, packaging, support decisions, payments, downloadable products, and escalation procedures to answer clearly, then transfer sensitive cases with an actionable summary.
The chatbot helps the customer move forward without inventing a discount, a package privacy guarantee, a support exception, a double charge refund, or download access that has yet to be confirmed by a reliable source.
Explore AI support, the AI sales agent or request a demo.
Key takeaways
Key Takeaways
Discount requests must follow clear rules: promotion, loyalty, volume, error, incident, or validated exception.
What the customer must understand
The customer must understand why a discount is available, refused, or transferred.
The chatbot's correct boundary
The chatbot can verify simple offers, but it must transfer price errors, commercial gestures, B2B, and disputed promises.
Enzo
June 28, 2026
