AI has already fundamentally shifted our approach in many industries already. And customer service is no different. Experts believe in the coming years we will eventually reach a point where
Eric Broulette, Director of Global Support at Flywheel joins us in this episode of Support Ops Simplified to discuss customer support analytics. Connect with Eric and Flywheel here: Eric Broulette
Eric Broulette, Director of Global Support at Flywheel joins us in this episode of Support Ops Simplified to discuss customer support analytics.
Connect with Eric and Flywheel here:
The majority of Flywheel’s support team are located in Omaha, Nebraska with a small amount in Europe and the rest in Australia.
Eric ensures that there is a full handover between each team at the end of every shift to ensure no ticket is left behind.
Eric and Flywheel’s two core tools are Zendesk for support tickets and Livechat for chat communication.
CSAT is a good, reactive real time feedback metric (though Ryan Steinberg tells us how it can be gamed in this interview) that Eric measures in both tickets and chats. There are two other metrics that Eric looks at a high level: “median ticket resolution time” and “chat queue wait time”. Eric looks at these metrics on a weekly, monthly and annual basis.
Eric and Flywheel create “team norms” whilst training and onboarding reps to drive a consistent customer experience across the time zones (our host Sid talks more about creating a consistent customer experience in this episode.)
Flywheel customers on lower price plans can only communicate with their support team through live chat. Premium customers receive phone support.
Eric made small incremental changes to reduce chat wait time. For example, they looked at times with heaviest volume and ensured that more reps were working during those times. They were able to hit this goal with small workflow changes and an increased investment in training.
There is a standing meeting between support team leads and product managers to give team leaders the higher level view, they can ask questions and give feedback about features that could be added to the roadmap.
They are encouraged to bring data to this meeting to give weight to their feedback e.g. “we received two hundred tickets this week related to this issue” instead of “we need to fix this issue”
Flywheel will aim to provide help for their customers where they need it most… And it may not include people. E.g. if a customer is having an issue with directing their DNS, can they move through an automated workflow?
As a support leader, Eric sees his core role is to make the lives of his support reps easier!