Webinar recording

Service design for contact centers: building service around the customer

Oleh Koss explains what service design is and uses cases from a railway, apartment sales and a bank to show how a contact center becomes part of a service model rather than a place to collect complaints. The recording is useful for heads of contact centers, support teams and sales departments who want to understand what customers actually want.

January 30, 2026
Service design
Length1 h 25 min
Recording language
UAUkrainian
Watch the recording
Speakers: Oleh Koss, Yuliia Demchyk
The recording opens after a short quiz, about 40 seconds

What you will learn

  • Service design means designing a service: you look at the task through the customer's eyes and account for the steps before and after contact with your company, including those outside your control.
  • Every touchpoint, the contact center included, works by changing customer behavior; for a support team the desired change is that the customer stays with the company longer.
  • Customers are not like us and rarely articulate their motives, so without interviews you design blindly: 5 to 8 conversations reveal typical problems, 15 to 20 give you segments.
  • Categorize requests the way the customer sees the problem, not by responsible department; then even in a bank about 10 topics cover more than half of all requests.
  • Most support requests are bad for both the customer and the business, so the best fix is changing the product, while answers to the rest should match the customer's level of knowledge.

What is inside

  1. What service design is and why it means engineering, not looks
  2. The US railway case: the first-class passenger journey
  3. The contact center as a tool for changing customer behavior
  4. Selling apartments: three buyer segments and questions to identify them
  5. Customer support: each typical request needs its own design
  6. Three ways to categorize requests and a bank example
  7. One request, three customer types: how to talk to each
  8. Audience questions: who becomes the service designer, how many interviews, the role of AI

About this webinar

Oleh Koss starts with a definition: service design is designing a service so that it meets customer needs and business constraints at the same time, making it pleasant, reliable and profitable. Here "design" means engineering, not aesthetics. Every service was designed by someone, just not always deliberately. The key point for a contact center: the customer lives their life outside your phone line, something happened before the call, and their task continues after it. So a contact center can be part of service design, but never its only object.

The case of the US railway Amtrak illustrates this. The company wanted to fill its first-class cars. The agency first asked where people travel first class and found it was mostly business trips. In the ten-step journey of a business traveler, the train car turned out to be only step eight: before it, an assistant has to learn the train is an option, the schedule has to fit the meeting, the traveler has to get to the station, park and pass a security check, and after arrival still reach the meeting. The railway changed its schedule and arranged parking, lounges, car rental and a separate security checkpoint for first-class passengers.

Next, the speaker suggests seeing the contact center as a tool for changing customer behavior. Recalling his time at Kyivstar, he says the key support KPI became growth in the lifetime value of a customer who got through. To change, a person needs to see a problem and a benefit, but the comfort of the status quo and doubts about the new hold them back. One example: clothing buyers did not return items because they assumed it was complicated, although the process was trivial: bring the item, give a phone number and get the money back. The speaker sees the difference between influence and manipulation only in intent: a contact center should change behavior so that people end up better off.

In an apartment sales project the team ran about two dozen in-depth interviews and found three segments: young people buying their first home, families with children, and well-off people near retirement buying as an investment. Their motives differ: confidence in the right choice, keeping the familiar neighborhood and school, fear of losing savings. Two or three natural questions early in the call, such as who will live in the apartment and whether it is a first purchase, help identify the customer. According to the speaker, communication tailored to these needs doubled conversion.

Customer support gets the most attention. Each typical request topic needs its own design, and that is realistic if requests are categorized from the customer's point of view rather than by department or root cause. The wording "I can't add my card to my wallet" describes the problem better than a technical diagnosis and builds empathy across the organization. In a bank project about 10 topics covered more than half of all requests: blocking a card 6%, a card payment not completing 7%, failed online payments every tenth request. Some calls are welcome, such as a lost card or a loan, but most should be removed by changing the product. The answer to the same question differs for experienced, busy and novice customers.

In the Q&A Oleh advises that anyone who cares can take on the service designer role, and that for research you should pick operators with the longest average call time, because they listen better. AI still takes answers literally, so it is an assistant in analysis, while people should define the segments first.

Who it is for

  • Heads of contact centers and customer support teams
  • Service designers, CX managers and product teams
  • Sales managers working with inbound and cold calls

Speakers

  • Oleh Kossservice design and service model transformation practitioner
  • Yuliia Demchykwebinar host, CX Horizon

Watch the full recording for free

Answer six quick questions and the recording opens right away. We will also email you the link.