Chatting Service Promise: Write the Reply Times, Hours and Rules Your Customers Can Count On (Free Promise Builder)

Chatting service quality, from a customer’s point of view, comes down to a few questions: when is someone there, how fast will they reply, and what happens if the answer isn’t quick? Most small businesses never write these answers down, so every agent answers them differently and customers can’t tell what to expect. This guide shows how to write a short service promise for your website chat, turn it into internal targets your team can work to, check that your team can keep it on your busiest hour, and handle the days you miss it.

⚡ In short

  • A service promise is three or four sentences: hours, first-reply time, after-hours handling and what happens to slow questions.
  • Write a public version for customers and an internal version with targets for your team.
  • Check the promise against your busiest hour, not an average one.
  • Promise a little less than you usually achieve, and beat it.
Chatting service in LiveChatBot: the LiveChatBot shared inbox with a conversation open
How it looks in LiveChatBot: the LiveChatBot shared inbox with a conversation open.

Why write it down

Unspoken promises get broken

Every business with a chat window is making a promise, whether it writes one or not. A bubble that says “We’re here to help” suggests someone is there right now. A welcome message that says “Ask us anything” suggests any question will be answered. If nobody replies for twenty minutes, the customer feels let down, even though nobody ever said twenty minutes was too long.

Writing the promise down fixes this from both ends. Customers see clear hours and a realistic reply time, so they know whether to wait, leave a number or call. Your team gets a shared target, so the new hire and the owner answer at the same pace and close chats the same way.

It also forces useful decisions. Do you cover Sundays? What happens to a chat that comes in at 6:55 pm when you close at 7? Who owns a question that needs a supplier’s answer tomorrow? These questions come up every week anyway; a written promise means they’re answered once.

Large companies call this a service level agreement and write pages of it. A small business needs four sentences and a short list of internal rules. The free builder below writes both from a few numbers.

The four parts

What a good chat promise covers

1

Hours

Days and times someone reads chats. Use the same hours in your chat tool’s opening hours setting.

2

First reply

How quickly a person replies during those hours. This is what customers notice most.

3

After hours

What happens outside hours: leave an email or phone number, and when you’ll reply.

4

Slow questions

What happens when an answer needs checking: you say how long, and it becomes a ticket with an owner.

Leave out promises about total resolution time for every question. Some problems take a supplier, a courier or a refund cycle to solve, and a promise you can’t control will be broken. Promise to reply, to tell the customer what happens next, and to follow up.

Free tool

Build your service promise and check it

Enter your hours, team and busiest-hour numbers. The builder writes the customer-facing promise, internal targets, and a simple capacity check for your peak.

Describe your chat team honestly. The builder writes a customer-facing service promise and internal targets, then checks whether your team can keep it at your busiest hour.

Runs only in your browser; nothing is sent or saved. The capacity check is simple arithmetic, so treat it as a sense check, not a forecast.

Finding your numbers

Where the inputs come from

The builder needs a few numbers. Here's how to find them without guessing.

Busiest hour

Look at your last four weeks of chats in the inbox and count chats by hour for your two busiest days. Many businesses find a clear peak: lunchtime for office workers, evenings for consumers, or the hour after a promotional message goes out. Use the busiest single hour you saw, not the average.

Minutes per chat

Pick twenty recent chats that needed a person. Note how long each took from first reply to last message, and take the middle value. Routine questions may take two minutes; order problems may take ten.

Chats at once

Experienced agents can usually run two or three simple chats at the same time. Complicated chats, such as complaints or technical problems, need full attention. If you're not sure, start with two.

First-reply target

Check what you actually achieve now on a normal day, then set the promise a little above it. If you usually reply in three minutes, promise five.

If you don't have chat history yet, start with your best guesses and revisit them after a month. The point is to have a number your team can check against, not a perfect forecast.

Busy hours

When the check says your team is overloaded

If the busiest-hour check shows more chats than your team can handle, you have four options, and most businesses use a mix.

Answer routine questions automatically. If a third of your busiest-hour chats are about delivery times, payment methods and opening hours, saved replies and an AI assistant can answer them instantly. LiveChatBot's AI Agent answers from the knowledge you give it, and the free keyword bot answers from saved replies when the AI isn't available. That frees people for chats that need them.

Add a person at the peak only. You don't need two people all day. One extra person for the busiest two hours, perhaps someone from sales or the owner, often closes the gap. The Android app lets them answer from the shop floor.

Make the promise slower at the peak. Some businesses say “usually within 5 minutes, up to 15 at busy times”. It's honest and customers accept it.

Spread the peak. If the rush follows a promotional message, send it in two batches an hour apart.

Whichever you choose, rerun the check. A chatting service promise that fails at the peak fails exactly when the most customers are watching.

Internal rules

Turning the promise into daily habits

