Evermos

Evermos

April 2024 - July 2024

April 2024 - July 2024

April 2024 - July 2024

CS Funneling - Evermos Mobile App

CS Funneling - Evermos Mobile App

Overview

Overview

About the Project

About the Project

CS Funneling was the main project I undertook during my internship as a UX Designer at Evermos. The project aimed to guide users toward creating complaint tickets instead of directly contacting customer service via WhatsApp. The primary objectives of CS Funneling were to simplify the complaint process for users and reduce the operational cost ratio of customer service per transaction.

CS Funneling was the main project I undertook during my internship as a UX Designer at Evermos. The project aimed to guide users toward creating complaint tickets instead of directly contacting customer service via WhatsApp. The primary objectives of CS Funneling were to simplify the complaint process for users and reduce the operational cost ratio of customer service per transaction.

Role & Responsibility

Role & Responsibility

UX Designer

UX Designer

As a UX Designer, I was responsible for understanding user pain points in submitting complaints to Evermos customer service. I collaborated directly with stakeholders, including the CS team, to analyze data and identify the right business solutions, as direct WhatsApp complaints led to increased operational costs. I then worked with the project manager to find the best solution for both user and business needs, which I translated into a user interface design to be developed by the engineering team.

As a UX Designer, I was responsible for understanding user pain points in submitting complaints to Evermos customer service. I collaborated directly with stakeholders, including the CS team, to analyze data and identify the right business solutions, as direct WhatsApp complaints led to increased operational costs. I then worked with the project manager to find the best solution for both user and business needs, which I translated into a user interface design to be developed by the engineering team.

Pain Points

Pain Points

Based on research and data gathered by stakeholders, including the Project Manager and CS Team, several pain points were identified from both the user and business perspectives.

Based on research and data gathered by stakeholders, including the Project Manager and CS Team, several pain points were identified from both the user and business perspectives.

User Side

User Side

Users were frustrated with the long resolution time for their complaints handled by the CS team

Users were confused about the progress of their complaints submitted via WhatsApp, leading them to spam the chat

Users felt frustrated having to switch between the app and WhatsApp repeatedly to ensure their submitted data was correct

Business Side

Business Side

Operational costs increased due to the use of third-party services for each user complaint handled by the CS team

Complaint resolution took longer as the team had to manually sort through each case from the third-party system

The CS team was overwhelmed with managing data, which had to be continuously monitored and manually entered one by one

Ideate the Solution

Ideate the Solution

Next, the Project Manager and I formulated two How Might We questions, which served as a reference for developing solutions to address the identified pain points.

Next, the Project Manager and I formulated two How Might We questions, which served as a reference for developing solutions to address the identified pain points.

How Might We...

...streamline the process for users to create and submit complaint, reducing the need for direct customer service interaction?

Solution

One solution to this issue is to implement CS Funneling, guiding users to create complaint tickets within the Evermos application.

How Might We...

...help users easily check the progress of their complaint?

Solution

The proposed solution is to create a new page within the Evermos application that lists complaint tickets submitted by users. These complaint tickets contain information including their status. When a ticket is clicked, it will direct the user to a detailed complaint page where they can view the complaint details along with its progress status.

Design Exploration

Design Exploration

Order Complaint Flow

Order Complaint Flow

There are two entry points for submitting order complaints: the help center and the order details page. The flow shown here uses the help center as the entry point.

First, user can tap the "Pusat bantuan" button → "Bantuan kendala" → "Terkait pesanan", then select the order they want to file a complaint about.

After selecting the affected order, the user can choose the specific product with an issue and select the appropriate complaint category.

Next, the user must complete the required information to proceed with the complaint submission. When the user clicks the "Ajukan keluhan" button, a popup will appear to confirm that the entered data is correct.

After submitting a complaint, user will be redirected to the "Keluhan saya" page, where a confirmation message will appear indicating that the complaint has been successfully submitted. On this page, users can track the progress of their complaint resolution through the complaint status updated by the CS Team.

Other Complaint Flow

Other Complaint Flow

The entry point for app-related issues is the help center. To submit a complaint, the user can tap "Pusat bantuan" → "Tidak terkait pesanan" → then select the complaint category.

Next, user is required to complete the complaint submission form and can only submit the complaint after confirming that the entered data is correct.

After submitting a complaint, user will be redirected to the "Keluhan saya" page, where a confirmation message will appear indicating that the complaint has been successfully submitted. On this page, users can track the progress of their complaint resolution through the complaint status updated by the CS Team.

Design Critics

Design Critics

The design critique session was attended by several individuals, including stakeholders, the PM, the Design Manager, the UX Designer, and the Engineering Manager. During this session, I presented the results of my design exploration. I received several pieces of feedback, which I will present as follows.

The design critique session was attended by several individuals, including stakeholders, the PM, the Design Manager, the UX Designer, and the Engineering Manager. During this session, I presented the results of my design exploration. I received several pieces of feedback, which I will present as follows.

Design Finalization

Design Finalization

Next, I improved the design based on the feedback from the previous design critique session.

Next, I improved the design based on the feedback from the previous design critique session.

Results

Results

Here are some results from implementing CS Funneling in the Evermos mobile application:

Here are some results from implementing CS Funneling in the Evermos mobile application:

Operational costs per transaction decreased by 50%, from IDR 16,000 to IDR 8,000

Contact ratio to CS decreased by 70%

Success in creating complaint tickets is at 94%

Key Takeaways

Key Takeaways

What did I learn?

What did I learn?

Designing CS Funneling for a commerce application was challenging and provided a new experience for me in terms of design exploration

Communication is crucial when working in a team; therefore, I must always communicate with the team to avoid misunderstandings

Look for design references in various applications. This should be done to understand patterns that are familiar to users