The main users of the after-sales service system involve members of several departments in commerce and after-sales, so it is important to understand their daily workflow. Before the project started, we interviewed the actual users of the product (after-sales, commercial department members, after-sales person in charge) to understand these issues.

• The current division of responsibilities and workflow of each department.
• How the departments communicate and collaborate with each other.
• The common types of contracts signed with customers.
• What common problems customers encounter.
• The process of handling problems in the after-sales department.

After 3~4 rounds of in-person communication, we have an overall understanding of the obstacles that the after-sales department will encounter in practice, and the main problems that exist are.

After the requirements and product flow were determined, the design exploration began.

The design exploration mainly revolved around the following aspects.

• Overall style: including visual style, interactive forms, how to maintain a consistent image with the client's brand.
• Information architecture: including overall navigation, page layout, first and second page jumping relationship, etc.
• Lists: lists are the main form of displaying data in the system, so the search, filtering, adding operations and page-turning controls about lists also need to find the right form.

After communicating with the client, the after-sales service system, as an internal corporate tool, wanted the overall style to be consistent with the brand image, while the visuals and interactions could be kept simple and clear, and could help the after-sales staff to complete their tasks better and more efficiently.

We extracted design elements from the client's website and products, such as the stylized background image of the client's website and the color palette of the client's products, and applied them to the overall visual design.

The main considerations at the information architecture level were the overall navigation, page layout and the handling of logical relationships between pages at different levels. For this purpose we experimented with various layouts and discussed the future planning of the system with the client, and finally settled on a final version based on the following factors.

• Simplicity of hierarchy and ease of interaction.
• providing a consistent operating experience for users with different permissions (the amount of content they see may vary).
• meeting the client's future functional expansion needs.

Lists are essential components for any product with large amounts of data. Although they seem simple, they actually contain a variety of components and complex interactions, such as search, filter, sort, manipulate, and page flip controls, so the components have to be customized according to actual needs.

After communicating with the client to understand the requirements for handling list data, we iterated through the final design.

Since after-sales service relies heavily on mastering customer data and cluster data, data entry is an essential part of the system. But at the same time, the large amount of data entry operation may cause difficulties to the actual users.

For example, when entering a contract, the following information needs to be entered.

• Customer information
• Project information
• Hardware information
• Salesperson information
• Financial information
• Offering Information
• All-in-One Configuration
• ......

With this design, team members can clearly know how to fill in each field and what to pay attention to when using the form, so even new members can quickly get started and avoid the possibility of making mistakes.

In addition, we also carefully considered the appropriate default fill fields for each input box in the form to guide users to fill them according to the rules. We have added the function of collapse/expand area in the long form page with separate areas, so that you can focus on filling in a single part when modifying.

Providing quality after-sales service to customers depends on the mastery of customer information, and in the early stage it depends on the accurate entry of various data by members. In the post-sales stage, it depends on the efficiency of data processing.

Usually when a customer encounters a problem and contacts after-sales service, the after-sales service needs to understand the customer information and hardware environment information at the first time in order to provide a targeted solution for the customer. To get complete information is based on the fragmented information provided by the customer, and the fragmented information does not necessarily have a fixed type, so a powerful global search can greatly enhance the efficiency of after-sales processing.

The system data contains many confidential data, which are very important to the company and customers, such as customer information, contract information and cluster information. These data are managed under different departments, for example, the commercial department is responsible for entering contract data, and the after-sales engineers are responsible for entering customer cluster information ...... Different data need to strictly control the people who can access them to prevent important data from being misused or modified.

This also requires careful differentiation of permissions, so we break up the original role permissions (department member permissions) into the smallest granular operations: access permissions, add content permissions, modify content permissions, and a single department member permission is a combination of a series of operations. Permissions are no longer strictly divided according to departments. When administrators add members to select departments, permissions are selected according to the default permissions preset by the department, and flexible adjustment is also supported, so that different permissions can be assigned to members with different divisions of work within the team.

Together with the login permissions of the system itself, it constitutes the complete permission design of the system. When an employee leaves the company, the login permission can be closed.

The process of entering contract and cluster information requires the participation of several members, and even requires cross-departmental collaboration. In order to ensure the accuracy of the data, we need to record during the collaboration process and track the process of data changes; on the other hand, customer information and cluster information will keep changing over time, and also need to be updated by team members in a timely manner, we also need to record the changes of different versions.

For this reason, we added version information to the details page of contracts and clusters. Each update by the user will save a version and record the person, time and content of the modification, and the content modified in that version will be highlighted when the corresponding version name is clicked.

