Repeated staff questions: update the guide or fix the workflow?
Handle repeated questions by separating missing guidance, workflow faults and one-off circumstances.
Key points
- Keep questions with the blocked task
- Put guidance where the work happens
- Fix work that still fails with guidance
- Keep one-off replies and their reasons
Overview diagram in preparation
Contents
Keep questions with the task that stopped
A&A perspective
Organizing internal questions means reading each question alongside the task where work stopped.
A&A perspective
If reading an explanation lets someone proceed, review the guide; if it does not, fix the workflow. Reply individually to one-off circumstances, and ask the person who raised the question when the cause is unclear.
A&A perspective
The first task to give AI is a draft of this list. There is no need to extend it to sending replies automatically. The owner reads the original records behind the listed questions and decides what to change.
A&A perspective
One way to start is to select exchanges about a single task from questions already recorded in chat, where staff send each other short messages, or in email.
A&A perspective
Pair each question with the staff member's reply, include a way back to the original exchange, and have AI draft the list.
From the sources
Gumloop, a company providing workflow automation services, describes its own support operation.
From the sources
It summarizes daily inquiries and reviews the past 30 summaries once a month for common faults. It compares that report with its backlog to suggest work to address the issues.
A&A perspective
Automate & Augment (A&A), the author of this article, draws on the approach of grouping questions before choosing what to change.
A&A perspective
We do not adopt the source's daily and monthly cadence as a rule for a small company. Routing questions to the guide, the workflow or an individual reply is also A&A's proposal.
Hypothetical example
Consider a company where staff use AI to draft estimates.
Hypothetical example
'Where is it saved?' and 'I saved it, but I cannot see it' sound similar, but work may have stopped at different points. Missing guidance might explain the former; a failure to save might explain the latter. This is a fictional example.
A&A perspective
The list keeps the original question, the task that stopped, the steps already tried, what to check next, and the responsible person. Have AI retain the original words without merging causes simply because the wording is similar. Headcount and question count alone should not decide what to fix.
Add guidance when an explanation is enough
A&A perspective
When a correct explanation lets someone continue, respond by adding to the guide or changing where it is available. Distinguish an explanation that is missing from one that exists but cannot be found.
From the sources
Gumloop also describes a workflow that examines its support documentation every 24 hours, identifies gaps and drafts missing content. Maintaining documentation is a separate activity from replying to individual inquiries.
A&A perspective
That description alone does not establish whether support-ticket records are direct inputs to the documentation workflow.
A&A perspective
Using an internal question list to suggest additions is our proposed adaptation. A person checks AI's suggested additions against the actual screens and procedures.
A&A perspective
Also decide who changes the explanation and who checks it against the screen after the change. Recording the check date is one way to show which explanation was checked, even when the responsible person changes.
Hypothetical example
In the earlier hypothetical example, someone asks where an estimate draft is saved. The destination is fixed, and reading the instructions enables them to open it. This is a candidate for adding the location and the steps for opening it to the guide.
A&A perspective
If an explanation already exists but questions continue, adding text is not enough.
A&A perspective
A link to the guide could go on the screen where work begins or in the notice area staff already use. Making a guide longer in a place nobody reads still leaves the relevant explanation hard to reach.
A&A perspective
Check whether the next person can carry out the task with the explanation, rather than how many lines were added.
A&A perspective
Check when the task next occurs. If questions stop because nobody has done the task, that does not show the explanation helped.
| Question status | What to check next | Possible response |
|---|---|---|
| An explanation enables progress | Missing instructions or hard-to-find instructions? | Fix the guide or where it is available |
| Following the instructions still fails | Steps taken and actual result | Investigate and fix the workflow |
| Circumstances apply only this time | Could the same circumstances recur? | Reply individually and keep the reason |
| The cause is still unknown | What to ask the person who raised it | Leave unconfirmed and investigate |
Fix the workflow when following the guide still fails
A&A perspective
When a question reports that work still stops despite following the guide, consider investigating and fixing the workflow. Adding explanations alone can leave staff repeating the same unsuccessful action.
From the sources
Anthropic, the developer of the AI system Claude, describes Chatbase, a service for AI-powered customer support.
From the sources
The case study explains that managers can spot several customers struggling with the same connection between business systems and return to the relevant inquiries to investigate.
A&A perspective
A&A considers the ability to return from a summary to the original inquiry useful internally too. Repeated questions do not by themselves prove a fault. Confirm the steps taken and what happened before requesting a fix.
Hypothetical example
In the hypothetical estimate workflow, suppose an employee follows the guide to save a draft, but it does not appear on the responsible person's screen.
Hypothetical example
Keep the content before saving, the time of the action and the displayed result. Simply asking someone to 'fix the estimate AI' does not identify what the builder needs to check.
Hypothetical example
Write the observed behavior separately from the expected behavior in the request.
Hypothetical example
In this example, those are 'it does not appear in the list after saving' and 'the responsible person can open the saved draft.' Confirm the investigation and repair scope with the contractor, then have an internal owner try the same steps after the fix.
A&A perspective
The sources concern companies supplying products to many customers.
A&A perspective
In an internal workflow, even a small number of questions can require attention if work stops. Repairs also consume internal time or contractor fees. The owner weighs the effect on work and the burden of repair, not just question volume.
Keep the reply and reason for a one-off case
A&A perspective
Reply individually to questions that do not require changing shared guidance or the workflow, and keep the reason for treating them as one-off cases. Receiving a question only once is different from its circumstances being one-off.
Hypothetical example
For a hypothetical example, suppose a different person takes over checking estimates for that day only.
Hypothetical example
A question about whom to send an estimate to today gets the name of today's responsible person. Changing the normal guide would instead make instructions for the following days harder to follow.
Hypothetical example
If such handovers will happen again, however, an individual reply is not enough.
Hypothetical example
Shared guidance is needed on where to find the current responsible person. Record the basis for judging this handover to be temporary and note that the judgment should be revisited if the circumstances recur.
A&A perspective
In the list, separate responses into reviewing the guide, fixing the workflow and replying individually.
A&A perspective
Leave questions that cannot yet be classified as unconfirmed, with whom to ask and what to ask them. Even if AI supplies a plausible classification, the owner should not adopt a cause absent from the original question.
A&A perspective
For a small trial, limit the scope to a single internal task.
A&A perspective
Give AI only records approved for that use within the company, excluding customer names and other information unnecessary for the decision. The list is intended to find confusing parts of the work, not to evaluate or monitor employees.
A&A perspective
Decide whether to continue by considering the time to check the list, the effort to gather records and usage fees, as well as repeated questions.
A&A perspective
If replying directly is less work, there is no need to automate. This is a proposal for giving AI question-organization work, not a verified result showing fewer questions or lower costs.
Summary
A&A perspective
Pair questions with the task that stopped and the original records, and have AI draft the list.
A&A perspective
If an explanation lets someone continue, review the guide and where it is available; if following it still fails, review the workflow.
Reply individually to one-off circumstances and keep the reason for that decision. Question count alone does not determine what to fix. A person checks the original records and weighs the effect on work against the burden of changing it.
FAQ
Is AI-based organization useful when a company receives few questions?
It depends on the work involved in answering and checking. If collecting and checking records costs more effort, answering immediately is more suitable. Even a few questions may be worth reading together when the same task keeps stopping.
Can AI update the guide as well?
Initially, limit it to drafting additions. Have the responsible person check that they match the current screens and steps before applying them. Deciding what AI may publish automatically is a separate decision from organizing records.
What if the original question records were not saved?
Start with the records that remain, without guessing historical counts or causes. One option is to begin recording the question's actual wording and the task that stopped when the next question arrives.
Sources & editorial note
Primary pages read for this article. Publication dates below belong to the sources; access dates record our research.
- Supporting the world’s most AI-native companies with a 2-person team
Gumloop · 2026-02-17; updated 2026-03-13
Accessed 2026-10-31 - Chatbase helps companies deliver instant, personalized customer support with Claude
Anthropic · Undated; no publication or update date displayed
Accessed 2026-10-31