Back to News

BPOAI News / AI Vendors & Tools

Handled Isn't Resolved: What BPO Performance Metrics Can Miss

A customer's issue can remain open long after the support ticket closes. Michelle Giray asks what an operation should require as evidence before it calls an issue resolved.

Share on LinkedIn
Michelle Giray, Independent CX and Quality Consultant
Michelle Giray, Independent CX and Quality Consultant · Photograph: courtesy of Michelle Giray

A customer's issue can remain open long after the support ticket closes.

Consider a hypothetical refund enquiry. The agent verifies the account, explains the timeline, documents the conversation, and closes the ticket. The interaction passes its Quality evaluation.

A week later, the customer calls again. The refund is still waiting for an exception approval from another team.

The agent handled the conversation correctly. The customer is still waiting for the outcome.

For BPO leaders and enterprise buyers, this raises a useful question: what does the operation require as evidence before calling an issue resolved?

“The agent handled the conversation correctly. The customer is still waiting for the outcome.”
Michelle Giray, November 2026

The outcome

Define resolution around the reason for contact

Quality scores, service levels, and customer satisfaction measures provide useful evidence about service performance. Whether they also demonstrate resolution depends on what they measure and when.

An accurate explanation may fully resolve a policy enquiry. An overdue refund requires action. A disputed charge requires a decision and, where appropriate, a correction.

“Resolution does not mean granting every request. It means reaching a valid outcome for that issue.”

Resolution does not mean granting every request. It means reaching a valid outcome for that issue, with a clear explanation and any applicable review options.

Start by defining that outcome. Then identify the evidence needed to confirm it.

AI

Apply the same standard to AI

Imagine an AI assistant that explains the refund policy accurately and ends the conversation without a human transfer. That could be a complete outcome for someone asking about the policy. For someone whose overdue refund needs intervention, work remains.

Evaluate whether the workflow recognised that need, initiated the right action, and passed enough context to the person or team responsible.

Keep the stages visible: an answer delivered, an action initiated, and an outcome confirmed. Recording each stage separately makes it possible to see where progress stops. A completed conversation alone cannot establish that a refund arrived.

“A completed conversation alone cannot establish that a refund arrived.”
Michelle Giray, November 2026

Ownership

Make responsibility visible across the handoff

In the refund example, the agent may have no authority to approve the exception. The BPO could meet its contracted responsibilities while the customer waits for a client-owned team to act.

The review must follow that dependency. Identify the outstanding action, the team with authority to complete it, the expected timeframe, and who will keep the customer informed.

That gives BPO leaders specific evidence for client discussions. It also gives enterprise buyers a way to examine whether their service agreements and internal processes support the customer outcomes they expect.

“Accountability should sit with whoever can take the next required action.”

Accountability should sit with whoever can take the next required action. Penalising an agent for an approval they cannot control leaves the underlying delay untouched.

Know a BPO leader who should read this?Share on LinkedIn
BPO Leaders is written by executives from BPO companies, in their own words. Our editorial team sends you a topic.Write for bpo leaders

Try it

Test one recurring issue

Choose one contact reason, such as delayed refunds. Review a sample of cases from the first enquiry through to the final outcome, including related contacts across channels.

Ask three questions:

  1. What outcome did the customer need?
  2. What evidence confirms that outcome happened?
  3. Who owns the next step when it has not happened?

Compare the findings with the reported case statuses and Quality scores. Investigate the gaps: an early closure rule, a missing approval, an incomplete handoff, or an outcome that happened but was never recorded.

Check the evidence carefully. No further contact does not prove success, and a repeat contact may concern a different issue.

Use the findings to agree on a specific change with the team that can make it. Then review another sample to see whether the gap has narrowed.

The question to ask

When your dashboard says “resolved,” can you show what happened to the customer's issue?

The lesson for BPO leaders is a practical one. Pick one recurring issue this month, follow a sample of cases to their real outcome, and agree on one fix with the team that owns the next step.

This is a guest article. The views are the author's own. The refund scenario is hypothetical, not a client case study. The BPO AI Editorial Team reviewed it for publication.

About the author

Michelle Giray is an independent CX and Quality consultant with 19 years of experience across BPO and customer operations. Her work spans Quality frameworks, vendor governance, reporting automation, and performance improvement, including executive consulting across 32 retail and e-commerce programs. She focuses on connecting Quality insights with operational decisions and customer outcomes.

Related

BPO Leaders is written by executives from BPO companies, in their own words. Our editorial team sends you a topic.Write for bpo leaders

Share this story

Know a BPO leader who should read this?

Share it with your network on LinkedIn in one click.

Share on LinkedIn