E-commerce
July 1, 2026
A customer may request a human at a time when no agent is available: evening, weekend, busy period, public holiday or saturated queue. If poorly drafted, the response can give the impression that the brand is abandoning the customer.
The chatbot must be transparent about availability, collect useful context, offer immediate options and explain when an agent will be able to take over. It must not make the customer believe that a human is coming right away if this is not true.
This guide explains what to say when no human agent is available, without further frustrating the customer.
Summary
Why is this situation delicate?
When a customer asks for a human, it is often because they are stuck, worried, or unhappy. Simply replying "no one is available" can worsen the frustration.
The chatbot must recognize the request and provide a clear follow-up: delay, context collection, potential priority, or an immediate solution if one exists.
The absence of an agent is better accepted when the customer knows what will happen next.

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 information should be provided?
The bot must indicate if human support is closed, busy, or temporarily unavailable. It can provide operating hours or the resumption timeframe if this information is reliable.
It must avoid creating false expectations such as "an agent is coming" if the conversation will not be resumed for several hours.
How to collect useful context?
The chatbot can ask for the order, the reason, the urgency, useful evidence, and the desired solution. The goal is to prepare the file to prevent the customer from repeating everything.
It must remain sober. If the person is already annoyed, a long series of questions can be perceived as an obstacle.
How to handle emergencies?
Certain requests must be prioritized: payment debited without an order, hacked account, highly urgent delivery, dangerous product, exposed personal data, or immediate cancellation.
The chatbot must recognize these signals and apply the planned procedure: priority, emergency channel, immediate instructions, or escalation as soon as reopening occurs.
What can the chatbot resolve on its own?
Even without a human, the bot can answer simple questions: tracking, return policy, invoice, availability, hours, text cancellation, or basic steps.
However, it must say when it reaches its limit. An automatic response must not hide that a human will have to validate the next steps.
Which flow to follow?
The flow must recognize the human request and organize the next steps.
Recognize that the customer wants to speak to an agent.
Clearly explain the availability or response time.
Collect the minimum useful context to prepare the case.
Handle simple actions that the chatbot can resolve now.
Prioritize or transfer emergencies according to the planned procedure.
Which messages should be used?
To be transparent: "No agent is immediately available, but I can prepare your request so that it can be picked up with the right context."
For the schedule: "The human team resumes conversations from [schedule] if this information is confirmed."
For an emergency: "Your request seems urgent. I am gathering the essential elements so that it can be prioritized according to our procedure."
When not to automate more?
The chatbot must avoid prolonging the exchange if the customer is very dissatisfied, if the subject is sensitive, or if the requested decision cannot be made automatically.
In this case, it must prepare a proper file, acknowledge the limitation, and indicate the next step instead of looping indefinitely.
Which KPIs should be monitored?
Track out-of-hours agent requests, prepared files, abandons, detected emergencies, human takeovers, and post-wait satisfaction.
These indicators show whether the chatbot genuinely reduces frustration when the human team is not available.
Which mistakes should be avoided?
Avoid pretending an agent is available, hiding hours of operation, asking too many questions, downplaying the urgency, or leaving the customer without a next step.
The chatbot must be honest, helpful, and organized, especially when human support is temporarily unavailable.
How can Qstomy help?
Qstomy can connect the chatbot to the catalog, stock, orders, support rules, campaigns, and customer context to answer 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
Key Takeaways
When no agent is available, the chatbot must be transparent and prepare for human handoff.
What the customer must understand
The customer must know why they are waiting, what can be done now, and when their request will be processed.
The appropriate limit of the chatbot
The chatbot can collect and resolve simple cases, but it must prioritize emergencies and clearly recognize its limits.

Enzo
July 1, 2026


