The fake green dot: business hours, away messages, and honest expectations in live chat

Open almost any SaaS site at 2 a.m. and the chat bubble will tell you the team is online. Type a message and you will get "Thanks! We usually reply within a few minutes" and then nothing until the next business day. Everyone has done this, everyone knows it is a lie, and the tools keep shipping it because "online" converts better in an A/B test than "we are asleep".

We think that trade is wrong, and not only for ethical reasons. A visitor who expects minutes and gets hours is annoyed. A visitor who expects "tomorrow morning" and gets tomorrow morning is satisfied, and often leaves an email that lets you close the loop. This post is about setting up the honest version.

What the widget says and when

Svellyo's widget has three states, and it shows the one that is true.

Someone is online. A teammate has the dashboard open right now. The widget shows your online subtitle, for example "We usually reply within a few minutes", with a green dot. Only claim minutes if that is what you do during your hours.

Nobody is online but the AI is on. The dot is green and the subtitle says the AI assistant replies instantly, which it does. Visitors get real answers from your knowledge base, and a handoff to your team with an honest reply time if the AI cannot help.

Outside business hours, AI off. The dot is grey and your away message shows. New conversations go to a leave-a-message form that asks for an email. The visitor knows exactly what will happen.

The presence check is real. It is based on teammates who have the dashboard open in the last few minutes, not on a schedule alone, so if you are working late on a Sunday the widget says so.

Setting business hours

Under Settings, Hours, pick the days, the times and the timezone. Most solo founders set a wider window than they actually work, which defeats the purpose. Set the hours when you will actually answer, even if that is two blocks of an hour each.

The widget uses these hours for the away state, and Analytics uses them for the "busiest hours" chart so you can see whether your visitors are awake when you are. That chart is worth a look after a month: many makers discover that a third of their chats start in a timezone they never considered, which is the strongest argument for letting the AI cover the night.

Writing an away message people believe

The default is "We'll reply as soon as we're back". It is fine and it is forgettable. Better away messages do three things: say when, say how, and sound like a person.

We're away right now. Leave your email and we'll reply by 9am UK time tomorrow. If it's urgent, mention "urgent" and Aditya gets a ping.

Specific time, specific channel, a real name. Compare with "Our team is currently unavailable. Please leave a message and we will respond at our earliest convenience", which says nothing and sounds like a phone tree.

Two rules. Never promise a time you will miss; "by 9am" is a commitment, so pick a time you can meet on your worst day. And do not apologise twice. One "we're away" is enough; "sorry for any inconvenience" makes people feel like they caused one.

Deciding what the AI does at night

This is the setting that matters most: auto-escalate when offline.

With it off, the AI answers around the clock. Outside your hours, a visitor asking about pricing gets the pricing answer at 3 a.m. and never needs you. Only the handoffs wait for morning. For most products this is the right choice, because the questions that arrive at night are the same questions that arrive by day.

With it on, chats outside your hours skip the AI and go straight to the message form. Choose this when a wrong answer would be costly and you would rather the visitor wait, for example a product where support questions are usually about their specific account and data the AI cannot see.

A middle path many people miss: leave the AI on at night but tighten its handoff threshold for the away state by adding a line to its instructions, such as "Outside business hours, if you are not certain, collect the visitor's email and say the team will reply in the morning". The agent follows it.

The reply-time subtitle is a promise

The line under your team name in the widget, "We usually reply within a few minutes", is the most-read sentence in your support experience and most people never edit it. Edit it. Make it true for your business hours, and know that the widget only shows it when someone is actually online; outside that it shows the away message instead.

Honest options that still convert: "Usually within the hour", "Same day, often faster", "Real people, real replies, within a few hours". A visitor who reads "within the hour" and gets a reply in twenty minutes is delighted. The same reply after "within a few minutes" is a disappointment. Same work, opposite outcome.

What happens to messages left overnight

They arrive in your inbox under Unassigned with the visitor's email attached and the page they were on. When you reply in the morning, the visitor gets an email with your reply and a link back to the conversation, so they do not need to be on your site to see it. If they come back to your site, the widget shows the unread reply with a badge.

This is the loop that makes honesty pay: an evening message with an email and a morning reply is a solved problem. An evening message to a fake "online" widget with no email is a lost customer who thinks you ignored them.

Notifications that respect the hours

Set your email and Slack notifications to match. If you are not going to reply until 9am, a notification at 2am only costs you sleep. In Settings, Notifications, keep "new conversation" email on for the daytime sweep and rely on the morning inbox otherwise. Escalations can stay on, because those are the ones where a visitor explicitly asked for a person, and you may want to know.

The dashboard chime and the workspace badges are for when you are at the keyboard. Nothing in the system will nag you outside your hours unless you choose it.

Measuring it

After a month, look at three things in Analytics. Median first response, which should be about a second when the AI covers nights and a few hours otherwise. The busiest hours chart against your business hours. And the share of conversations that ended with an email left, which tells you how well the away message is doing its job. If that last number is low, the away message is not asking clearly enough.

The short version

Show the state that is true. Set hours you will actually keep. Write an away message with a time, a channel and a name. Let the AI cover the night unless your product genuinely needs a person for every question. Make the reply-time subtitle a promise you can keep. Then let the morning sweep close the loop with the emails you collected.