Category Archives: Helpdesk

CRM, Customer Experience, Customer Management, Helpdesk, Tools

How Help Desk Software Increases Your Customer Support ROI

1 Comment

If you want to invest in customer support software such as Freshdesk, you may be wondering if the cost of the software will pay off. It can be tricky to calculate the return on investment (ROI) of your new tools.

One of the things you need to consider is if it will bring in revenue. Most help desks are cost centers, but if the software reduces the cost of doing business it is still a benefit. This is one of the most important questions that you must get answers before you start using the software. The software can be effective in measuring the impact of your actions on the business metrics. It is possible to make customer support into a revenue generator and not just a cost center.

Nowadays, things are changing, and more customer support teams are focusing on driving growth in businesses and proving their worth to the business. Using the right software can make your customer care more effective in generating revenue. Freshdesk, for example, can help you streamline your customer conversations, automate your repetitive work and collaborate with other teams to solve problems faster. Software for help desks should save money and bring money into the business in order to create a return on investment.

How to Measure Your Investment in Software

If you are at the stage of putting processes into place to support your business’ customer of if you want to fix some gaps in your system, the right help desk package will ensure that you get back to all clients in a timely manner.

This is an important baseline to meet. If you miss one email just once, you can cause your customers to stop doing business with you. 86% of customers quit doing business with companies because of poor customer service. 51% of customers quit doing business with a company for one poor customer experience. All the lost customers lead to lost revenue. Read on to understand different ways of investing in help desk software, save revenue in your business, and increase your customer service team’s ROI.

Move to a Streamlined Queue

Help desks were originally made around the idea of tickets. This can still be seen at the butcher. You take a ticket number and get services in the order that you came in. Nowadays; your businesses shouldn’t treat customers like tickets anymore.

It is important to adopt a nuanced approach to organizing questions from customers. You can become adept at managing messages from customers by using modern help desks. You can achieve this by prioritizing customers who seem to be more upset or customers who have a high opportunity of converting to paid customers. Businesses should invest in help desks that offer better management of queue. This will make customer support teams to more effective.

Self-service Should be Part of Your Customer Service

Businesses should have the ability to offer content in the form of FAQs and knowledge base articles to help customers be able to help themselves. Businesses should understand that self-service is another form of customer service. Self-service carries the highest ROI for different reasons.

Customers like being able to help themselves. 70% of customers like to see an option on your website where they can help themselves. If you don’t offer this service, your customers will be frustrated and will need to contact you. On the other hand, 73% of customers prefer researching for answers on their own instead of talking to a human over social media and live chat. 81% of customers also try to help themselves before contacting human support.

Investing in software that allows self-service keeps the customers happy. Customers will keep coming back when they find it easy and convenient to do business with you. Apart from customers helping themselves, self-service also benefit you as a business owner or manager. Self-service is a cost-effective way of helping customers to resolve issues versus other business help channels. When you get self-service right, it is a cost-effective way of making your customers happy.

Personalize Each Transaction

You can build your customer loyalty by investing in your customers. You can focus on building good relationships with your customers beyond transactions. We should form holistic relationships with customers instead of treating the problems of our customers as a series of events that don’t relate to each other.

You should, first of all, know who your customers are before you think beyond the transaction. If all your customer service team can see is the question at hand, they won’t have a nuanced and personalized conversation about their customers’ needs.

Your help desk can provide additional context with different conversations. For instance, they might show you the last four conversations the customer initiated. If you have integrated your help desk with your CRM, you can see when the renewal date is coming up. You will also see how many users they are paying for. When the context revolves around the history of the customers, you can tailor your approach. You can easily see what your customers need and offer it.

Provision of valuable data

The return of investment of customer support is not always tied to sales . Businesses can also use customer support for research on users. This includes knowing what customers think of your product and how they use the product. You can also know what your customers think of your competition. You need help desk reporting that will capture trends for you to get all the information you need from your conversations.

You can use important data from your customers to enhance the efficiency of service delivery and improve the quality of your products to suit your customers’ needs.

Investing in Helpdesk Software – Money Well spent

Calculating the customer experience return on investment is a critical requirement for frontline teams. It is important to know how our actions affect the business. When we connect our customer support goals to the business goals, we move from making our customers happy to the value we create.

A Help desk plays a crucial part in the journey of connecting customer interactions and making money. This can be through increasing the power of your support team, improving the loyalty of your customers or uncovering important data. With all these, a help desks can deliver a huge ROI.

Helpdesk, Incident Management, ITIL, KPI, Problem Management, Service, SLA, Teams

WHAT IS A HELPDESK?

Leave a comment

OK, to start with it’s not a desk that helps people! A help desk is a team of individuals (generally support staff) that provide solutions and resolutions to customers experiencing problems. Generally working at the 1st tier of the support model they are responsible for Incident reporting and resolution vs. Problem Management (I shall discuss those terms in greater depth below).


