A chatbot can answer a question while the team is away. Decide which questions it can actually settle, and what happens to the rest.
Start with the access the chatbot has. A helpful reply should make that limit easy to understand.
| The question | While the team is away | What needs the team |
|---|---|---|
| Hours, location or a published policy | Answer from the current source, including the conditions that matter. | Keep that source current when hours or policies change. |
| “Where is my order?” | Explain how to find the tracking information or reach the team. Say if the chatbot cannot see this order. | Check the actual record and follow up through the stated route. |
| A refund, cancellation or booking change | Explain the published process. Distinguish requesting a change from completing it. | Make the decision or perform the action that needs account access and authority. |
| Something time-sensitive | Give the business's actual contact route and staffed hours. Use a monitored out-of-hours route only if one exists. | Own the follow-up. A message in an unattended inbox is still waiting. |
If your chatbot has connected tools, expand this table to name the actions it can perform and how success is confirmed. An explanation of a process does not complete the process.
These conversations and the business behind them are fictional. The example repair shop is staffed Monday–Friday, 09:00–18:00, and Saturday, 10:00–16:00. Its chatbot has help content, but no live job or booking data.
Source: the shop's current opening-hours page.
Visitor“Are you open on Sunday?”
“The shop is closed on Sunday. It opens on Monday at 09:00.”
The answer gives the relevant hours. There is no reason to turn a simple question into a callback request.
Source: the contact process. The chatbot cannot inspect repair jobs.
Visitor“Is my bike ready to collect?”
“I can't see individual repair jobs. Use the contact page to send your job reference and preferred contact details. The team reads requests during the shop's staffed hours.”
This gives a route to the people who can check. It makes no claim that the bike is ready or that a request has already been sent.
Source: the booking policy. Changes need confirmation from the team.
Visitor“Move my Monday appointment to Tuesday.”
“I can't change a booking here. Send the appointment details and requested date through the contact page. The team will check availability during staffed hours and confirm whether it can be moved.”
The existing appointment still stands until the team confirms a change. If the chatbot can submit a request, its reply should reflect whether that submission actually succeeded.
Write down the staffed hours and time zone, which inbox or form receives requests, and who checks it. Match any stated response window to what the team can deliver.
If nobody monitors the channel overnight, make that clear in the reply. Customers need to know whether they are asking someone who is available now.
At the next shift, the owner checks the request, confirms what still needs doing, and follows up. A useful record keeps the original question, the route used and the next action together.
Look for repeated gaps in the help content. Keep one-off account questions separate from information that could help the next visitor.
The editable template has space for hours, contact routes, answer boundaries and follow-up responsibilities. Fill it in with the people who actually pick up the requests.
Download the coverage planMarkdown text · opens in a text editor
The coverage plan works on its own. The resources below cover a chatbot on your website, customer evidence, and a separate topic: how the business appears in search answers.
I contribute to Beamtrace at Elfsight. These tools concern search answers, rather than support conversations on your own website.
The audit and research briefings are my independent work. These readings concern search measurement.