Write the Daily Procedure for Your Business Live Chat Solution: One Page Your Team Follows (Free Procedure Builder)
Business live chat solution choices get all the attention, yet the software is the easy half. The hard half is how your people use it: who answers, how fast, what happens at 7:05 pm, and which questions go to the owner. This guide helps you write that down on one page. A free tool turns your answers into a printable procedure and points out the gaps.
⚡ In short
- Software doesn’t decide who replies or how fast. A written procedure does.
- Nine rules cover almost every small team: hours, reply target, first responder, backup, after-hours, escalation, saved replies, closing and review.
- The most common gap is no backup person, so chats wait whenever one person steps away.
- Print the procedure, pin it up, and update it after the weekly review.

Why write it down
Most chat problems are people problems
Think about the complaints you hear about website chat. “Nobody replied.” “They said one thing, then someone else said another.” “I left a message and never heard back.” None of those are software faults. They happen because nobody agreed who does what.
In a small business the agreement usually lives in the owner’s head. It works while the owner answers every chat. It breaks the day a new staff member joins, the owner travels, or chats double during a sale.
A written procedure fixes that. It doesn’t need to be long. One page that answers nine questions is enough for a team of one to ten people. New staff read it on day one. Existing staff check it when unsure. And when something goes wrong, you change the page, not just the person.
What it is not
It’s not a script. Scripts and saved replies cover what to say; our live chat scripts cover that part. The procedure covers who, when and what happens next.
The nine rules
What every business live chat solution procedure covers
Answer each one in a sentence. If you can’t, that’s the gap to fix first.
1. Hours
When chat is staffed. Set the same hours in the widget.
2. Reply target
How many minutes before a first reply. Pick one you can hit on a busy day.
3. First responder
Who picks up new chats by default.
4. Backup
Who takes over during calls, lunch and leave.
5. After hours
What visitors see and who follows up the next morning.
6. Escalation
Which topics go to the owner or a manager.
7. Saved replies
Which answers everyone uses word for word.
8. Closing
How every chat ends: recap, next step, owner.
9. Review
Who reads last week’s chats and updates this page.
Rules 1–4
Hours, targets and who picks up
Hours you can actually staff
Don’t promise 9 to 9 if the person answering leaves at 6. Pick hours when someone is genuinely watching the inbox, and set them as your opening hours. Outside those hours the widget can show an away form instead of an unanswered chat.
A target, not a hope
“Fast” isn’t a target. “First reply within two minutes during chat hours” is. Our response time guide explains what visitors expect. A small team should start with a target it can hit at its busiest hour, then tighten it.
One name, then a backup
Write a name, not “the team”. When everyone is responsible, nobody is. Then write a second name for when the first person is on a call, at lunch or on leave. The team inbox and the Android app mean the backup can answer from anywhere, so it doesn’t have to be someone at the same desk.
Rules 5–6
After hours and escalation
After hours
Decide what a visitor sees at 10 pm and who deals with it. With LiveChatBot, the away form collects an email or phone number, and offline messages can become support tickets. The rule might be: “The first person in each morning clears overnight tickets before opening new chats.”
Escalation
List the decisions staff must not make alone. Typical ones are refunds, discounts beyond a fixed limit, custom quotes above a value, legal or medical questions, and angry complaints. Write what staff say while they check: “Let me confirm this with our manager. I’ll reply here or by email within the hour.”
A clear escalation list protects staff as much as customers. Nobody has to guess whether they’re allowed to say yes.
Free tool
Build your procedure in two minutes
Type your answers, or load the example to see how it works. The tool writes a one-page procedure and lists the gaps.
Fill in how your team will run chat. Short answers are fine. The tool writes a one-page operating procedure and flags gaps.
Business name
Chat hours (e.g. Mon–Sat 10:00–19:00)
First-reply target in minutes
Who answers first (names, comma separated)
Backup person when they are busy or away
Topics only the owner or a manager decides (comma separated)
Who reviews chats each week
Runs only in your browser; nothing is sent or saved.
Rules 7–9
Same answers, clean endings, weekly review
Saved replies for repeated answers
If three people answer delivery questions in three different ways, customers notice. Agree one answer for each common question and store it as a saved reply. The same replies also feed the free keyword bot when no one is online.
A clear end to every chat
Every chat should end with a short recap, the next step and who owns it. “So: I’ve sent the quote to your email, and Priya will call you tomorrow at 11.” That one line prevents most “I never heard back” complaints.
A weekly review with a named owner
Once a week, one person reads a sample of last week’s chats. They look for slow replies, wrong answers, and questions that should become saved replies. Then they update this page. If the reviewer also answers chats, ask someone else to read a few as a check.
Example
Vague rules vs rules people follow
Putting it to work
Test the procedure in your business live chat solution
A procedure only counts if it works on a real day. Try three quick tests.
- The lunch test. At 1 pm, have someone send a chat from their phone. Does the backup reply within your target?
- The 8 pm test. Send a chat after hours. Do you see the away form, and does a ticket appear for the morning?
- The refund test. Ask for a refund in a chat. Does the person answering escalate, using the agreed words?
Fix whatever fails, then update the page. LiveChatBot’s free plan covers the parts the procedure relies on: the team inbox, Android app, opening hours with an away form, tickets, saved replies and Flows, for two websites with 100 visitors per website each month. See pricing and start at livechatbot.in.
Frequently asked questions
What should a business live chat solution procedure include?
Nine things: chat hours, a reply target, the first responder, a backup, the after-hours process, escalation topics, shared saved replies, how chats end, and a weekly review owner.
How long should a business live chat solution procedure be?
One page. If it runs longer, move the wording into saved replies and keep only the who, when and what-next rules on the page.
What’s a realistic reply target for a small team?
Two to three minutes during chat hours is a good start. Set it for your busiest hour, then tighten it once you’re hitting it.
Who should own the weekly review?
Ideally someone who doesn’t answer most chats, such as the owner or a manager. A fresh reader spots slow replies and inconsistent answers.
Does the builder save my answers?
No. It runs in your browser and nothing is sent or stored. Copy or print the result before you close the page.
Software plus a procedure
Set your hours, away form, saved replies and team inbox, then follow your one-page rules. Start free on livechatbot.in.