What is an Incident?
Simply put, an Incident is anything related to customer contact (Incidents are also reported by automatic means via monitoring tools and I will discuss those types of incidents in greater depth in later posts). Incidents related to customers can be anything really – Information requests, Account Updates, Issue reporting are all examples of Incidents. Incidents can also be reported through a variety of different methods – this could include the phone (probably the most common), email (a close 2nd) and even chat. As mentioned previously, automated monitoring tools can also generate incidents.


All of these different Incidents coming from/through different sources would get routed to your Incident Management tool. For smaller teams, this could be something as simple as a spreadsheet but in larger organizations either in-house customer-built applications or enterprise level tools prevail.



Incident Management (in a nutshell)
Your helpdesk is responsible for reviewing the information in each of these incidents and checking if there is an appropriate solution already available to the customer. For those instances for example where the customer wishes to update their Account Information, the helpdesk would look at the Incident, obtain the correct new information (& assuming that all appropriate security questions had been reviewed) log into the customers account and update the information. Once the information had been updated, they would inform the customer and then close the Incident. This is probably one of the simpler examples of an Incident from start to finish.


If the customer is reporting a problem or an issue, the Helpdesk staff are responsible for updating the Incident with all the relevant details as supplied by the customer. If the customer’s issue matches a known fix they are able to inform or supply that fix to the customer, however, if that is not the case they would need to escalate the issue to the Problem Management team. The simplest way to think of the Incident Management (Helpdesk/Tier1) team and the issues they resolve is that if a “band-aid” exists they can apply it. If more drastic attention is required they will need to call the Doctor!



Problem Management
Problem Management is where the interesting work really happens. Incident Management due to its repetitive nature can get tedious and is definitely a drain on the more skilled staff in your organization … if you have people like that, think about moving them into Problem Management if you have such a team or create one if you don’t! Problem Management is more in-depth. It’s where more often than not a single Problem is the cause of multiple Incident’s from multiple customers … as such you want your best people at this level. Generally, you would consider this Tier 2 or Tier 3 from an escalation and staffing perspective and dependent on your product or service you would have some very technically oriented people there. Their goal is not to just provide a band-aid, but rather to find out why the problem happened in the first place and fix it. Ideally, they should be looking at ways to fix it in such a way as to ensure that it doesn’t happen again!!



KPI’s
Now each of these teams would have different metrics in place. Obviously, your Tier1 team (Incident Management/Customer Service/Helpdesk) needs to get back to the customer in a timely manner. Their goal as already mentioned is to fix it, fix it fast and move on. A band-aid will not always reattach the finger though, so it’s up to the Tier2 team to ensure that the surgery goes smoothly which obviously takes a lot more time as you don’t want the surgeon doing a shoddy job!
Response Time – So with that analogy in mind … you want to have an aggressive goal set for your Helpdesk – try to work with the 80/20 rule … 80% of incidents responded to in 20 seconds (If you have the resources, otherwise maybe 20 minutes? Or 20 hours (that’s less than 1 day so might still be good – especially if you’re doing email support)? Or 20 days ß well that’s probably not really worthwhile) but hopefully you get the point? You want to set a specific goal for measuring how quickly your customers are getting a response.
Resolve Time – notice that I have separated these out. As much as you’d like to be able to resolve 100% of issues at that first contact, it’s not always going to be possible. However, you can have another measurement in place that tracks this which is the Resolve Time (sometimes called MTTR (Mean Time to Repair)). The Goal here is also to get that band-aid on as quickly as possible so you need to ensure that your Incident Management system has some sort of a knowledge base which helps your staff find the solution to commonly placed issues/questions. If they have the answer every time, then a 100% resolution at 1st contact is achievable! If not, however … it gets a bit more complicated because all of a sudden your Incident Management team becomes the customer and the team they go to is the Problem Management team. Guess what? They have a different measurement for Response Time and Resolve Time too!


Problem Management Response Time – now as previously mentioned these are generally your more senior staff and as much as you’d like them to be available 24/7 unless you have an extremely large organization this is probably fairly unlikely. So you are going to have built or determined some relevant response times based on their availability. In addition, as these escalated issues are generally issues that cannot easily be resolved, your resolution time is going to be extended also. Pick some appropriate intervals that meet your customers SLAs. Your main goal for this team (in addition to resolving the problem of course) is communication, communication, communication!!! They must inform your customer-facing agents what the issue is, what they are doing to resolve it and when they expect to have it resolved. If they cannot provide an estimated resolution time, they MUST provide your Tier1 team with an estimated update time.
Helpdesk, KPI, Service, SLA, Teams

What is a Helpdesk?

Leave a comment

