Contact Center & UCaaS Integration

Contact Center & UCaaS Integration

Contact Center & UCaaS Integration

Merging a legacy Contact Center app into Intermedia Unite — one unified desktop experience for agents handling both business and customer service calls.

A desktop application used by Contact Center Agents

Industry

Unified Cloud Communications

My Role

Product designer

Stack

Sketch, Figma, Zeplin, Miro

Problem & Solution

Problem & Solution

Unite was a modern, well-designed desktop app. The newly acquired Contact Center app (CCA) was a legacy product — outdated UI, different workflows, different mental model. The challenge was integrating both without breaking either.

I designed a unified experience where agents could handle regular business calls and contact center interactions from a single app — with clear visual distinctions so they always knew which type of call they were on.

200

Number of Customers

Number of Customers

45,000

Number of Users

Number of Users

The big problem

The big problem

Unite and CCA were built independently, looked nothing alike, and served different user needs. Merging them meant reconciling two completely different interaction models — without confusing users who only needed one of them.

Unite was the existing app. CCA was the newly acquired app that had to fit in the Unite ecosystem of services. They were miles apart from one another!

Approach

Approach

How I split my time — heavily weighted toward research because the integration complexity had to be understood before anything could be designed.

Initial Exploration

Initial Exploration

Before designing anything, I mapped everything the CCA did — queue status, inbound calls, outbound calls, transfers, chats, and email — to understand what had to be integrated and what could be deferred.

  • It allows the agent to have an overview of the queue status

  • It allows agents to receive calls to the Contact Center

  • It allows agents to place calls to various destinations

  • Agents can transfer calls within the organization

  • It handles chats and email (Not MVP)

  • It allows the agent to have an overview of the queue status

  • It allows agents to receive calls to the Contact Center

  • It allows agents to place calls to various destinations

  • Agents can transfer calls within the organization

  • It handles chats and email (Not MVP)

  • It allows the agent to have an overview of the queue status

  • It allows agents to receive calls to the Contact Center

  • It allows agents to place calls to various destinations

  • Agents can transfer calls within the organization

  • It handles chats and email (Not MVP)

Competitor research

Competitor research

I researched how Five9, 8x8, RingCentral, and Vonage handled the same integration challenge — looking specifically at how they distinguished contact center calls from regular calls, and how they handled the agent login flow.

Competitors

Competitors

Driving conversations

Driving conversations

  • I mapped two options: merge CCA into Unite, or redesign it as a standalone app. I presented the tradeoffs to stakeholders with pros and cons for each.

  • The decision: merge. One app, one experience, no context switching for agents.

Finding the right place for the new app

Finding the right place for the new app

The core challenge was positioning Contact Center functionality within an interface agents already knew. I introduced a new tab for accounts with CCA access — keeping the familiar Unite structure intact while making the new functionality immediately findable.

Designing the Contact Center Call Bar

Designing the Contact Center Call Bar

The Call bar

The Call bar

I audited every control in the existing Unite call bar and mapped each one against Contact Center needs — keeping what applied, removing what didn't, and adding what was missing. The result was a leaner, purpose-built call bar for CCA interactions.

Creating a new Call bar

Creating a new Call bar

To help agents instantly distinguish a Contact Center call from a regular one, I changed the call bar colour to amber — familiar enough to feel native, distinct enough to be unmistakable.

Call bar instances

Call bar instances

The call bar had to reflect every state an agent might encounter — incoming, active, on hold, transferring, ending. I designed distinct colour and control states for each, so agents could read the situation at a glance without having to think.

Testing user flows

Testing user flows

The transfer flow was the most complex interaction in the product — six distinct states from incoming call to completed transfer. I tested this first as it set the interaction pattern for everything that followed.

Iteration

Iteration

Most of the work happened between the wireframes and the final UI — aligning interaction behaviour with existing Unite patterns, building consistency into edge cases, and stress-testing every call scenario with the product team before the design system work began.

Lessons Learnt

Lessons Learnt

I was brought in to establish the foundation — the interaction model, visual language, and core flows. Once the groundwork was done, the project moved to a dedicated team.

Integration projects are behaviour problems before they're design problems. The hardest work was alignment, not aesthetics.

© Dimitra 2026

© Dimitra 2026

© Dimitra 2026

Create a free website with Framer, the website builder loved by startups, designers and agencies.