● OMNI-CHANNEL AGENT WORKSPACE

Redesigning the Contact-Center Workspace

scroll on — the GIFs are the fun bit ↓

Turning a legacy, 12-year-old agent interface into an AI-assisted workspace used across millions of customer conversations.

ROLE
Sole IC designer
TEAM
Director of PM (AI) · ECC Engineering
TIMELINE
6 months
SCOPE
Research · concept · design · handoff
MY SLICE
I led research, concept, UX and handoff end to end — the four-panel model and the AI-in-the-flow patterns are mine. ECC engineering owned the build; PM owned scope and rollout.
THE PROBLEM
A 12-year-old agent tool, a floating dialer and a browser full of tabs. Agents lost context mid-call, and deals were slipping on UX maturity.
WHAT I DID
Sat with agents on the floor, sorted the work into a four-panel layout, put AI inside the flow, and took it through five passes to a handoff-ready prototype.
THE RESULT
Used by 10,000+ agents every day. 30% lower average handling time, 18% higher first-contact resolution, 28% fewer escalations and +7.5% CSAT.
app.exotel.com — agent workspace · prototype
Prototype walkthrough: an agent on a live voice call clicks the WhatsApp interaction in the list and the workspace switches to the chat, with customer details and past interactions staying beside the conversation, then switches back to the call
↑ prototype walkthrough — one customer, two channels. Voice and chat sit in the same interaction list, and the customer context stays beside the conversation.
( WHERE IT LANDED )

The impact, first

10,000+
agents use the new workspace every day
DAILY USAGE · TRACKED IN AMPLITUDE
EFFICIENCY
20%
faster time-to-information
4%
less tab switching
13%
fewer clicks / interaction
30%
better disposition compliance
EFFECTIVENESS
30%
lower average handling time
18%
higher first-contact resolution
28%
fewer escalations
BUSINESS
↑ Higher tender win rate
↓ Lower churn risk
↓ Reduced training time
↑ Better agent retention
CUSTOMER
+7.5%
higher CSAT
−2%
lower repeat-contact rate
BEYOND THE NUMBERS
IN DAILY USE
Shipped to production
Used by 10,000+ agents every day, tracked in Amplitude.
TESTED WITH CUSTOMERS
Prototype tested externally
Run with customers including redBus, Slice, Razorpay, HSL and Blue Dart.
AI THAT SHIPPED
Every AI pattern is live
Sentiment, auto-disposition, context transfer, alerts and summaries all reached agents.
GROUNDED IN THE FLOOR
Built from watching agents
Floor visits with 300+ bus-travel agents across 3 cities and 200+ fintech collections agents, plus three more industries.
RESEARCH TO FEATURE
Supervisor asks shaped the design
Idle-agent alerts, customer-indexed recordings, self-service DID rotation and earlier barge-in each trace back to a quote from the floor.
( WHAT AN ENTERPRISE CONTACT CENTER ACTUALLY IS )

You order food. Your order is delayed. You tap Help & Support.

A bot asks questions. It tries. It fails. You get transferred to a human agent…
IN SECONDS, THE AGENT MUST
Instantly understand what went wrong
WHILE YOU WAIT ON THE LINE
See order details, payment status & delivery-partner notes
WITHOUT ASKING AGAIN
Know what the bot already asked and promised — then resolve, fast
( THE STARTING POINT )

A Once-in-a-
Decade Reset

GOOGLE WEB TOOLKIT · 12 YRS

The workspace had run on Google Web Toolkit for over a decade. Patches kept it alive, but the architecture blocked modern interaction patterns, performance work, and any real UX ambition.

