Your team asks you 15 questions a day. Here's the real cost.
It's 11:40 p.m. on a Tuesday. Your phone buzzes. It's the night shift: “did the guest in 302 have parking paid for?” The answer is in the manual. Page 14. Nobody has looked at it.
This isn't an edge case. It's the pattern. In a business with rotating shifts, the manager answers between 10 and 20 operational questions a day, and almost all of them are already written down somewhere: the manual, an old email, a WhatsApp group nobody knows how to search.
The math nobody does
Each interruption takes about 3 minutes: reading, getting context, answering, picking up where you left off. At 15 questions a day, that's 45 minutes daily. 22 hours a month. From the most expensive person in the business.
And that's just the time. The worse cost is the other one: the night shift that doesn't ask and makes the wrong call, the new hire who takes three months to work on their own, the customer waiting while someone “goes to check.”
Why the manual doesn't work
It's not that your team is lazy. It's that a 30-page PDF can't compete with asking you. You answer in 20 seconds, tailored to the specific case. The manual demands searching, reading, and inferring. It will always lose against you.
The solution isn't writing more documentation. It's changing the interface: making asking the manual as fast as asking you.
What changes with an assistant that only reads your documents
An internal assistant like Concierge does exactly that: your team asks in their own language, whatever it is, and it answers with what your documentation says, citing the document and the section. If the answer isn't written down, it doesn't make one up: it emails it to you once, you answer it, and it gets added to the manual. Every week the assistant knows more and you answer less.
The goal isn't for the assistant to answer everything on day one. It's for every question to be answered for the last time.
Where to start this week
1. For three days, write down every question you get asked. No filtering.
2. Mark the ones that are already written down somewhere. It's usually around 80%.
3. Gather those documents, however messy they are, and give them an interface your team will actually use.
The third step is ours. The first two you can do today, and on their own they'll show you the size of the problem.