E-commerce
July 1, 2026
A slow or unavailable chatbot can frustrate a customer at the worst possible moment: checkout, order tracking, returns, or an urgent issue. The customer does not know if their request is being processed, if they should wait, or if there is another solution.
Good communication prevents a technical incident from turning into a bad brand experience. You must explain things simply, offer an alternative, and resume the context when the service is restored.
This guide explains how to communicate when an AI chatbot is slow or unavailable, without leaving the customer stranded.
Summary
Why must a chatbot's unavailability be explained?
When the chatbot does not respond, the customer does not see the technical cause. They only see a brand that is not responding. This perception is even more negative if the problem concerns an order or a payment.
The bot, or the backup system, must therefore indicate that a problem exists and suggest a next step. Silence is the worst response.
An unavailable chatbot must still help the customer know what to do.
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 situations should be anticipated?
Common situations include slowness, lack of response, maintenance, connection error, overload during a peak, inability to reach an agent, or a partial response.
Each situation must have a tailored message. Planned maintenance is not communicated in the same way as a sudden outage during Black Friday.
How should the message be phrased?
The message must be short and honest: "The chat is currently experiencing a slowdown. You can wait or contact us via [channel]."
It must avoid vague formulations like "an error has occurred" without an alternative. The customer needs a way out.
What alternative can be proposed?
The alternative depends on the urgency: email, form, telephone, help center, self-service order tracking, or delayed message. The customer must know which channel to choose.
For sensitive topics such as a debited payment, lost package, or urgent order, the message must direct to the priority channel.
This hierarchy avoids treating all requests the same way during an outage. Simple product advice can wait, but a payment that has been debited without confirmation must find a quick resolution.
How to resume after the incident?
If the customer had started a conversation, the bot must try to resume the context when the service is restored. It can say: "The service is available again. Would you like to resume your previous request?"
This resumption prevents the customer from being charged for the technical incident.
Which flow to follow?
The flow must inform and redirect.
Detect slowness, unavailability, or maintenance.
Display a clear message with the impact level.
Offer an alternative adapted to the urgency.
Keep the context if possible for later resumption.
Report the incident to the teams if the volume or duration exceeds the planned threshold.
Which messages should be used?
For slowness: "The chat is slower than usual. Please wait a few moments or use our form if your request is urgent."
For maintenance: "The chat is temporarily unavailable for maintenance. You can consult the help center or contact us by email."
For a resumption: "I can resume your previous request if you wish to continue."
When to transfer?
Transfer or internal alert is necessary if the unavailability affects payment, peak sales, urgent complaints, or a high volume of customers.
The system must transmit the time, channel, error type, affected volume, and blocked requests if they are available.
Which KPIs should be monitored?
Track availability, response time, drop-offs during incident, redirections to other channels, resumed requests, and post-outage satisfaction.
These indicators show whether the technical incident remained under control on the customer side.
Which mistakes should be avoided?
Avoid silence, overly technical messages, the lack of an alternative, or the loss of context after the service returns.
The customer accepts an incident better when the brand acknowledges it and gives them a clear option.
How can Qstomy help?
Qstomy can use the customer, cart, order, and payment context to respond clearly, and then hand over sensitive cases with an actionable summary.
The chatbot helps the customer understand what is happening, without exposing unnecessary data or promising an unverified action.
Explore AI support, AI sales agent or request a demo.
Key takeaways
Key takeaways
An unavailable chatbot must still communicate clearly and offer an alternative.
What the customer needs to understand
The customer needs to know if the problem is temporary, what to do now, and how to resume later.
The chatbot's proper limit
The chatbot or backup system must transfer emergencies and retain context when possible.
Enzo
July 1, 2026
