How a Smart Workbench Can Boost B2B Customer Service Efficiency

Introduction

In B‑to‑B product design, a well‑designed workbench can greatly improve user efficiency and experience. The Customer Service System (CSC) reconstruction aims to connect business processes, enhance service quality and response speed, using the CSC project as an example.

Background and Pain Points

The CSC is a comprehensive service platform whose core value lies in boosting enterprise competitiveness and brand image through after‑sales service, consumption promotion, and membership renewal. Current pain points include a chaotic, unstandardised workflow, low task‑completion rates, limited integration with business lines, and insufficient support, all of which hurt efficiency and quality.

Workbench Overview

The workbench is the digital module that supports users in completing role‑based tasks. In the CSC there are two main roles:

Executor (Customer Service Representative) : needs to complete tasks efficiently.

Manager (Customer Service Supervisor) : needs to monitor business status.

For executors, a typical day involves checking assigned tasks, planning work, and reviewing completion before leaving. Without a workbench, tasks are scattered across multiple screens, wasting time and causing omissions. For managers, a unified dashboard is required to view overall performance and individual task status; otherwise they must manually gather data, which is slow and outdated.

Design Process

The first step is to understand what users care about most. By consolidating workflow information for the two key roles, the workbench presents role‑specific task data.

Content acquisition methods include user interviews, surveys, feedback, competitor analysis, and brainstorming. Qualitative research is emphasised because a small sample can represent the majority of users in each role.

Reconstruction goals are to standardise the workflow, translate management policies into concrete tasks, and raise the target‑completion rate. Key performance indicators displayed on the workbench include monthly cash consumption, consumption completion rate, customer count, coverage, and overall KPI completion.

Core workbench content (derived from a frontline representative example) consists of performance display, schedule management, reminders, daily to‑do list, and common tools.

Framework Structure

Navigation design adopts multi‑page opening within the system to reduce page jumps and improve task efficiency.

Page layout design follows data‑driven and task‑flow‑driven principles, organising modules by importance to enhance browsing and operation efficiency.

System Extension

To serve multiple business lines and scenarios, the system is built with high flexibility, allowing role‑ and scenario‑based composition while reducing product changes and development cost.

At the UI layer, content structures are decoupled to lower module coupling. At the code layer, modular units are aggregated in an orderly manner to meet multi‑role, multi‑scenario needs.

Visual Communication

Two factors shape visual design:

Machine factor : Most agents use 1366×768 or 1600×900 screens. Smaller component sizes and a 12‑pt base font were chosen to fit more information on a single screen.

Human factor : Emotional design is introduced through illustrations, skin‑changing, and “soul‑soup” motivational messages, creating a sense of connection and reducing the monotony of repetitive tasks.

Illustrations are added to the main workbench and login pages; a skin‑switching feature lets users personalise the interface.

Conclusion

The workbench design revolves around tasks, people, and scenarios. Although the concept appears simple, its value varies with the underlying business. Only by deeply understanding business needs and real user requirements can the workbench unleash its full potential.