Small teams need fast answers, but not every question should be handled the same way. The simple rule is this: if the answer is already clear in your approved documents, let the team use that. If the question needs judgment, missing facts, or a choice that could change the outcome, send it to a manager. That keeps routine work moving while protecting the calls that need a human decision.
Start with one plain test: is the answer already clear?
If your policy, price list, or task guide gives a direct answer, the team should use that answer first. For example, a refund window, a service price, or the steps to create a ticket are the kinds of things a document can usually cover well.
If the document leaves room for judgment, that is a sign to stop and ask a manager. A good source answer should make the next step obvious, not leave the employee guessing.
Send it to a manager when the question changes the rules
Some questions are not really about finding information. They are about making a choice. That includes cases where a customer wants an exception, the policy is unclear, or two documents seem to disagree.
It also makes sense to escalate when the answer could affect money, a refund, a discount, a service promise, or how a problem is handled. Those are the moments where a manager should decide, not the person at the desk or on the floor.
Use a few clear trigger words for escalation
It helps to give your team simple cues. For example: ask a manager if the customer wants an exception, if the policy does not cover the situation, if the answer depends on the order history, or if the employee is not sure which version of the document is current.
You can also use a manager check when the question is sensitive, unusual, or time-limited. The point is not to escalate everything. The point is to escalate the cases where a wrong answer would cause trouble later.
Keep routine questions out of the manager queue
A manager should not have to answer the same basic questions over and over if the business already has approved guidance. Clear documents should handle everyday things like office steps, service prices, opening hours, or standard refund rules.
When routine questions are answered from the source each time, employees learn faster and managers get more time for the cases that need real judgment. That is where a tool like ObiAnswers fits well: it can point people to the source, then hand off the unclear cases for review.
Give employees a simple way to ask the next question
When a document answer is not enough, the employee should know what to do next. A plain handoff works best: say what is missing, name the manager or team to ask, and keep the question short.
A useful process is: check the source, follow the documented answer if it is clear, and ask a manager if it is not. That keeps the workflow moving without forcing employees to decide alone.
A practical example of the split
Hypothetical example: a customer asks for a refund after the normal window has passed. If the policy says refunds are allowed only within a fixed number of days, the employee can use that answer. If the customer wants an exception, the policy leaves room for judgment, so the question goes to a manager.
In the same way, a question like ‘How do I generate a ticket?’ can usually be answered from a task guide. But if the system behaves differently than expected or the steps do not match the employee’s screen, that may need manager help or a document update.
Make the rule visible in your knowledge library
The best setup is one where employees can see both the source answer and the path for unclear cases. That is easier when your documents are short, current, and labeled well, and when managers can publish approved answers for common exceptions.
Over time, the questions that keep coming back can show you where your library is weak. If the same issue keeps getting escalated, it may be a sign that the policy needs a clearer rule, or that the team needs a better step-by-step guide.