Reducing contact rates by 90% for CX agents

Role Product Designer
Platform iOS & Android
Collaborators Product Manager, Engineers
The Overview

I designed an in-app dispute flow that lets Tamara users raise and track disputes without calling customer support, saving CX agents significant time and removing frustration on both sides.

The Problem

Disputes were flooding CX agents with calls: users came to Tamara before the merchant, couldn't track their dispute, and often lacked the documents agents needed.

The Business Objectives

Cut CX contact for disputes without frustrating users, freeing up agent time and reducing the cost of handling every dispute by phone.

Results
↓ 90%
Dispute-related CX contact rates
The problem

Three recurring problems were driving up contact rates and frustrating both users and agents.

1. Contacting Tamara before the merchant

After a purchase, Tamara has limited visibility into order delivery or condition. If a user is dissatisfied, CX agents escalate the issue to the merchant and await their response. To streamline this process, users should be directed to contact the merchant for order-related issues.

2. No visibility into dispute status

After raising a dispute, users frequently contact CX agents for status updates due to limited app visibility, increasing contact rates and user frustration.

3. Insufficient documents to support users' claims

Users often contact Tamara support without sufficient documents, delaying CX agents' ability to assist efficiently.

CX agent
"Why can't we allow users to manually do this? They usually call us and it takes a lot of time."
CX agent
Iterations & Setbacks

Stakeholders wanted to send every dispute back to the merchant.

Merchant-first routing was the fastest way to cut contact, so stakeholders pushed for a flow that deflected users back to the merchant and hid the option to raise a dispute with Tamara altogether.

I pushed back. Hiding the dispute option would have reduced contacts on paper, but left users with a real problem and nowhere to take it, and they would have called us anyway. Instead, I made contacting the merchant the primary action, while keeping a clear way to raise a dispute with Tamara. Users are guided to the fastest route without losing the ability to ask us for help.

Success

What does success look like?

📉

Reduced contact rates

☺️

Improved user experience

Solution

I designed a structured in-app dispute flow with merchant-first routing, real-time status tracking, and upfront document guidance.

Contact merchant flow
1. Direct users to the merchant first
When users raise a dispute and select order-related issues, they are given the option to contact the merchant directly. This highlights to users that reaching out to the merchant may lead to a faster resolution.
Dispute status tracking
2. Full visibility of dispute status
Users can view and track the status of their dispute at every step of the process, ensuring full visibility of the system.
In-app dispute flow
3. Raise a dispute directly in the app
Users can easily raise a dispute directly within the app, eliminating the need to contact support through multiple channels for assistance.
Document upload guidance
4. Clear document guidance upfront
Clearly informing customers about the required documents for their dispute helps them identify what is needed and upload the files accurately without errors.
End-to-End Flow

The buyer protection flow, from start to finish

How a user raises a dispute in the app, from choosing what went wrong to tracking the outcome.

Edge Cases

Designing beyond the happy path

I designed and documented the edge cases across the flow for developer handoff.

Edge cases handled in the dispute flow
Impact
90%

After launching the in-app dispute flow, we reduced user contact rates regarding disputes by 90%. Almost all disputes are raised through the app.

Learnings

My key takeaways and learnings

Look past the customer metrics
Success metrics usually, and rightly, centre on the customer. Looking at the experience of our CX agents surfaced the process inefficiencies that were driving contact in the first place.
Guide users, don't trap them
Deflecting users to the merchant worked because they could still reach us. Making the fastest route the obvious one, not the only one, cut contact while keeping users' trust, and delivered value for employees, users and the business.