The question that brought this customer to us was about after-hours customer inquiries, and it started with one message. A subscriber of theirs had written at 1.30am to say a subscription had renewed after being cancelled. The chatbot explained the cancellation policy correctly, then offered to connect them with someone. Nobody was there — the support team had gone home at six — and the subscriber waited, gave up, and left a review the next morning.
What they told us
They did not expect round-the-clock support, and neither did their customers. What customers did expect was an honest answer about what would happen next, and a team that already knew the problem when it started work. Instead, the chatbot had promised a person who was not there.
They asked for two things: never promise an agent who is offline, and turn the conversations that need a person into something the team can pick up in the morning without asking the customer to explain again.
How we approached it
The failure was a promise the system could not keep. So we planned the handover around what is actually true at that moment, and around how a team really works the next day:
- Offer live chat only when someone can actually answer it; otherwise offer a ticket.
- Never offer a person at all when no help desk is connected.
- Give the team a short summary with every ticket, and file each ticket exactly once.
- Offer a person before a frustrated customer has to ask.
- Show the business which after-hours questions keep needing a person, so it can answer them in its knowledge.
How it works
Gydr 4.0 lets each help desk work in one of three ways: live chat, tickets, or both.
Live chat when someone is there, a ticket when nobody is. With both on, the visitor chooses. Outside business hours, a ticket takes their question and contact details, and the team replies from the help desk.
The morning starts with a summary. For every ticket Gydr writes a short summary of the conversation, so the agent understands the problem without reading the whole chat. Each ticket is filed once, however many times the network hiccups.
No promise of a person who is not there. A widget never offers to fetch someone when no help desk is connected, and a help desk that checks agent availability only offers live chat when an agent is actually online.
A person offered early. When a conversation is going badly — the customer sounds frustrated, repeats the same question, or goes several turns without a useful answer — the chatbot offers to bring in the team.
Knowing what the night brings. Conversation Topics shows what visitors ask about most and whether they got what they needed.
Where it leaves the team
A customer writing at night gets what the knowledge can answer, and an honest offer of a ticket for the rest. The team starts the day with each ticket and its summary in the help desk. The assistant does not resolve billing problems itself; it makes sure the right person sees them, with the context they need.
Frequently asked questions
How should a business handle after-hours customer inquiries?
Answer what your knowledge covers immediately, and turn the rest into tickets your team picks up in the morning. With Gydr 4.0 a help desk can run live chat, tickets or both, and the visitor chooses.
Will the chatbot promise a person when nobody is online?
No. It never offers to fetch someone without a connected help desk, and if the desk checks availability, it offers live chat only when an agent is online.
What does my team see in the morning?
A ticket in your help desk with the visitor's details and a short summary of the conversation written by Gydr.