One of the most common live chat mistakes is leaving the widget in a permanent "Online" state when no agents are actually available. Visitors start a conversation, wait, get no response, and leave frustrated — sometimes for good. The fix is straightforward: proper business hours configuration and a well-designed offline experience.
This guide covers how to configure both correctly, and how to turn what looks like a limitation (agents not being available 24/7) into a smooth experience that still captures leads.
Why This Matters More Than It Seems
A live chat widget that appears active but is not monitored is actively harmful. It creates a false expectation — the visitor believes someone is there — and then delivers a silence that reads as being ignored.
The alternative — showing an offline state with a clear message and a way to leave a contact — converts a potential frustration into a managed interaction. The visitor knows what to expect, leaves their details, and is no longer disappointed.
Getting this right is not a cosmetic improvement. It directly affects how many inquiries you capture outside of working hours.
Step 1: Define Your Business Hours Accurately
Start with an honest assessment of when agents are actually monitoring the chat inbox and responding within a reasonable time (under 2 minutes). Do not set hours based on when office is technically "open" if agents are in meetings for most of that time.
A typical configuration looks like this:
| Day | Start | End |
|---|---|---|
| Monday | 09:00 | 18:00 |
| Tuesday | 09:00 | 18:00 |
| Wednesday | 09:00 | 18:00 |
| Thursday | 09:00 | 18:00 |
| Friday | 09:00 | 17:00 |
| Saturday | Closed | — |
| Sunday | Closed | — |
Most live chat platforms let you configure this per day and assign a timezone. The timezone setting is critical. If your team is in Bucharest and your server defaults to UTC, your business hours will be off by two or three hours. Double-check this setting after configuration.
Step 2: Write an Offline Message That Works
The default offline messages that come pre-loaded in most chat platforms are generic and forgettable. A message like "We are currently offline. Please leave a message." gives the visitor no confidence that anyone will actually read what they write.
A better offline message:
- Acknowledges that you are unavailable right now
- States specifically when you will be back
- Reassures the visitor that their message will be read and answered
- Optionally provides an alternative contact (phone or email) for urgent matters
Example:
We are offline right now. Our team is available Monday through Friday, 9:00–18:00 (EET). Leave your question and contact details below and we will reply within one business day. For urgent matters, email us at support@yourcompany.com.
This is honest, specific, and sets a clear expectation. It is also far more likely to produce a completed form submission than a vague placeholder.
Step 3: Configure the Offline Form Thoughtfully
When the chat switches to offline mode, visitors should see a form — not a blank screen. This form should collect:
- Name — required
- Email — required (this is how you follow up)
- Message / Question — required
Optional but useful:
- Phone — optional, for visitors who prefer a callback
- Subject or Category — helps route the inquiry to the right agent before anyone has read it
Keep the form short. If someone is reaching out after hours with a question, they are already willing to wait. Do not add friction with a long form that looks like a survey.
Step 4: What Happens After Submission
The offline form submission should trigger two things automatically:
-
A confirmation message to the visitor: "Thanks — we've received your message and will reply by [specific time]." Vague confirmations like "We will get back to you" are less effective than ones with a specific commitment.
-
A notification to the team: either an email to the agent inbox, a ticket created automatically in your help desk, or both. Without this, submissions can fall through the cracks — especially if agents do not check the chat dashboard first thing in the morning.
The best practice is to route offline chat submissions directly into your ticketing system so they are treated with the same priority as other support requests and do not get lost in a separate queue.
Step 5: Handle Multiple Time Zones
If your business serves customers in multiple countries and your support team is in one time zone, you face a mismatch: your business hours in EET are the middle of the night in California.
Options:
Option A: Accept the mismatch. Clearly state your time zone in the offline message ("Our team is available 9–18 EET") so international visitors know when to expect a reply. This is honest and manageable for most businesses.
Option B: Staggered shifts. If your volume justifies it, have agents in different time zones cover different windows. The chat platform should allow seamless handoffs between agents.
Option C: AI / bot coverage. An AI bot can handle FAQ-level questions outside business hours — common questions about pricing, features, availability — and escalate to a human agent during business hours. This is the most scalable solution but requires setup investment.
Step 6: Test Before Going Live
Before your configured business hours take effect, test them from both directions:
- During your configured online hours: confirm the widget shows the chat window and the agent receives new conversation notifications.
- Outside your configured hours: confirm the widget shows the offline form, not an empty chat window.
- Submit the offline form and confirm the agent receives a notification and the visitor sees the confirmation message.
This test takes five minutes and prevents a potentially long period where your configuration is broken and you are not capturing after-hours leads.
Common Mistakes to Avoid
Not setting a timezone. Leads to business hours that are offset by several hours from what you intended.
Using the same offline message forever. If your hours change seasonally (e.g. shorter hours in summer), update the offline message to reflect it.
Offline form submissions going nowhere. Test that submissions actually reach an agent. Set up a shared email or ticket automatically — do not rely on agents to check a separate offline message queue.
Showing offline state during holidays without a message. "We are offline right now" during a one-week office closure will confuse visitors. Add a specific holiday note: "Our office is closed until January 6th. We will reply to all messages when we return."
How Nura24 Handles Business Hours and Offline Mode
Nura24 includes per-day business hours configuration with timezone support for each workspace. The chat widget switches automatically between live mode and offline form mode based on the schedule. Offline form submissions are routed directly into the Nura24 ticket queue, so agents see them alongside other support requests when they start their shift — no separate inbox to check. The offline message, confirmation text, and form fields are all customizable from the chat settings panel without touching any code.