Philippines staffing blog ·

Review the browser tabs an agent needs during a quality sample

Watching the desktop during a quality review shows which systems the work really depends on and which tabs exist only to cover a gap.

Review the browser tabs an agent needs during a quality sample help desk operations illustration

Direct answer

Operational guidance

Start with the ticket, not the desktop

A quality review usually reads the ticket and the reply, then stops. That misses the desktop where the agent worked, which often explains why a reply took so long or why a detail was copied wrong. Ask to observe one case from open to close and note every tab the agent uses. The observation is about the work, not about surveilling the person.

Tell the agent what you are looking for before the session begins. Explain that the review covers tool friction, unclear policy, and missing information, not typing speed. An agent who expects a speed test will hide the very workarounds the review needs to see. Consent and a clear purpose make the observation useful, and they make the findings easier to discuss afterwards.

Record each tab and its purpose

List each tab with the question it answers, such as order status, refund policy, or customer identity. A tab with no clear purpose is either a habit or a missing integration. Group the tabs by the request type they support so the pattern becomes visible. The list should be short enough to review at the end of the case.

Note the tabs the agent opens but does not use, because they still cost attention and screen space. A policy page opened for every case but read for one may be better placed in a decision aid. Ask the agent why the tab stays open rather than assuming it is clutter. The answer often reveals a fear of missing a rule.

Find the duplicated systems

Look for two systems that hold the same fact, such as a customer's plan in the billing tool and in the support tool. When the two disagree, the agent has to choose, and the choice may depend on which tab was open last. Record the disagreement and the source the agent trusted. Duplicated facts are a design problem, not an agent problem.

Check whether the agent copies identifiers by hand between systems. Manual copying produces transposed digits that are hard to spot in a reply and expensive to correct later. A shared identifier or a search link removes the step without changing the workflow. Fix the copy path before coaching accuracy, because a faster agent repeating the same copy step will still make the same error.

Check the copy-and-paste path

Follow one reply from the support tool to the knowledge article to the customer message. Note where the agent switches from reading to writing and whether any text is retyped. Each switch is a chance to lose the customer's wording or the case detail. A good tool path keeps the original question visible while the answer is written.

Check how the agent inserts a saved reply and whether the reply brings its own links or attachments. A macro that depends on a second tab is fragile under pressure. If the reply requires a manual edit every time, the template is not finished. The quality sample should record the edit as a tool gap rather than a personal shortcut.

Watch for tabs that hide a policy

Some tabs exist because the agent does not trust the written policy and wants to check the source. That is a signal that the policy page is hard to read or out of date. Ask which tab the agent would keep if only three could stay open. The answer ranks the real dependencies of the role and shows where the documentation is failing.

Look for a tab that holds a personal note, a spreadsheet, or a chat thread with an unofficial answer. These are often the most accurate source in the room and the least visible to a reviewer. If the note contains a rule the team needs, move it into the knowledge base with an owner. If it contains a workaround, decide whether the workaround is approved.

Compare two agents on the same request type

Observe a second agent handling the same request type and compare the tab sets rather than the individuals. Differences show where the workflow is undefined and where one person has found a better path. Ask both agents to explain the difference before drawing a conclusion. The better path may be a habit that should become the standard.

Avoid turning the comparison into a ranking. The agent with fewer tabs may simply have memorized a rule that the other agent is still learning. The useful question is which tabs the role genuinely requires and which are personal compensation. Answer that question with the team, then update the onboarding checklist so the next agent starts from the better path.

Fix one tool gap at a time

Choose one gap from the observation and fix it before the next sample. A new integration, a corrected link, or a shorter policy page is easier to evaluate than a broad tooling project. Write down what changed and which case it should help. Then observe a second case and check whether the tab disappeared.

Keep the observation notes with the quality record, but remove anything that identifies the agent unnecessarily. The point is to improve the work environment, not to build a performance file. Share the finding with the client when it affects their system or their policy. A tool gap that stays private cannot be fixed by the people who own it.

Close the review with a written map

Write a one-page map of the request type: the systems used, the facts each supplies, the handoffs, and the known gaps. Give it to the training owner and the client system owner. The map is more useful than a list of complaints because it shows how the work actually flows. Update it when a tool changes, and date the version.

Repeat the observation after the next major tool change, not only during a quality cycle. Tool changes are when old tabs return and new ones appear without a plan. A short check at that moment is cheaper than a full review later. The goal is a desktop that matches the documented process, so a new agent can follow it.

Authoritative sources

Related planning pages