📥Help Desk: Resolve and Record Customer Issues

The Help Desk is the main workspace where agents handle customer interactions. This article explains the complete process of a service in FIRST LINE, from the customer reaching out, identity verification, issue handling, and recording service information, to completing the service or creating a ticket for ongoing follow-up.

FIRST LINE Service Desk centralizes customer interactions from different channels into a single workspace. Whether a customer contacts you via LINE, Facebook Messenger, live chat, email, or phone, agents can view the current case in the Service Desk, respond to customers, look up customer information, record service details, and create a ticket for ongoing follow-up when needed.

Rather than thinking of the Service Desk as "many features on one page," it is better to view it as a workflow from the start to the end of a service case:

Customer contacts in → Agent responds → Verify customer → Understand the issue → Reply and handle the case → Record service information → Create a ticket / reassign if needed → Complete the service → Leave a service record

The end of a conversation does not necessarily mean the service is complete.

If the customer has not sent another message for the moment, the call has ended, or the email has been replied to, it only means that this conversation has temporarily come to a close. If you still need to wait for another department, logistics, billing, or a follow-up confirmation, you can first keep the service open or create a ticket to track it, and then close the service after the actual handling is finished.

Understanding the three main areas of the Service Desk

The Service Desk can be roughly divided into three areas:

Area	Main purpose
Service list	View the services currently being handled and those waiting to be picked up, and switch between different services.
Workspace	View customer data, service information, tickets, knowledge, and historical service records to help agents make decisions and keep records.
Conversation area	The area for actual interaction with customers, with an interface suited to channels such as messages, phone, and email.

The Service Desk brings the service list, workspace, and conversation area together on the same screen.

1. Use the service list to keep track of the customers you need to handle

The service list shows the service status currently related to you. It is commonly divided into "In service" and "Waiting":

Status	Description
In service	Services that have been picked up by you and are still your responsibility. You can switch between multiple services and continue handling different customers.
Waiting	Items that have entered the service process and are waiting to be picked up or handled by you. The actual assignment and waiting behavior may vary depending on the company's conversation assignment settings.

How waiting services are assigned, whether they can be reassigned, and how many services an agent can handle at once may all be affected by the company's conversation assignment and service settings. Therefore, it is not recommended to understand every company's service process using only one fixed rule.

2. First confirm "who you are serving right now"

When a customer contacts you via LINE, Facebook, phone, or another channel, the system first knows only the "contact on that channel." If the company already has matching customer data, it is recommended to associate the current service with the correct customer.

The value of doing this is not just displaying a name, but placing the interaction back into the full customer context. After linking, the agent can more easily view:

• Basic customer information and company-customized fields.

• Past service records.

• Tickets and follow-up items related to the customer.

• Other historical information that can help judge the current service.

Common situations include:

• Customer data already exists: Search for and select the correct existing customer.

• Customer not yet created: Create a new customer record directly and link it to this service.

• Incorrect association: Remove the current association and select the correct customer.

• Duplicate customer records: After confirming the data, use customer merge or other management functions to organize them.

Before merging customers or relinking existing data, it is recommended to confirm the customer's identity and history to avoid merging service data from different individuals.

3. Understand the issue and find the information you need in the workspace

The workspace centrally displays the customer and business information related to the current service, so agents do not need to leave the Service Desk frequently to look up data.

Common tabs and their uses are as follows:

Item	Purpose
Customer	View or edit the currently linked customer data, and handle customer association.
Service details	Record notes, custom fields, service tags, and other information for the current service.
Ticket	View existing customer tickets, or create a new ticket for matters that require cross-time, cross-person, or cross-department handling.
Knowledge base	Look up products, policies, processes, or FAQ content organized by the company as a reference when replying to customers.
Service records	View past service history to understand why the customer contacted you, how it was handled, and the outcome.

If the company has enabled AI-related features, AI can also be used to assist in finding, organizing, or generating reply content; however, before replying, the agent should still confirm whether the answer is appropriate for the customer's current situation.

4. Respond to the customer in the conversation area

The conversation area provides interaction methods based on the service channel, while the overall service workflow remains consistent.

