Slack AI Bot Knowledge Base: Why the Bot Said "I Don't Have That Documented"

A Slack bot built to answer staff questions replied to a dispatch question with "I don't have that documented", and the bot was not broken. The company had no official FAQ for it to read, so it could not go out to the team.

This comes from a short-term-rental management company. It applies to real estate operators and property managers who want a bot that answers like a veteran employee. The first step is not the bot.

The situation

The company was building an internal Slack bot that answers staff questions from a company knowledge base. On the call a dispatch question was put to it, the kind of thing a field team asks.

The bot answered with "I don't have that documented", which was the right answer for a bot with nothing to read. A tool that invents a procedure is worse than one that admits a gap. It was also a clear sign the bot was not ready to be handed to staff.

What was broken

No official FAQ existed. A bot can only repeat what has been written down, so the missing document was the whole problem.

Rolling a bot out in that state teaches staff one lesson quickly: this thing does not know our business.

What we decided

We held the rollout and turned the failed answer into a work list.

• Hold the deployment. The bot does not go to staff until the knowledge gaps are closed.
• Ask for an FAQ per functional group. A written FAQ was requested for each function of the business.
• Start from work already done. Earlier audit work and the existing Claude skills were moved into the company account, so the knowledge base begins from material that already exists.

What changed

The call produced no tested improvement yet. What changed is the order of work: documentation comes before deployment. The bot's failed answer became a concrete work item with a written deliverable behind it, instead of a vague feeling that the bot needs more training.

Build the FAQ before the bot

This section is advice for your own company, not a fact about the client. The same order works almost anywhere.

• List your functional groups, such as dispatch, guest messages, cleaning or maintenance.
• For each group, collect the questions staff really ask, in the words staff use.
• Write each answer once, including who decides and what happens next.
• Test the bot with those real questions. Every "I don't have that documented" is a missing entry.
• Roll out to staff when the misses stop.
• Keep a log of every question the bot could not answer, and note when each gap was closed.
• Give each functional group one owner who keeps its answers current.

Frequently asked questions

Why does my Slack AI bot say it does not have something documented?

Because the answer is not in the material the bot can read. That is the bot behaving correctly. Add the missing answer to your knowledge base and test the same question again. If it still fails, the entry is unclear or in the wrong place.

Should I roll out a company knowledge bot before the FAQ exists?

We advise against it. On this account we held the rollout until the gaps were closed, because staff tend to judge a bot on its first few answers. A bot that says it does not know in week one can lose the team before it has a chance to improve.

Who should write the FAQ for a company bot?

The people who own each answer. Here an FAQ was requested for each functional group. One person writes, another checks, and the bot is the test that shows what is still missing.

How do I find which knowledge gaps matter most?

Run real staff questions through the bot and log every miss. The questions staff ask most often, and the ones tied to urgent work like dispatch, go to the top of the list. Misses on rare questions can wait for a later pass.

If you want an internal bot your staff will trust, book a 30-minute AI follow-up and reporting audit. We list the questions your team asks and show you which answers still need to be written down first.