Date Published: January 12, 2014 - Last Updated 3 Years, 164 Days, 22 Hours, 3 Minutes ago
This article originally appeared in the HDI newsletter in December 2013.
If you’re like most consumers, you’ve probably experienced a chat session. Perhaps you engaged in chat with an agent at your bank or insurance company to resolve a payment issue. Or perhaps you used chat to troubleshoot your new computer or a new software application you installed.
Why chat? One reason is that some people simply prefer this channel for service and support; the fact is, chat is the channel of choice for a growing number of consumers and businesses, particularly among millennials. The second reason is economics. An effective chat channel can significantly reduce the cost per transaction versus the more traditional (live voice) support model. Because of this, chat has the potential to both improve customer satisfaction (by giving customers an alternative channel choice) and reduce cost per contact.
Costs are typically lower in the chat channel because chat agents can generally handle more than one chat session at a time. These are called concurrent sessions, and some agents are talented and skilled enough to handle as many as four concurrent chat sessions. When agents handle more than one session at a time, cost per session decreases accordingly.
Many chat metrics simply mirror their live-agent counterparts. For example, customer satisfaction for chat is the same metric as customer satisfaction for the live (voice) channel. However, the values for the metrics in each channel are likely to be different. Customer satisfaction in the traditional voice channel might be 80 percent, while customer satisfaction for chat might be 90 percent, or vice versa.
The metrics listed below are common to both the chat and voice channels. Some names might vary slightly; for example, speed of answer in the voice channel becomes speed of response in the chat channel, and call abandonment rate becomes chat abandonment rate in the chat channel.
- Cost per contact
- Cost per minute of handle time
- Contacts per agent per month
- Agent utilization
Service Level Metrics
- Average speed of answer/average speed of
- Call/chat abandonment rate
- Percent answered in 30 seconds
Contact Handling Metrics
- Inbound contact handle time
- Customer satisfaction
- First contact resolution rate
- Call/chat quality
- Agent Metrics
- Annual agent turnover
- Daily agent absenteeism
- New agent training hours
- Annual agent training hours
- Agent tenure
- Agent job satisfaction
But there’s another category of metrics that are unique to chat, including:
Percentage of contacts originating in chat: As the name suggests, this is the percentage of all contacts coming into the service desk that originate in the chat channel. As a chat channel matures, this metric normally increases.
Percentage of contacts resolved in chat: This number will be less than or equal to the percentage of contacts originating in chat. Once again, as the chat channel matures, this metric normally increases.
Failover rate from chat to voice (%): This measures the percentage of chats that “failover” to a live agent contact. This happens when the agent or caller feels that voice communication is needed and they revert from the chat channel to the voice channel to complete the transaction.
Average concurrent chat sessions: This metric indicates the average number of concurrent sessions a chat agent has open at any given time. The ability to handle concurrent chat sessions is the primary economic advantage of the chat channel.
Maximum concurrent chat sessions: Most organizations limit the number of concurrent sessions an agent is allowed to handle. Newer agents might be limited to a single chat session at a time, while more experienced agents might be allowed to handle as many as four concurrent chat sessions.
Service desks that are interested in growing, improving, and optimizing chat can use these metrics to effectively manage the chat channel.
Which chat metrics does your contact center track? Share in the comments below.