Channel type	Common operations
Messages	LINE, Facebook Messenger, live chat, and other channels are presented as a conversation timeline, and can be replied to with message templates, attachments, and other messaging tools.
Phone	Displays call-related operations, and depending on the company's plan and phone settings, features such as transfer and three-way calling may be available.
Email	View and reply to customer emails in an email conversation format, with support for email templates and attachments.

Although reply methods differ by channel, the agent can maintain the same approach when handling the issue:

1. Confirm the customer's identity and current needs.

2. Review past services and related tickets to avoid asking the customer to repeat information they have already provided.

3. Look up knowledge, internal materials, or other supporting references.

4. Reply to the customer and record the important information from this service.

5. Determine whether the issue has been resolved or still needs follow-up.

5. Record why the customer came and how it was ultimately handled

The Service Desk is responsible not only for replying to customers, but also for organizing each service case into a service record that can be queried and analyzed later.

Common record contents include:

Data	Purpose
Notes	Add important background, handling process, or follow-up notes for this service.
Service tag	Describe why the customer contacted you this time, such as returns/exchanges, billing issues, or product inquiries.
Service result	Describe the final handling outcome when the service is completed, such as completed, ongoing follow-up, or transferred to another department.
Custom fields	Record other structured information according to the company process.

Service tags and service results have different purposes.

Service tags focus on "why the customer came"; service results focus on "how it was finally handled." For example, if a customer contacts support for a "return/exchange," the service tag can be recorded as "Return/Exchange"; if the issue is later resolved, the service result can be set to "Completed."

These data become part of the service record and can later be used to search historical services, as well as combined with reports and AI analysis to understand common issues, service outcomes, and handling trends.

6. If the issue is not finished yet, create a ticket to continue tracking it

Not every customer issue can be resolved in a single conversation.

The following situations are usually suitable for creating a ticket:

• Need confirmation or handling from another department.

• Need to wait for logistics, billing, engineering, or other external results.

• Need ongoing follow-up across multiple days.

• There is a clear owner, deadline, or progress that needs to be managed.

• The customer may contact you again later, and the team needs to quickly understand the current handling status.

You can simply think of them as:

A service record records "what happened in this service"; a ticket tracks "what still needs to be done next."

Therefore, even if the conversation has come to a close, as long as follow-up items are not truly complete, you can leave responsibility and progress in a ticket rather than relying only on the agent's memory or a personal to-do list.

7. Reassign the case when another agent needs to take over

When the current service is better handled by another agent or team, you can use the reassign function to let someone else continue the service.

After reassignment, this service will be taken over by the new owner. Which personnel it can be assigned to and how the handoff is selected will vary depending on the company's permissions and service settings.

8. When should the service be completed?

"Complete service" means the case no longer needs to remain in the current agent's service workflow, and the system will save the handling details as a service record.

Before completing, it is recommended to confirm:

• Whether the customer's current issue has reached a stage where this service can be closed.

• Whether the correct customer data has been linked.

• Whether important handling information has been recorded in notes, custom fields, or other service information.

• Whether the appropriate service tag has been selected.

• If the company requires a service result, whether the correct result has been selected.

• Whether any unfinished follow-up items already have a ticket or another clear tracking method.

A good service process is not about "the faster you click complete, the better," but about letting the next person who views the data clearly know:Why the customer contacted you, what was done this time, what the final result was, and whether anything still needs to be tracked.

FAQ

The customer has stopped replying, so should I complete the service?

Not necessarily. The customer not sending another message for now only means there is no new conversation content at the moment. If the issue has been resolved, you can complete the service according to company procedure; if you still need to wait for another department, reply to the customer, or continue tracking, you can keep the service open or create a ticket first.

If the call has ended, does that mean the service is complete?

Not necessarily. Ending the call means the conversation is over, but the service itself may still need additional notes, a ticket to be created, follow-up results to be awaited, or a service result to be selected. After these necessary tasks are done, ending the service is better for preserving a complete record.

Why do I have to record a service tag or service result?

Whether it is required depends on company settings, but the value of structured records is that they make it possible to later count "what issues customers contact us about most often" and "how they are usually handled in the end," making them much easier to use for reports, quality management, and analysis than simply keeping a text note.