OK, to start with it’s not a desk that helps people! A help desk is a team of individuals (generally support staff) that provide solutions and resolutions to customers experiencing problems. Generally working at the 1st tier of the support model they are responsible for Incident reporting and resolution vs. Problem Management (I shall discuss those terms in greater depth below).

What is an Incident?

Simply put, an Incident is anything related to a customer contact (Incidents are also reported by automatic means via monitoring tools and I will discuss those types of incidents in greater depth in later posts). Incidents related to customers can be anything really – Information requests, Account Updates, Issue reporting are all examples of Incidents. Incidents can also be reported through a variety of different methods – this could include the phone (probably the most common), email (a close 2nd) and even chat. As mentioned previously, automated monitoring tools can also generate incidents.
All of these different Incidents coming from/through different sources would get routed to your Incident Management tool. For smaller teams, this could be something as simple as a spreadsheet but in larger organizations, either in-house customer-built applications or enterprise level tools prevail.

Incident Management (in a nutshell)

Your helpdesk is responsible for reviewing the information in each of these incidents and checking if there is an appropriate solution already available to the customer. For those instances for example where the customer wishes to update their Account Information, the helpdesk would look at the Incident, obtain the correct new information (& assuming that all appropriate security questions had been reviewed) log into the customers account and update the information. Once the information had been updated, they would inform the customer and then close the Incident. This is probably one of the simpler examples of an Incident from start to finish.
If the customer is reporting a problem or an issue, the Helpdesk staff are responsible for updating the Incident with all the relevant details as supplied by the customer. If the customer’s issue matches a known fix they are able to inform or supply that fix to the customer, however, if that is not the case they would need to escalate the issue to the Problem Management team. The simplest way to think of the Incident Management (Helpdesk/Tier1) team and the issues they resolve is that if a “band-aid” exists they can apply it. If more drastic attention is required they will need to call the Doctor!

Problem Management

Problem Management is where the interesting work really happens. Incident Management due to its repetitive nature can get tedious and is definitely a drain on the more skilled staff in your organization … if you have people like that, think about moving them into Problem Management if you have such a team or create one if you don’t! Problem Management is more in-depth. It’s where more often than not a single Problem is the cause of multiple Incident’s from multiple customers … as such you want your best people at this level. Generally, you would consider this Tier 2 or Tier 3 from an escalation and staffing perspective and dependent on your product or service you would have some very technically oriented people there. Their goal is not to just provide a band-aid, but rather to find out why the problem happened in the first place and fix it. Ideally, they should be looking at ways to fix it in such a way as to ensure that it doesn’t happen again!!

KPI’s

Now each of these teams would have different metrics in place. Obviously, your Tier1 team (Incident Management/Customer Service/Helpdesk) needs to get back to the customer in a timely manner. Their goal as already mentioned is to fix it, fix it fast and move on. A band-aid will not always reattach the finger though, so it’s up to the Tier2 team to ensure that the surgery goes smoothly which obviously takes a lot more time as you don’t want the surgeon doing a shoddy job!
Response Time – So with that analogy in mind … you want to have an aggressive goal set for your Helpdesk – try to work with the 80/20 rule … 80% of incidents responded to in 20 seconds (If you have the resources, otherwise maybe 20 minutes? Or 20 hours (that’s less than 1 day so might still be good – especially if you’re doing email support)? Or 20 days ß well that’s probably not really worthwhile) but hopefully you get the point? You want to set a specific goal for measuring how quickly your customers are getting a response.
Resolve Time – notice that I have separated these out. As much as you’d like to be able to resolve 100% of issues at that first contact, it’s not always going to be possible. However, you can have another measurement in place that tracks this which is the Resolve Time (sometimes called MTTR (Mean Time to Repair)). The Goal here is also to get that band-aid on as quickly as possible so you need to ensure that your Incident Management system has some sort of a knowledge base which helps your staff find the solution to commonly placed issues/questions. If they have the answer every time, then a 100% resolution at 1st contact is achievable! If not, however … it gets a bit more complicated because all of a sudden your Incident Management team becomes the customer and the team they go to is the Problem Management team. Guess what? They have a different measurement for Response Time and Resolve Time too!
Problem Management Response Time – now as previously mentioned these are generally your more senior staff and as much as you’d like them to be available 24/7 unless you have an extremely large organization this is probably fairly unlikely. So you are going to have built or determine some relevant response times based on their availability. In addition, as these escalated issues are generally issues that cannot easily be resolved, your resolution time is going to be extended also. Pick some appropriate intervals that meet your customers SLAs. Your main goal for this team (in addition to resolving the problem of course) is communication, communication, communication!!! They must inform your customer-facing agents what the issue is, what they are doing to resolve it and when they expect to have it resolved. If they cannot provide an estimated resolution time, they MUST provide your Tier1 team with an estimated update time.