A South American Telco

From Fragmented Systems to Seamless Service

Consolidating a nine-system retail operation into one agent workspace.


The Moment

"I just need to sit for a few minutes."

A store customer resting in the seating area during a long counter interaction.

Maria came to the store with her daughter to buy a plan and a device. The interaction took over 30 minutes. She could not stand that long. She kept walking back to the seating area to rest, then returning to the counter, visibly exhausted.

We watched this happen. It was not an exception.


The Problem in Numbers

20 to 40 min
per customer request
7 to 9 systems
per interaction
0
consolidated view of the customer

Research

On the ground, in three stores.

Store observations, live customer interactions. 10 in-depth interviews across 5 roles, from CSRs to a regional manager. Current journeys mapped step by step with the people who run them.


What We Found

Strong culture. Tools that fought it.

Agents took full ownership of every customer, end to end. They compensated for their systems with workarounds: fictive IDs, personal Excel trackers, manual re-typing of data the system already held.

A tooling problem, wearing a process costume.


Method

4 hero flows, the store's most frequent requests. Every step interrogated.

Buy an Accessory

Replace Equipment

Change Plan

Bill Query

For each step: the system used, the pain point, the opportunity.


One Journey Up Close, Replace Equipment

A customer comes to upgrade his old device.

Start
Customer enters the store and asks about a new device.
Promotion & eligibility Excel
Check the offer.
Warehouse chat
Confirm stock availability.
CRM
Change device status, leased to owned.
CRM
Populate order and identification details.
End
Device handed to the customer.

Recurring pain

Agents pull customer information from multiple, disconnected sources. Progress depends on warehouse and supervisor responses.

Recurring opportunity

Provide an integrated, up-to-date device catalog. Present supporting sale information upfront.


Synthesis

What agents need to know upfront.

The same core information came up in every journey we mapped. Six categories recur across all four hero flows.

Redrawn from the research synthesis. A filled dot means the category is needed upfront in that journey.
Information the agent needs upfront Buy an Accessory Replace Equipment Change Plan Bill Query
Customer Profile & Identification
Device Information
Usage
Plan & Services
Bill & Payments
Recent Interactions

One insight solve the information problem once, and every journey gets faster.


Design Principles

The rulebook for every decision that followed.

01

Connect the ecosystem

One integrated flow instead of nine destinations

02

Minimize system interactions

To maximize human ones

03

A shared experience

One screen that works for agent and customer together

04

Automate the routine

So agents handle the complex

05

Surprise me, don't just fix me

Proactive insights, not just data


The Concept

Everything the agent needs, one glance.

Designed for tablet: the agent can leave the desk and serve the customer wherever she is.

The 360 concept dashboard, showing customer identity, billing, lines and devices, usage, cases and orders, and an interaction timeline.
  • Identity and verification
  • Billing at a glance
  • Lines, plans, and devices with eligibility indicators
  • Live usage
  • Open cases and orders
  • Interaction timeline

The Concept in Practice

From a spreadsheet to a device catalog.

The legacy tool: a shared spreadsheet filled in by hand for every upgrade quote.
Before, legacy tool. A shared spreadsheet, filled in by hand for every upgrade quote.
The concept: a searchable, filterable device catalog built into the agent's workspace.
After, the concept. A searchable, filterable device catalog, built into the agent's workspace.

Outcome

Approved. Built. In production.

Concept approved by the client. We designed the hero flows and moved into detailed design. The system is live in production today.

The best design decision was to simplify: fewer systems, fewer steps, fewer workarounds.

← Back to all work