The public version of your chatting service promise is short. The internal version tells your team how to keep it. Good internal rules are specific enough to check:

  • First reply within the target, even if it's only “Thanks, let me check that for you.” A quick holding reply buys time; silence doesn't.
  • Tell the customer how long a check will take. “Give me two minutes while I check stock” is better than disappearing.
  • Anything not solved in the chat becomes a ticket with an owner before the chat ends. LiveChatBot's tickets have open, pending and solved statuses and owners, and the customer can see their ticket page without logging in. See turning a chat into a ticket.
  • The last person on shift checks the inbox at closing. No chat waits overnight with no reply.
  • After-hours messages are answered first the next morning, in the order they arrived.
  • Use saved replies for common answers so the facts are the same whoever replies. Our saved replies guide covers setting them up.

Print the list, or pin it in your team chat. New staff should read it on their first day.

Showing the promise

Where customers should see it

A promise that sits in a document nobody reads doesn't set expectations. Put it where customers meet your chat:

  • The welcome message. One line is enough: “We reply in a few minutes, Mon to Sat, 10 am to 7 pm.”
  • The away form. Outside hours, the form should say when you'll reply: “Leave your number and we'll call by 11 am tomorrow.”
  • Your contact or chat page. The full four-sentence promise fits here.
  • Order confirmation emails. A line with your chat hours tells customers when help is available.

Keep the hours consistent everywhere. If the website says 10 to 7, the chat tool's opening hours should say 10 to 7, the Google Business Profile should say 10 to 7, and the welcome message should match. Mismatched hours are one of the most common reasons customers think nobody is there.

For the first line inside the chat, see our welcome message guide.

When you miss it

A recovery script for slow days

Every team misses its target sometimes: someone is ill, a courier fails and fifty customers ask at once, the internet drops. What matters is what customers hear.

Apologise briefly and specifically. “Sorry for the wait, we're busier than usual this morning.” Not a paragraph.

Answer the question fully. The apology is worth nothing if the answer is rushed.

Change the promise for the day if you need to. If you know the next few hours will be slow, update the welcome message: “We're busy today; replies may take up to 20 minutes.” Customers forgive a warned delay more easily than a surprise.

Look at the cause afterwards. Was it a one-off or a pattern? If the same hour is slow every week, the promise or the staffing needs to change.

Keep a simple weekly log: the target, the share of chats you met it on, and the reason for misses. After a month, the pattern usually shows you the fix. Our guide to live chat response time has more on measuring it.

Examples

Promises for three kinds of business

These are illustrative promises written with the builder. Adapt them to your own hours and team.

🎓

Solo tutor

“I answer chats Monday to Saturday, 4 pm to 9 pm, usually within 10 minutes. Outside these hours, leave your number and I'll reply by the next evening.”

🛍️

Two-person shop

“We answer chats every day, 10 am to 8 pm, usually within 5 minutes. After 8 pm, leave your email and we'll reply by 11 am. If we need to check stock, we'll tell you how long it will take.”

🏥

Clinic front desk

“Our front desk answers chats Monday to Friday, 9 am to 6 pm, within 15 minutes. For medical emergencies, please call or visit the nearest hospital. Booking questions outside hours are answered the next morning.”

Getting started

Write it today, check it monthly

Run the builder with today's numbers, paste the promise into your chat page and welcome message, and set the same hours in your chat tool. Share the internal rules with your team. After a month, check your log and adjust: tighten the promise if you're beating it easily, loosen it or add help at the peak if you're not.

A clear chatting service promise is the cheapest service improvement there is: it costs nothing and changes how every customer feels about the wait. LiveChatBot's free plan includes opening hours with an away form, saved replies, tickets with owners and the Android app, for two websites with 100 visitors per website each month. See pricing and start at livechatbot.in.

Frequently asked questions

What should a chatting service promise include?

Your chat hours, the usual first-reply time, what happens outside hours and how questions that need checking are followed up.

How fast should a first reply be?

Fast enough that customers wait rather than leave, and slow enough that your team can keep it on busy days. Promise a little above what you usually achieve.

Should I promise how long it takes to solve a problem?

Usually not. Promise to reply, explain the next step and follow up. Many solutions depend on suppliers or couriers you don't control.

What if my busiest hour is more than my team can handle?

Let saved replies or an AI assistant answer routine questions, add a person at the peak, or promise a slower reply at busy times.

Where should customers see the promise?

In the welcome message, the away form, your chat or contact page and your order emails, with the same hours everywhere.

Keep reading

Related guides

📘

Chatting Page for Your Website: Build a Dedicated “Chat With Us” Page That Visitors Actually Use (Free Copy Builder)

Read the guide →

🧭

Chatbots in Artificial Intelligence: How Much AI Is Really Inside? A 6-Level Scale and a Free Behaviour Test

Read the guide →

🛠️

Companies With Chatbots: 9 Patterns Big Brands Use That a Small Business Can Copy This Week

Read the guide →

Make a promise your team can keep

Set honest hours, a realistic reply time and a follow-up rule for every chat. Start free on livechatbot.in.