Lessons Learned from Customer Service Management Experiences
Over the past two decades, we have learned two main lessons from our customer service management experiences.
Help Desk (Ticketing) Is Not Enough.
In short, within a typical ticketing-based help desk, you collect an issue, forward it to the relevant people via email, and then wait for an answer. Hopefully an answer comes back fairly quickly and then you can return to the customer. You can track an issue only through its status, such as “new”, “in-progress”, “resolved”, etc.
There are hundreds of ticketing solutions, but we believe that ticketing-based help desk solutions result in fragmented customer service. That is, when an issue requires the contribution of other units, partners, suppliers, etc., it is mostly done by emailing the issue to the relevant people or submitting it to another system, yet customer service departments are still in charge of the whole resolution processes. Customers are waiting for answers from customer service.
Problems of Fragmented Customer Service
- Using emails as a workflow tool: When you have an issue, you forward it to the relevant people or units by email. If you or your customer want to hear about the status of the issue, you have to call or ask via email. You only have an “in-progress” status at hand during the whole resolution process. You have no single tool for monitoring what is being conducted on which issue.
- Using other systems as a workflow tool: After capturing the issue, if you submit the issue to another system (rather than email) to be tracked, this fragments the issue life cycle and you now have to track it in two different systems. If you would like to receive a report about the full issue life cycle (for example, which units were late, which ones were on time, who was doing what on an issue) then you have to combine the data in both systems to formulate a single report.
Different types of issues require different types of resolution processes
- For each type of issue, you need to ask different sorts of questions while capturing the issue details.
Different forms for different types of issues
For example, the process for resolving “bad employee behavior” issues is completely different when compared to resolving issues of late delivery. When addressing the first problem, you need to ask the customer about the name of the store, where and when the “bad behavior” occurred, and what the “bad behavior” was. In the case of late delivery, you may need to ask the customer for their order number and other details.
- For each type of issue, different units should be involved in the resolution sequence with different service durations.
Different workflows for different types of issues
For the “bad employee behavior” issues, you may request a report from the store about the case. In the next step, you may ask HR to come forward with a decision.
In the late delivery case, you may ask the operations department for the shipment details. You may also request the delivery data from the logistics company and so on.
However, if you are using a ticketing solution, you have only one flow, which is to forward the issue to the relevant unit which you think should be in charge. You can track only the status of the issue.
The untrackable, unmeasurable secret box: “in-progress”
It should be noted that merely being aware of the status of an issue is not enough. We need to know more about what is really happening within the “in-progress” status. We need to open up the secret box and organize the thousands of customer issues being forwarded chaotically back and forth between departments.
Forwarding the issue and asking about what is happening with the resolution will slow down the customer service experience and may even lead to an unhappy customer. Issue management is, therefore, process management.
Single view of issue life cycle
For each type of issue, we need to design the resolution process:
- What will be the resolution workflow steps?
- Who will be incorporated within each step?
- What will be the actions within each step?
- What should the service levels be?
Only process-based customer service management provides:
- Performance KPIs: Who is late? Who is on time? What are the service levels of partners, suppliers?
- End–to-End Issue Tracking: A single view of an issue life cycle. Who is doing what on an issue? What should the person in charge do, what were the previous actions, and what will be the subsequent actions?
- Improvement Opportunities: How can we improve the processes for better customer satisfaction and to reduce issue resolution costs?
No IT Then No Cry
Whatever established software you have, however well it meets your current requirements, or however user-friendly it is, it doesn’t really matter too much. Every piece of software will have to be modified eventually in order to adapt to changing requirements.
However, IT departments usually have long pending task lists and hectic schedules. Whenever you have a change request for them, they will most probably direct you towards their limited resources and budget. You will find yourself in a situation where you have to explain why you need the changes, the expected return value from this change, etc. Even if you finally convince IT to schedule your requests, you’ll then have to deal with man-day budgets, project plans, delivery dates, postponements, and delays. By the time you get the change implemented, it may be too late.
On the other hand, from IT’s perspective, never-ending change requests and wish lists must be planned in an appropriate way. Therefore, software solutions that reduce dependency on IT would be the choice of IT departments also.
You will need flexible software that will let you reduce the business unit’s IT dependency. Namely, the business units should be able to design and modify workflows and forms on their own.
In next4biz’s administration interfaces, you can define or change the category structure, customer issue types, communication channels, issue root causes, departments, regional working hours… in short, you can change every parameter to customize next4biz for your own needs.
Moreover, next4biz provides design editor tools that business units can use to design or change forms and workflows by themselves without any technical assistance. Our customers have been doing it for years.
For instance, in the diagram below, a request has arisen to add a multiple-choice box field into the “late delivery” issue form.
A new field (logistics company) has been added without writing a single line of code.
In another example below, a new workflow step has been added to the process design. Needless to say, you can also change the SLA or escalation scheme without writing any code!
This example workflow can be easily edited from two steps to there or more steps.
A new unit has been added to the “Personnel Behavior” resolution workflow within a couple of minutes.
A Comparison Between Traditional and Non-Code Solutions (next4biz)
The diagram below compares the delivery and ongoing costs of implementing and maintaining customer service management solutions.
The vertical and horizontal lines represent the cost and time dimensions respectively. Using next4biz’s software, delivery duration and delivery costs are far less compared to those in traditional cases.
But what will the cost be after delivery?
As a result of changing requirements, sometimes you will need to add a new field on an issue form. You may discover more efficient ways of resolving issues or need to improve your workflows or processes. Or sometimes you may have to change the agent scripts based on your agents’ experiences. next4biz is a no-code solution, meaning you can design new processes or customize the current ones without the need for any technical assistance.