Contact Center Team (Dialpad)
As the product designer, I worked closely with a lead designer in creating a qa scorecard on the Dialpad web app.
Product design, IXD, user research, product strategy, and overseeing development
Aug 2020 - Nov 2020 | Released '21
Currently our customers with do this informally or outsource it to another (paid) product. Even managers at Dialpad use another 3rd-party tool to perform call quality control.
As turnover rate for agents is high, companies may not be able train or prepare the employees fully. Managers often would want to provide coaching to those agents who are new or struggling.
Managers can create new scorecards with prebuilt templated questions, or create new templates to build new evaluation criteria that cater to the managers' needs.
Customize question with different types and rate how important a question is.
At a glance, view graded calls or find calls to grade.
Additionally, share calls to invite others to grade.
Use existing voice intelligence to conduct semantic analysis and provide suggestions to a question in the scorecard.
View agent performance at a glance or drill down individually to view their performance in detail.
(Not my design, but adding to complete the whole project)
Unfortunately the a new PM joined the project when it was closed to project launch, so desired metrics were not collected properly. However, through chatting with internal sales and CSAT, Ai Scorecard is one of the most sought after feature in the Contact Center product.
The project was first released in 2021. The company has been through a rebrand since then with an emphasis on labelling Ai. The visual may look different however the general design has stayed the same.
We conducted 2 sessions with 15 internal stakeholders, ranging from C-suites, engineers and support agents. We asked them to brainstorm and come up with sketches that would helpful for the users.
We synthesized the findings from the workshops, user interviews and competitor analysis. We presented the general user flow and came up with fundamental design feature requirements. This process allow PM and engineering lead to understand the project overview to prepare scoping and resources.
The scale of the project was much bigger than what the team has anticipated, so we decided to split up the flows to work in parallel to meet the desired deadline.
I was tasked to come up with the solutions for
1.) Creating a rubric,
2) Find and assign calls and
3) Score calls.
The rest of the flows were designed by the lead designer.
As Dialpad is a SaaS company, different subscription and licenses are offered. Employees same roles within the company might have different feature access based on the license they are on. We came up with charts to further differentiate the type of access and permission they have on individual page.
White space with limited information was purposely intended, as I want the manager to solely focus on creating questions one at a time.
We discovered that managers are so used to seeing many graphs and details in one page, so opted for a more compact view when creating a score card.
Many options were explored on how we can create the best grading experience for the managers. I originally went with the existing call summary pattern to figure out how can grading be incorporated into the page.
Hoping to create a more modern and refreshed look with bigger real estate to grade call, I deviated from existing pattern and explored two column layout. It was well received from the stakeholders.
However despite the well-received exploration from internal stakeholders, the desire of revamping the transcript/ call summary page received a strong pushback from the engineering team. By doing so, the project will be in risk of not being able to meet the deadline.
Additionally some users are already used to the three-column layout, and changing to a two column layout may interrupt user's mental load and experience with Dialpad.
Edited on Jan 2024
The two exploratory north star feature has been rolled out. Even though I am no longer to over see the project but I am happy to know that my exploratory design was still used and implemented.
This was one of the most anticipated features, however due to time constrained it was not included in the engineering sprint. However I still came up with exploratory design to present to the the stakeholders to get buy-ins.
Use sentimental analysis (Vi) to help answer the questions: allow admins to come back to finish the work as the process may be tedious.
Connect call summary to custom moments: allow admins to double check on their work before creating class creation, plan eligibility mapping that might impact the entire benefits package
Use familiar interaction patterns that matches users’ mental models