The main users of the after-sales service system involve members of several departments in commerce and after-sales, so it is important to understand their daily workflow. Before the project started, we interviewed the actual users of the product (after-sales, commercial department members, after-sales person in charge) to understand these issues.

• The current division of responsibilities and workflow of each department.
• How the departments communicate and collaborate with each other.
• The common types of contracts signed with customers.
• What common problems customers encounter.
• The process of handling problems in the after-sales department.

After 3~4 rounds of in-person communication, we have an overall understanding of the obstacles that the after-sales department will encounter in practice, and the main problems that exist are.

After the requirements and product flow were determined, the design exploration began.

The design exploration mainly revolved around the following aspects.

• Overall style: including visual style, interactive forms, how to maintain a consistent image with the client's brand.
• Information architecture: including overall navigation, page layout, first and second page jumping relationship, etc.
• Lists: lists are the main form of displaying data in the system, so the search, filtering, adding operations and page-turning controls about lists also need to find the right form.

After communicating with the client, the after-sales service system, as an internal corporate tool, wanted the overall style to be consistent with the brand image, while the visuals and interactions could be kept simple and clear, and could help the after-sales staff to complete their tasks better and more efficiently.

We extracted design elements from the client's website and products, such as the stylized background image of the client's website and the color palette of the client's products, and applied them to the overall visual design.

The main considerations at the information architecture level were the overall navigation, page layout and the handling of logical relationships between pages at different levels. For this purpose we experimented with various layouts and discussed the future planning of the system with the client, and finally settled on a final version based on the following factors.

• Simplicity of hierarchy and ease of interaction.
• providing a consistent operating experience for users with different permissions (the amount of content they see may vary).
• meeting the client's future functional expansion needs.

Lists are essential components for any product with large amounts of data. Although they seem simple, they actually contain a variety of components and complex interactions, such as search, filter, sort, manipulate, and page flip controls, so the components have to be customized according to actual needs.

After communicating with the client to understand the requirements for handling list data, we iterated through the final design.

Since after-sales service relies heavily on mastering customer data and cluster data, data entry is an essential part of the system. But at the same time, the large amount of data entry operation may cause difficulties to the actual users.

For example, when entering a contract, the following information needs to be entered.

• Customer information
• Project information
• Hardware information
• Salesperson information
• Financial information
• Offering Information
• All-in-One Configuration
• ......

With this design, team members can clearly know how to fill in each field and what to pay attention to when using the form, so even new members can quickly get started and avoid the possibility of making mistakes.

In addition, we also carefully considered the appropriate default fill fields for each input box in the form to guide users to fill them according to the rules. We have added the function of collapse/expand area in the long form page with separate areas, so that you can focus on filling in a single part when modifying.

Providing quality after-sales service to customers depends on the mastery of customer information, and in the early stage it depends on the accurate entry of various data by members. In the post-sales stage, it depends on the efficiency of data processing.

Usually when a customer encounters a problem and contacts after-sales service, the after-sales service needs to understand the customer information and hardware environment information at the first time in order to provide a targeted solution for the customer. To get complete information is based on the fragmented information provided by the customer, and the fragmented information does not necessarily have a fixed type, so a powerful global search can greatly enhance the efficiency of after-sales processing.

The system data contains many confidential data, which are very important to the company and customers, such as customer information, contract information and cluster information. These data are managed under different departments, for example, the commercial department is responsible for entering contract data, and the after-sales engineers are responsible for entering customer cluster information ...... Different data need to strictly control the people who can access them to prevent important data from being misused or modified.

This also requires careful differentiation of permissions, so we break up the original role permissions (department member permissions) into the smallest granular operations: access permissions, add content permissions, modify content permissions, and a single department member permission is a combination of a series of operations. Permissions are no longer strictly divided according to departments. When administrators add members to select departments, permissions are selected according to the default permissions preset by the department, and flexible adjustment is also supported, so that different permissions can be assigned to members with different divisions of work within the team.

Together with the login permissions of the system itself, it constitutes the complete permission design of the system. When an employee leaves the company, the login permission can be closed.

The process of entering contract and cluster information requires the participation of several members, and even requires cross-departmental collaboration. In order to ensure the accuracy of the data, we need to record during the collaboration process and track the process of data changes; on the other hand, customer information and cluster information will keep changing over time, and also need to be updated by team members in a timely manner, we also need to record the changes of different versions.

For this reason, we added version information to the details page of contracts and clusters. Each update by the user will save a version and record the person, time and content of the modification, and the content modified in that version will be highlighted when the corresponding version name is clicked.