THREE PRESSURES FORCED THE REBUILD
01 Rigid workflows with fragmented context.
02 A widening feature gap against Sprinklr and Intercom.
03 Deals slipping on UX maturity.
( WHO IT'S REALLY FOR )

The Agent Is the System

Agents hold emotional, high-stakes conversations, switch tools constantly, and carry the brand in every call. The workspace wasn't a feature to them — it was their command center. Designing for them meant protecting focus, not just adding capability.

“High-stakes, emotional
“Constant tool-switching
“Carries the brand, every call
( THE INDUSTRY SHIFT )

AI Changes the Role of the Agent

01
Bots handle frontline queries

Verification, status checks and repetitive intents get automated before a human ever picks up.

02
Humans handle complex, high-empathy cases

What reaches an agent is now harder, more emotional and higher-stakes by default.

03
State, Vibe & Intent become critical
State · 3 complaints in 1 week Vibe · frustrated Intent · delivery delayed
( THE REALITY ON THE FLOOR )

One Customer, Six Broken Tools

Before designing anything, I sat next to agents. What I found wasn’t one bad screen — it was a stack of disconnected tools: a bright legacy CRM, a bolt-on dialer floating on top of it, and a browser full of tabs. These are photos I captured sitting next to agents — de-identified.

legacy CRM + a dialer floating on top · captured on a visit
Legacy CRM with a dialer floating over the case record, de-identified
The contact-centre floor during a customer visit
Legacy dialer during a connected call, de-identified
↑ real screens from a floor visit — URLs, agent & customer details removed under NDA
WHAT AGENTS ACTUALLY BATTLED
1The full customer name is cut off — you minimise the window just to read who you’re talking to.
2The dialer opens at max height and floats on top of the record — the more it shows, the less of the case you can see.
3Two scrollbars fight each other — constant confusion about which one moves the thing you need.
4Fields are so dense agents zoom in and out mid-call just to read a value.
5The customer’s preferred language isn’t visible while transferring — so calls land with agents who can’t speak it.
6Every disposition is typed twice — once in the dialer, once in the CRM.
( RESEARCH )

How We Pressure-Tested the Hypothesis

Paired large-scale behavioral analytics with on-ground qualitative work — then validated the patterns beyond dashboards with enterprise clients (names bound by NDA).

FLOOR VISITS & SHADOWING ACROSS
Bus travel · 300+ agents, 3 cities Fintech collections · 200+ agents EV mobility · 5 languages Edtech counselling Digital payments
▦Quantitative — Amplitude
Interaction opened
Hunting for context
Switching tabs
Reply sent
shape of the funnel we analysed — illustrative
screen replays event tracking funnel analysis
Found the drop-offs, tab-switching, and time-to-information bottlenecks.
◉Qualitative — on the floor
agent shadowing supervisor interviews live-floor observation
Validated the patterns beyond the dashboards, with real enterprise clients.
ON THE FLOOR — WHAT WE HEARD, AND WHAT IT BECAME
WHAT WE HEARD WFM analyst · fintech collections floor
“We change 6 DIDs in the morning and 6 in the evening. If the DIDs aren’t changed, our call connectivity drops, and productivity is lost.”
→ WHAT IT BECAME
Self-service DID rotation — spam-hit numbers auto-detected, no support ticket.
WHAT WE HEARD Quality & escalations lead · fintech collections
“If I remove an agent from a campaign, their calls disappear. If a customer escalates from three months ago, we re-add the agent just to hear the recording.”
→ WHAT IT BECAME
Unified recording search — organised by customer, not campaign; survives agent moves.
WHAT WE HEARD Collections supervisor · fintech floor
“We can only spot idle agents by downloading reports and reading them by hand. If it flagged them live, we could act immediately.”
→ WHAT IT BECAME
Real-time alerts on the Home dashboard — idle, silence and break-misuse surface live.
WHAT WE HEARD Observed · edtech counselling floor
“Supervisors can’t barge, whisper or snoop for the first 3–5 minutes — by the time we join, the context is already gone.”
→ WHAT IT BECAME
Earlier intervention + conference coaching — the agent stays on the line, not dropped.
( THE LANDSCAPE )

Where We Stood,
Where the Field Was Going

Agents weren’t using one product — they were stitching several together. Meanwhile competitors were shipping the exact capabilities that stack couldn’t. I benchmarked both to find where a redesign would actually move the needle.

THE STACK ON ONE DESK
Legacy CRM
The case record — bright, dense, and never sized for a call.
Bolt-on dialer
A separate toolbar floating on top — its own dispositions, its own scrollbar.
WhatsApp, on the side
Supervisors defaulted to it for files and screenshots — the built-in chat didn’t cut it.
A separate journey platform
One floor spent ~₹35L a year on a third-party tool just for WhatsApp campaigns & routing.
COMPETITOR RESEARCH · SCREEN BY SCREEN

Before drawing anything, I collected the agent-facing screens of seven contact-center platforms into one board and went through them column by column: how each handles the call, the customer record, and the channels around it.

SprinklrGenesys CloudCisco Contact CenterNice CX OneIntelliconZoom Contact CenterSalesforce
Figma research board with screens collected from Sprinklr, Genesys Cloud, Cisco Contact Center, Nice CX One, Intellicon, Zoom Contact Center and Salesforce, one column per platform
The research board in Figma · one column per platform
CAPABILITY BENCHMARK
✕absent ◐partial ✓shipped
CAPABILITY
LEGACY STACK
THE FIELD
NEW WORKSPACE
Unified customer context, one view
✕
9 tabs + floating dialer
◐
Sprinklr · Intercom
✓
4 panels, always on
In-call AI summaries & transcription
✕
manual notes
✓
yellow.ai · verloop
✓
in the flow
Real-time supervisor alerts
idle · silence · break misuse
✕
download reports
◐
colour thresholds
✓
live on Home
Recording search by customer
across campaigns
✕
re-add the agent
◐
campaign-scoped
✓
customer-indexed
DID spam auto-rotation
✕
manual tickets, 2×/day
✓
competitors offer it
✓
self-service
Early barge + conference coaching
✕
3–5 min lockout
◐
agent dropped
✓
3-way, stays on
Single disposition write-through
✕
typed twice
◐
varies
✓
write once
↑ competitor & tool names are the third-party platforms these floors already ran; client identities anonymised under NDA.
( DESIGN GOALS )

What the redesign had to do

Research and the benchmark turned into six goals. The decisions below trace back to them.

GOAL 1
Context in one view
The agent should understand the customer before the first word, without opening another tab.
SEE · FOUR PANELS
GOAL 2
Never lose a live conversation
Moving to a CRM record or a KB article must not drop or swap the interaction in progress.
SEE · FLOATING PIP
GOAL 3
Keep SLAs and reporting intact
Whatever the interface unifies, the backend still tracks and reports at the interaction level.
SEE · CHANNEL-CENTRIC MODEL
GOAL 4
Fit the agent's real desk
Work as a full workspace and as a slim toolbar docked inside the CRM agents already use.
SEE · PASS 03
GOAL 5
Be adopted, not imposed
Agents had to want to move, so the rollout needed nudges and a phased path, not a forced switch.
SEE · ADOPTION
GOAL 6
Keep monitoring out of the call
Supervisor and performance signals live between interactions, never on top of a conversation.
SEE · HOME DASHBOARD
( INSIGHTS → DECISIONS )

What We Tried,
What We Killed

Every decision earned its place. The directions we axed mattered as much as the ones we shipped — here's the spine of it.

AXED — explored, then cut SHIPPED — made it to agents
INSIGHT A · COGNITIVE LOAD

Multi-session handling was fragmenting attention

Floating PiP windows silently swapped customer context — leading to accidental context switches, errors, and slower resolution. The problem was fragmented attention, not volume.

✕ AXED
Customer-Centric Inbox

One interaction list per customer; one consolidated transcript across voice / chat / email. Felt clean — but the backend defines SLAs and reporting at the interaction level. A fully unified thread would break operational accountability.

✓ SHIPPED
Channel-Centric Model

Kept interaction-level tracking, but structured interactions under the customer name — channel-specific transcripts, SLA-safe disposal flows, a UI built to evolve toward full unification later. Balances operational reality with experience ambition.

SLA-safe grouped by customer
INSIGHT B · CONTINUITY

Agents kept losing the thread between sessions

✕ AXED
Persistent avatars in header

Showed presence, not state. Agents still had to click back, re-orient, and re-scan history. It preserved access, not continuity.

✓ SHIPPED
Floating PiP, done right

A minimized live-interaction window that persists across navigation, expands instantly, and keeps real-time context — instead of silently swapping it.

Rohan K. · live
02:14 · voice
⤢
✓ SHIPPED · SEEN IN THE REAL UI

Live interactions collapse into a row of avatars in the top bar; one tap re-expands the full picture-in-picture window — transcript, timers and call controls intact — so an agent can open a full-page CRM or KB article and never lose the thread.

Collapsed live interactions as a row of avatars in the top bar, over the closed-interactions page
collapsed — presence in the top bar
Expanded floating interactions window with live call controls and conference list, over a full-page view
expanded — full context, over any page
STATE, NOT A TAB
The interaction is treated as persistent state, not a page — it follows the agent anywhere in the product, minimized or expanded.
NOTHING GOES SILENT
Collapsed avatars still carry live signals — channel, timer and unread badges — so a waiting customer is never invisible.
FREEDOM TO MOVE
Agents open full-page CRM records, KB articles or dashboards mid-call — the thing the old fixed layout made impossible.
INSIGHT C · CONTEXT ✓ SHIPPED

The Customer Context Panel

Identity, recent interactions, sentiment, and AI summaries in one view — the moment an interaction begins. The goal wasn't more data. It was the right context, at the right time.

Identity
Recent interactions
Sentiment
AI summaries
INSIGHT D · TAB SWITCHING ✓ SHIPPED

Four persistent panels, one view

Restructured the cost of tab switching into four panels that never disappear.

INTER-
ACTIONS
TRANS-
CRIPT
CON-
TEXT
3RD-
PARTY
INSIGHT E · MONITORING ✓ SHIPPED

Monitoring, out of the call

Performance monitoring competed with conversations. Moved it into a Home Dashboard — visible between interactions, never intrusive mid-call.

HOME · BETWEEN CALLS
( AI, LAYERED IN — NOT BOLTED ON )

Intelligence In the Flow

Instead of a separate AI feature, intelligence was embedded into the agent workflow itself.

ALL OF THESE SHIPPED
Sentiment signals
😠 frustrated 😐 neutral 😊 happy
Auto-disposition

Cuts manual tagging, improves reporting accuracy.

✦ Refund · Escalated auto
Context transfer

Intent and promised actions survive a handoff — no “start from scratch.”

A→B context intact
Critical-conversation alerts

Fire when urgency or SLA risk spikes.

⚠ SLA risk · 2:00 left
AI summaries

Across past and live conversations.

✦ AI SUMMARYRepeat contact re: delayed refund. Two prior emails unresolved.
( BEYOND THE CORE FLOW )

Production-Ready,
End to End

login · session timeout
Exotel agent sign-in with session-timeout dialog
Sign-in and the session-timeout state — a clear message instead of a silent logout.
reply composer
Email composer with recipients, rich-text toolbar, AI assist, attachments, draft and send
A rethought composer — recipients, rich-text formatting, AI assist, attachments, draft and send in one place.
recommended interactions
Interactions recommended list with sentiment tags and a resolved state
Sentiment tags, durations and a resolved state that fades out of the list on its own.
( ADOPTION )

Getting Agents to Actually Switch

Redesigning was half the work — the real question was whether agents would move. We leaned on behavioral nudges.

SOCIAL PROOF
“14 teams have already migrated.”
POSITIVE REINFORCEMENT
“You saved 1.5 hrs this week. 🎉”
SCARCITY FRAMING
What they'd miss by staying on the old tool.
FEEDBACK CAPTURE
Lightweight prompts for resistant users.
✕ AXED · ONE BOLD MIGRATION POPUP

One forceful migration popup got killed in review. We replaced it with a softer, phased rollout.

“Let's not traumatize our enterprise customers.”
— PM verdict
Your old workspace is gone.

Everything has moved. Learn the new system now or fall behind.

Force migrateLater
( HOW IT EVOLVED )

Five Passes, One Workspace

The workspace was never one big redesign. It grew in five deliberate passes: first the conversation, then email, then the full UAD and the docked toolbar, then a prototype developers could build against, and finally a second phase driven by how agents actually used it. Every screen below comes straight from the working Figma files.

BEFORE PASS 01 · CARD SORTING

Sort first, then draw

Floor visits gave me a long list of things an agent touches during a conversation. Before drawing a layout, I wrote each one on a card and sorted them by one question: when does the agent need this?

FigJam-style board: thirty-eight yellow sticky notes in a pile at the top, sorted into eight sections: Switch channel, Pick a conversation, Be in the conversation, Know the customer, Set up the shift, Wrap up the call, Dock in the CRM, and Dropped
Channel is a switch, not a property
Channels kept landing in their own group, apart from the conversations. So they moved to tabs on top, and each name in the list shows only its main channel.
The groups became the layout
Four of the eight groups became the zones of Pass 01: tabs on top, list on the left, the call in the centre, contact and CRM on the right. The other four shaped the toolbar header, the wrap-up step and the CRM dock in later passes. Two cards were dropped.
PASS 01 · VERSION ONE

Plan the conversation first

The first version started from a simple question: what does an agent need to see while a customer is talking to them? I mapped the call and chat layouts before touching any other feature.

  • Channels live on top as tabs (All, Video Call, Webchat, Email, WhatsApp), so an agent switches channel without leaving the screen.
  • The narrow left list is split into Active and Completed, with only the main channel shown under each name, so several conversations stay easy to scan. Other channels are a tab away.
  • Call controls and the video sit in the centre, so nobody tabs away mid-call.
  • A Contact and CRM panel on the right keeps channel details, open cases and knowledge-base answers beside the conversation.
FIGMA · ALL OLD FILES
one workspace · channel tabs, active and completed list, video call, contact and CRM panel
Version one of the workspace: channel tabs along the top, an active and completed interactions list on the left, a video call in the centre and a contact and CRM panel on the right
PASS 02 · EMAIL AS A CHANNEL

Email without breaking the flow

Email is slow, long and formal, which is the opposite of a live call. The goal was to add it as a first-class channel without turning the workspace into a mail client.

  • The subject line becomes the interaction title, and each email sits in the same interactions rail as calls and chats.
  • The reply box expands in place: To, Cc and Bcc chips, rich-text tools, attachments, AI assist and Save as Draft.
  • The customer panel stays visible beside the composer, with sentiment trend and a summary of the last five interactions.
  • I designed many states of the composer (plain reply, reply with Cc and Bcc, formatting, expanded, final state) so engineering never had to guess.
FIGMA · EMAIL
email reply · To / Cc / Bcc, formatting toolbar, drafts
Email reply composer with recipient chips, rich text toolbar and customer context panel
email reply · expanded to focus on writing
Email reply composer in its expanded state
PASS 03 · FINAL UAD + TOOLBAR

The workspace, and the toolbar

Many agents never leave their CRM, so the same product also had to work as a slim toolbar docked inside it. The final UAD defined both: the full workspace and the compact window.

  • A 350px toolbar keeps the customer, call timer, campaign, queue and call type in one compact header.
  • Call controls become a small grid of icon buttons, with end call set apart in red so it is never hit by accident.
  • WhatsApp works in the same window: the controls move up, and the conversation, search and reply box fill the rest.
  • It docks inside the customer’s CRM, here Salesforce, with a bottom bar for Home, Workbench, Callback, Apps and More.
  • Sign-in is the first screen: email or user ID with a password, or one click with Google or SAML. The left half previews a customer card (name, sentiment, reason for calling) under the line “Know what matters before the call begins”.
FIGMA · HARMONY AGENT UAD
sign-in · the first screen
Exotel sign-in screen: a welcome form with email or user ID, password, Login, Login with Google and Login with SAML, beside a customer card previewing who is calling and why
Sign-in. Password, Google or SAML on the right. On the left, a customer card shows what the call is about before it starts.
toolbar docked inside the CRM · Salesforce
The toolbar docked on the left of a Salesforce screen, showing agent status, a time analysis chart and a bottom navigation
Inside the customer’s CRM. The toolbar sits beside the record, so agents never leave the tool they already use.
toolbar · inbound call
The toolbar during an inbound call with caller name, number and a grid of call controls
Voice. Caller, timer and every control in one narrow column.
toolbar · WhatsApp chat
The toolbar during a WhatsApp chat with controls on top, a message thread and a reply box
WhatsApp. The same window turns into a chat, with search, replies and attachments.
PASS 04 · PROTOTYPE FOR DEVELOPERS

Design that builds itself

Static screens leave too much to interpretation. For handoff, I built a clickable prototype of the real flows (dialling, channel choice, past interactions) so developers could see behaviour, not just layout.

  • Starting an interaction is a short, guided path: pick a campaign, enter a number, or view the customer before dialling.
  • Channel rules are visible in the interface. If a WhatsApp customer is outside the 24-hour window, the agent is told why and offered a template to send.
  • Past interactions open in a right drawer with a case timeline across calls, email and WhatsApp.
  • Each state is named and ordered, so the prototype doubles as the build checklist.
FIGMA · PROTOTYPE FOR DEVELOPERS
prototype · initiate interaction, channel + 24-hour rulelooping
Animated prototype: the agent dials a number on the keypad and starts an interaction, then the Initiate Interaction dialog appears with WhatsApp Chat selected, explains the customer is outside the 24-hour window, and offers Choose Template
start a new interaction
Initiate new interaction with campaign selection and dial pad
past interactions drawer
Past interactions drawer with intents, case status and a cross channel timeline
PASS 04 · TESTED WITH CUSTOMERS

The prototype was tested with customers

I tested the clickable prototype with customers who run their own contact centers, so the flows met real operations and not only internal opinion.

redBusSliceRazorpayHSLBlue Dartand more
PASS 05 · PHASE 2

Smaller moments, fewer mistakes

Once agents were using it daily, the work moved to the small things that slow a person down: typing the same phrases, losing track of parallel chats, or ending a call by accident.

  • Acronym shortcuts. Type “/” in the chat box to open recent shortcuts like TTYL or TL, and the full phrase is dropped in. It works mid-sentence.
  • Persistent status bar. Every live interaction stays visible in the toolbar with its channel, timer and a “+5” overflow, so no conversation is forgotten.
  • Collapsible centre panel. Agents can shrink the conversation to an icon rail and give the customer record the full width.
  • End-call confirmation. A plain modal warns that unsaved notes will be lost, with “Stay on Call” as the safe choice.
FIGMA · HARMONY AGENT PART II
“/” opens recent acronym shortcuts
Chat composer with a slash command popup listing acronym shortcuts such as TTYL and TL
end-call confirmation
End interaction confirmation modal warning that unsaved notes will be lost
centre panel collapsed
Workspace with the centre conversation panel collapsed into an icon rail
persistent interaction status bar
Toolbar windows showing a persistent bar of live interactions with channel badges, a timer and an overflow count
( THE PRODUCT, SHIPPED )

Real Screens,
in Production

( OLD → NEW )

The same job, rebuilt

One connected call. On the left, the stack agents actually lived in. On the right, the workspace that replaced it — the call, the transcript and the CRM in a single, legible view.

BEFORE · LEGACY STACK de-identified
Before — legacy CRM with a dialer floating on top
A dialer floating over a dense CRM, twin scrollbars, truncated fields — dispositions typed twice.
AFTER · NEW WORKSPACE docked in the customer’s CRM
After — the Exotel softphone docked compactly inside the CRM, agent available
One compact widget that lives inside the CRM. Nothing floats, nothing hides the record.
( FEATURE BY FEATURE )

The details that do the work

TRANSCRIPT SEARCH
TRANSCRIPT SEARCH
Find any word across a live transcript — matches highlighted inline, filterable by speaker.
AI SUMMARY & SENTIMENT
AI SUMMARY & SENTIMENT
Last-5-interaction summary with a sentiment read and intent-tagged history, ready before you speak.
OMNI-CHANNEL COMPOSER
OMNI-CHANNEL COMPOSER
One reply box across email, chat and WhatsApp — recipients, subject, drafts and smart send.
CRISIS TAKEOVER
CRISIS TAKEOVER
Live conversations flagged Crisis surface for supervisor takeover the moment they turn.
INTERVENTION FUNNEL
INTERVENTION FUNNEL
Monitoring → proactive takeover, visualised so supervisors see their impact on the pool.
ROLES & PRIVILEGES
ROLES & PRIVILEGES
Enterprise RBAC — default and custom roles, per-row actions, org-wide access control.
AI SUGGESTIONS IN-THREAD
AI SUGGESTIONS IN-THREAD
AI drafts the next step inside the team thread — fraud alert SMS, repeat-case patterns — and humans confirm it.
TASKS FROM THE CONVERSATION
TASKS FROM THE CONVERSATION
A promise made on a call becomes a task — tagged, prioritised, assigned and dated without leaving the interaction.
ONE CUSTOMER, EVERY CHANNEL
ONE CUSTOMER, EVERY CHANNEL
One customer's call, email and WhatsApp thread stack under a single card — agents switch channels, not contexts.
agent workspace · live call + CRM lead
Live call with CRM lead details in the full agent workspace
supervisor home · performance overview
Supervisor home dashboard with KPIs and intervention funnel
↑ the full agent workspace with embedded CRM · the supervisor’s between-interactions home
( LOOKING BACK )

What I would do differently

The biggest lesson: agents do not need more features, they need fewer decisions in the middle of a call.

Push for the unified thread sooner
The customer-centric inbox lost because SLAs and reporting live at the interaction level. I shipped the channel-centric model with a UI built to evolve. The next step is to work with the backend on customer-level accountability, so the thread can finally be one.
Design the adoption path with the screens
The forceful migration popup died in review, and the phased rollout with behavioural nudges did the real work. I would plan that path from the first pass rather than after the screens were done.
Treat the prototype as the spec from the start
Static screens left room for interpretation. The Pass 04 prototype, with every state named and ordered, removed it. Next time I would build that clickable version at the first pass, not the fourth.
clarity
not capacity
( THE CLOSE )

Scaling Clarity,
Not Just Capacity

This wasn't about redesigning screens. It was about reducing friction in high-pressure conversations. By restructuring context, embedding intelligence, and respecting how agents actually work, the system scales clarity — not just throughput.

Want the deeper walkthrough? Let's talk → ← back to the studio
CONTACT CENTER WORKSPACE · EXOTEL ECC ANJALI SRIVASTAVA · 2026