E-commerce
July 1, 2026
Push notifications can quickly inform a customer about an order, a restock, or a delivery. They can also annoy if they are too frequent, poorly targeted, or difficult to disable.
Support must help the customer understand why they are receiving these notifications and how to manage their preferences.
This guide shows how to answer customer questions about e-commerce push notifications.
Summary
Why are push notifications sensitive?
A notification appears directly on the customer's device. It is more interruptive than an email, so it must be useful, expected, and manageable.
The response must respect the customer's right to control this channel.
A push notification must deserve the attention it demands.
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
What questions should be checked?
Check device, application, browser, consent, notification type, preference, account, order, campaign, frequency, opt-out, and message received.
A distinction must be made between transactional notification and marketing notification.
How can I help disable or modify?
Explain where to change preferences in the account, application, or device settings. If certain order-related notifications are still necessary, make it clear.
The customer must be able to regain control.
When device settings still block push notifications, support must explain it simply.
How do you respond to a notification that has not been understood?
If the customer receives a notification about an order, stock, or marketing promotion, verify the event that triggered it. A notification received too late or without context can cause confusion.
The response must link the message to a real action.
If a notification announces a status that no longer corresponds to reality, such as a package marked as delivered then put back in transit, support must explain the update rather than letting the customer believe it is a permanent error.
The push notification must be put back into the context of the complete history.
How to limit fatigue?
Set a reasonable frequency, clear categories, and priority rules. A customer who receives too many push notifications may disable everything, including useful messages about their orders.
Support must escalate complaints about frequency or targeting.
The push channel must remain a trusted channel.
You should also plan for cases where the customer changes phones, reinstalls the application, or shares a device. A notification may continue to appear on an old device if preferences are not synchronized.
Support must know how to explain this situation without blaming the customer.
Which flow to follow?
The flow must verify preference and trigger.
Identify customer, device, account, message, push type, consent, and request.
Verify order, campaign, preference, frequency, device settings, application, and logs.
Explain why the notification was sent and how to manage it.
Disable, modify preference, forward bug, reassure, or report a campaign.
Measure push complaints, deactivations, useful clicks, bugs, frequency, and satisfaction.
Which examples should be used?
“This notification is about the back-in-stock you requested.” “You can turn off offers while keeping the order alerts.”
The answer must give control.
When to transfer?
Transfer is necessary for contested consent, push bugs, sensitive notifications, personal data, massive campaigns, public complaints, or vulnerable clients.
The bot must transmit the client, message, device, type of push, consent, time, and request.
Which KPIs should be monitored?
Track sent notifications, clicks, opt-outs, complaints, errors, frequency per customer, conversions, and satisfaction.
This data shows whether the push notification is helpful or causes fatigue.
Which mistakes should be avoided?
Avoid push notifications that are too frequent, impossible to deactivate, poorly targeted, lacking context, or that confuse transactional and marketing messages.
The customer must remain in control.
How can Qstomy help?
Qstomy can connect the chatbot to purchase history, customer preferences, push notifications, campaigns, QR codes, orders, stores, events, payments, and escalation procedures to respond accurately.
The chatbot helps the customer understand a recommendation, notification, or purchase via QR code without inventing consent, a promotion, an order, or a status that needs to be verified.
Explore AI support, the AI sales agent, or request a demo.
Key takeaways
Key Takeaways
Push notifications must clarify consent, type of message, trigger, frequency, preference, opt-out, and bugs.
What the customer must understand
The customer must know why they are receiving a push and how to control it.
The chatbot's limits
The chatbot can explain and guide, but it must transfer disputed consent, bugs, and sensitive data.
Enzo
July 1, 2026
