TL;DR

Business hours tell your chat widget when your team is actually online, so it can promise fast replies during the day and set honest expectations the rest of the time.

Key Points

✓

A business-hours schedule defines weekday and time ranges (often per time zone) when operators are available to handle a [[live-chat|live chat]].

✓

Inside the window the widget can show reply-time expectations and a [[typing-indicator]]; outside it, it switches to an after-hours mode such as an [[offline-message]] or a contact form. [1][3]

✓

Outside hours, leading tools tell visitors when the team will be back rather than just saying "offline" so expectations stay realistic. [3][4]

✓

Schedules let you configure different greetings and responses for during versus outside business hours, instead of one generic message. [1]

✓

Many teams start with a single 9-to-5 block to keep volume predictable, then widen coverage as demand and staffing grow. [2]

✓

Business hours pair naturally with [[asynchronous-messaging]], a [[knowledge-base]], or a [[chatbot]] that can deflect questions when no human is online.

What business hours control

Business hours act as a switch between two states of a chat widget: live and after-hours. During the scheduled window the team is treated as online, so the Chat Launcher can advertise quick replies and a Website Visitor reasonably expects a human soon. Outside it, the same widget shifts to a fallback path, typically an Offline Message, a pre-chat form that captures contact details, or a prompt toward self-service. Vendors like Zendesk let you attach a schedule and then author separate responses for in-hours versus out-of-hours contacts, so the greeting, the details you request, and the follow-up all adapt to the time of day. ^[1] Without a schedule, every visitor gets the same message regardless of when they arrive.

Setting expectations after hours

The point of business hours is honesty about wait times, not hiding the chat. Best-practice guidance is to automatically switch the widget to an offline or email mode outside working hours and to state a concrete return time, for example "We are offline now but will reply by 9 AM tomorrow", alongside a link to a Knowledge Base. ^[3] Intercom's office-hours feature does this directly: when someone messages outside the schedule, the Messenger tells them when the team will be back, rounding the estimate to a clean number. ^[4] This protects First Response Time (FRT) metrics from being skewed by overnight messages and keeps a Conversation from feeling abandoned. It also frames any SLA you publish, since response targets usually apply only within business hours.

Choosing your coverage window

How wide your hours should be is a staffing decision. A common starting point is an average eight-hour workday such as 9 to 5, which keeps incoming chat volume predictable and contained to hours you can actually staff. ^[2] As a Customer Support operation grows it can widen the window, follow traffic across time zones, or move toward 24/7 coverage. Smaller teams often blend a tight live window with Asynchronous Messaging and a Chatbot so the widget still captures leads and answers common questions overnight. In Eloqra, where visitor messages are forwarded to an operator on Telegram and replies flow back to the widget, defining when you are realistically watching that channel is the practical equivalent of business hours, paired with a clear Welcome Message for quieter periods.

Sources & References

Configuring messaging responses and business hours - Zendesk Help ↗

Live chat support: benefits & best practices - Zendesk Blog ↗

Live Chat Best Practices - Hiver ↗

Set your default office hours - Intercom Help ↗

Last updated: June 25, 2026

Related Terms

Offline Message

An offline message is a message a website visitor sends through the chat widget when no operator is available to reply in real time, captured for asynchronous follow-up once a human is back online. It turns an unattended chat into a lead instead of a missed conversation.

First Response Time (FRT)

First Response Time (FRT) is the elapsed time between a customer's first message in a conversation and the first human reply from a support agent. It measures how quickly your team acknowledges an inbound request, not how long it takes to resolve it.

Service-Level Agreement (SLA)

A service-level agreement (SLA) is a documented commitment between a service provider and its customers that defines the standard of support to be delivered, such as how fast inquiries are acknowledged and resolved, and how that performance is measured. [1]

Asynchronous Messaging

Asynchronous messaging is a style of customer conversation that can start, pause, and resume at the participants' convenience, kept in a single continuous thread rather than a real-time session that ends when either party leaves. Customers send a message and pick up the reply later, without staying glued to the chat window.

Welcome Message

A welcome message is the pre-written greeting a live-chat widget shows when a visitor opens it, used to set a friendly tone and prompt the first reply. In Eloqra it is a configurable line of text rendered inside the chat panel before any operator is involved.

Live Chat

Live chat is a real-time, text-based support channel embedded in a website or app that lets visitors message a business and get answers within the same browsing session, without phoning or emailing. It pairs a customer-facing chat window with an agent or bot interface on the other side.

More in Conversational Support & Help Desk

Canned Response

Collect testimonials that build trust

Eloqra gives you a lightweight live chat widget that routes every visitor message to your Telegram — free while in early access.

Get Started Free

More in Conversational Support & Help Desk

Canned Response

Chat Routing

Conversation Assignment

Conversation Tag

Conversational Support

Customer Service

Customer Support

Escalation

First Contact Resolution (FCR)

Help Desk

View all in Conversational Support & Help Desk →

Business Hours