Great CX Starts With Happy Agents

Listen and subscribe to our podcast:

In this episode of the Customer Service Secrets Podcast, Gabe Larsen is joined by Derek Hixon to talk about his lessons learned after providing over 15 years of exceptional customer support. Listen to Derek’s fun and invigorating life lessons in the podcast below.

Fostering Relationships Leads to Better CX

Derek Hixon, Director of Customer Support and Implementation at WordStream, proudly leads his team of reputable customer service agents. Having over 15 years of customer service experience, he has learned the best methods of garnering customer loyalty and agent happiness, starting with fostering relationships in the workplace. Derek believes that the best customer service experiences start with a happy team of CX agents. To present this idea, he states, “Everything starts with the team that you have working for you and if they’re not happy with you or with the role, nothing’s going to work. So that’s where your primary focus has to be initially. You always got to stoke that flame to make sure that they’re happy and cool with you.”

Derek finds that when his team is happy, their positivity trickles down and reflects in their work. They are able to have more productive conversations, find the best solutions to their customer’s needs, and have better overall CX scoring. When those genuine daily interactions take place, the work environment becomes more comfortable and interactive, ultimately resulting in the best customer service experiences.

Utilizing Data as a Tool

Data is a driving force in innovation. It presents the information needed to push internal growth and to modify methods and tools to better suit the needs of the customer. When customers use a product and don’t understand how to use it, Derek finds that is the right opportunity to learn from their data and to innovate that product as well as alter their CX approach. He says, “Data is key. It’s not the only thing, but you need solid data to make informed decisions.” Using data to gauge what your customer expects from a product has proven to be extremely useful with Derek’s CX process. Data can give the information needed to build internal tools that assist customers, or remove the need for internal CX tools all together by creating an effortless experience. Having a high-level view and taking the small but necessary steps to creating the ultimate satisfactory customer experience through using data can be very beneficial to companies.

Building on Each Other’s Strengths

Something all companies would benefit from is employing each team member’s strengths to work together and create a cohesive CX team mindset. Early on in his career, Derek found that each person offers specialized skills for their job and that utilizing that specific knowledge has proven to be advantageous to the company. He explains, “I think when you’re working with people with different expertise and skill sets, that’s where true innovation really can happen. That’s where you can really have the biggest impact on the business and the customer experience.” He notes that unearthing each team member’s strengths takes patience because oftentimes, they are used to completing tasks in specific ways, and their specialized knowledge gets buried under the day-to-day cycle. Breaking that cycle can be done through engaging with the team, learning from the team and pulling from their skill set. CX teams would be wise to learn from each other and to use their specialized knowledge to build on each other’s strengths.

To learn more insightful life lessons, check out the Customer Service Secrets podcast episode below, and be sure to subscribe for new episodes each Thursday.

Listen Now:

You can also listen and subscribe to our podcast here:

Full Episode Transcript:

Great CX Starts With Happy Agents | Derek Hixon

Intro Voice: (00:04)
You’re listening to the Customer Service Secrets podcast by Kustomer.

Gabe Larsen: (00:11)
Hi, welcome everybody. We’re excited to get going. Today we’re going to be talking about lessons learned from running 15 years of successful support operations, and to do that, we brought on Derek Hixon, who’s currently the Director of Customer Support and Implementation at WordStream. Derek, how the heck are you?

Derek Hixon: (00:30)
I’m doing great. How are you doing Gabe?

Gabe Larsen: (00:32)
Yeah, pretty good. Well, I’m pretty good, man. We had an interesting morning. But I got to ask, man, it sounds like you’ve got a fun hobby on the side, is that true? You’re a DJ by night, by day, by, what is it?

Derek Hixon: (00:45)
I’ve been trying to retire for years, but I can’t get out of the game, I guess. I do DJ around Boston, specifically a place called State Park in Cambridge that I really like and I also make some music on the side and actually I think being creative is very important to me. And I think what I learned outside of the walls of work really helps me inside them as well. So –

Gabe Larsen: (01:07)
That’s awesome, man. Been doing it for years? As long as you’ve been doing support or not really?

Derek Hixon: (01:12)
Oh, I’ve been messing with music since I could walk, so yeah, long, long time.

Gabe Larsen: (01:17)
Love it, man. That’s fun. I’m just getting my boy into guitar lessons. I always wanted to be a jammer, but I just never had the guts to stick with it. So we won’t make you say your DJ name, but if you want to know that you’ll have to ping Derek on LinkedIn. So outside of DJ, give us your quick background real quick.

Derek Hixon: (01:40)
So, I’ve been working within technical support organizations for the past 15 plus years now. Before that I was working within a company called Pearson and, sorry, I’m just going to take a beat for a second. I can’t even talk about myself. So I’ve been working in technical support organizations for the past 15 years and I have a pretty diverse background in media as well. I’ve worked within print production. I’ve worked within the education sphere. I’ve worked within big media and video and I have a fairly diverse background in communications and I’m also in media.

Gabe Larsen: (02:32)
Awesome, man. Well, it definitely sounds like you’ve got a robust background. Want to see if we can pull out some of that today, as we talk about just lessons learned. I mean, you’ve been at different companies, you’ve been in different industries. What are some of those things that just stand out as, “Man, as I’ve looked back at my career, these things have been kind of the make or break things that have made me more successful?” Start at the top. What comes to mind?

Derek Hixon: (02:57)
Oh, it’s funny. I think I’ve fallen into a technical support role and leadership role kind of by accident, but that’s kind of life too. I think life’s very non-linear and you kind of got to go with the waves and fight against them or you’ll drown. And I was working in publishing many moons ago and it was a big publishing company and I was rising up the ranks well, and I had a pretty big team and across multiple cities, but I just wasn’t feeling the culture or just the industry, so to speak. So I was looking for my next new big challenge and I heard of a company called Brightcove at the time. And what excited me about them is that they combined two of my loves, technology and also video. And this is back in 2008, 2007, and YouTube was only a year old. Having video on the internet was the wild, wild West. It was exciting, new, and hard. Which all of it really intrigued me. I had a friend who recently joined there and all they had open at the time was a single contributor support role. And I’ve debated in my head because I had this good career path. I had a good bonus. I liked the people I worked with at the time, but I wasn’t really challenged in ways I wanted to be. Way back in the day I went to school for video and I was going to be the next great Steven Spielberg or something like that. So it was a way for me to still kind of plug into that world as well. So I kind of rolled the dice and I interviewed for a position. I got the single contributor position and this is 2008 and it was about two weeks after I accepted that the whole economy fell through the floor. And I thought, I remember one day specifically, I was going up the elevator and I thought it was gonna be going right back down it. We had to do some layoffs. They were a startup at the time and I was able to survive it thankfully. And the thing I realized real quickly at Brightcove that was different than at the previous company I was at was, and some of this may be due to me at the time, me being in my mid to early twenties, but I thought I knew everything. And I always felt like I was the smartest guy in the room and real quickly at Brightcove, I realized I was not the smartest guy in the room. I was far from it. And it was very intimidating at first for me. I had a lot of fakers syndrome. I was like, “Why did they hire me? Like this was a mistake. Like I shouldn’t be in the room.” But what that really did for me is it threw me into survival mode and I’m like, “Okay. Well, if I’m not going to be the smartest guy at the table,” like I was literally, ActionScript was a thing back then. Rest in peace Flash. I like literally, the guy who was sitting across the table from me, wrote the book I learned from and I was just like, “This is ridiculous, I can’t compete with this level of knowledge.” So what it instilled in me was, I’m like, “Okay, if I can’t be, if I’m not going to be the smartest guy in the room or at the table, I’m going to be the most prepared. I’m going to be the hardest working.” Really what I started doing, the seeds I started lying just to survive, ended up being very helpful for me throughout my career as I grew in different leadership positions in technical support organizations. And what I’d really tried to do initially was I had brilliant coworkers, but they had all this brilliant knowledge trapped inside their heads. So I was just always pinging and poking at them to try and learn from them. And then I was trying to transfer all that down to paper or Google Docs or whatever it was or Confluence or whatever it was at the time, and create my, and it was really a selfish way for me to do documentation. And so I had the knowledge, so I could do my job better. But by getting that mindset, it’s really helped pave a path for me to where I am today.

Gabe Larsen: (07:10)
I love that man. That’s powerful. So one of the big keys was, it sounds like you kind of thought a little high, got yourself in the deep water, neck deep, but you were able to figure it out. And one of the keys was just being able to kind of, sit with that team, really spend some time and pull stuff from them and not just do the conversations, but actually translated into a document or something that could be shared with others or shared with yourself so that you could actually say, “Hey, this is what this process looks like. Or this is what this function, or actual detail looks like,” is that correct?

Derek Hixon: (07:49)
Yeah, that’s exactly right. And that’s something I’ve noticed from my early experiences at my first technical support experiences at Brightcove all through the last few roles I’ve had is I’ve been really blessed throughout my career to work with really brilliant people. And sometimes it’s just helping organize the really good knowledge that they have. Like everyone has very specialized knowledge for wherever they work, but sometimes it’s trapped within and like trying to really get hive mentality and spread the love with what they have.

Gabe Larsen: (08:23)
How [Inaudible] I mean, I think most of us know that intuitively, but it’s always hard to kind of pull it out of people and then get it into, again, a format that’s digestible. You just take, is it just about taking the time? Is it about the right questions? What’s kind of the secret to getting that richness out of people and into a place that can be digested?

Derek Hixon: (08:43)
Yeah. It’s a lot. It’s a bunch of things you have to be patient with. I’m like old school at heart. I like to DJ. I DJ with vinyl only. I don’t like DJ out digitally. If I cook I’m grilling with charcoal, I don’t want a gas grill. It’s just kind of my nature. I just think things are better if they’re done right and slowly, and usually you benefit from it in the long-term. You can always get short-term success with things, but if you have the luxury of time, which you don’t always have obviously, you can do really great things. And I also think just keeping it real with people and being transparent can really get you a lot of credit with people to get trust within you. To kind of pull things out, but it takes time. And where it really starts is, it’s process, right? Process is what everyone’s chasing in a leadership role. They want people to do things in a similar manner. I don’t necessarily want everyone on my teams to do things exact. And I compare, I like sports as well. And when I talk to my team, I’m really, really good at bad analogies. And I like to equate how they do their job, like a golfer and a golf swing, or a baseball player in their batting stance. It doesn’t have to be the same exact stance or swing for everyone, but we’re all trying to get the same results. You’re trying to drive the ball straight and far down the middle, or you’re trying to get a base hit or a home run. When I’m sitting with people, you really have to sift the team, you have to take the time. You have to stroke the coals, you have to prepare for a DJ set, like you have to really understand, “Okay, what’s their day-to-day like?” And that goes through shadowing. Okay. And like I always say, cliques kill. You can do things to simplify your team’s job, you’re getting quick wins and you’re making their lives easier, which is going to filter right down to the customer. And so that’s where you start. And also people like talking like, hey, I’m doing it right now. People like talking about themselves. People like showing off the things they know and it also gives people a chance to feel empowered and talk about the hard work they’ve put in and how they do it.

Gabe Larsen: (11:02)
I like that. Then through all of these interviews you’ve done and different stakeholder discussions, et cetera, any quick things you’ve found that ultimately changed the way you look at support, ideas around simplicity, or people making it harder than they maybe need to sometimes, but different things like that?

Derek Hixon: (11:24)
Yeah. I think that it’s hard to see the forest through the trees type of thing, fully applies when it comes to support. And I think support at times traditionally can have a bit of a stigma. It’s literally at the end of the big funnel from sales to marketing, through products; we’re at the very end. But also, we’re at the end of one part of the process where we’re at the tip of the spear for the customer part of the process of how they’re using a product and where they’re running into things. And I think that it’s just really important to, I’m sorry, what was the exact question? I kind of went off there a little bit.

Gabe Larsen: (12:05)
No, no. It’s totally fine. I missed some of the lessons learned as you interview some of these people and, just curious if there’s general findings. What did you find [inaudible] people ‘complexify’ stuff or –

Derek Hixon: (12:20)
Yeah. Yeah. I think sometimes, and this is the, I find this especially when I first join an organization is I really lean into it when I hire somebody new as well. New blood is invaluable, new perspectives, just new angles on looking at things. Sometimes people live with a certain way of doing things for so long or someone told them to do it a certain way. So they just will do it a certain way. And that’s just the way they’re going to do it forever. And it goes back like, I have a saying that I always tell my team is like cliques kill. And like, if we can simplify the amount of things like tools needed to accomplish a task or ways to assist someone, that’s where it helps. And also I think the other hard thing, a thing I’ve seen across the, when I’m working with people to try and figure it out and simplify the job is, a lot of times, people are afraid to take a short-term hit to get a long-term gain. And I kind of almost look at it like preventative medicine or it’s like if sometimes teams are really scared to take some steps back and look at, “How do I do my job? Well, what are the steps I need?” instead of actually just taking the cases and doing them because like, “Oh, if I’m doing all this stuff and I’m not taking the cases, are cues going to really grow?” And I’m like, well take that short-term hit because it’s going to like, if you take time on this one case it’s going to help, or if you write an article on this one type of case and we post it, it’s going to help hundreds of people down the line and it’s forever going to be evergreen and all that jazz. So it’s helping the pulp. I think that’s, really it’s the benefit I have in the positions I’m in now. I used to be in the trenches, just like the people on my team, taking the cases and doing the calls. You don’t always have the luxury to pull yourself above the clouds and look down at everything. But to be able to do that with the team and allow them that freedom really helps them to help the customer experience better, how the team works better, and also helps them get a different perspective on things and potentially, like I think when people talk about support and customer success so much, they’re always just talking about the customer, but the customer experience is going to suck if the people on the team supporting them aren’t happy, or don’t what they’re doing, or don’t feel like they’re growing. Not everyone’s going to be a support lifer, and that’s cool. I’m sure yourself, you’ve had many different turns throughout your career. But when people are on my team and they’re working with me, I want to know what their goals and aspirations are. And I want to figure out how, when they’re in the current role they’re in with me and my team, how can I help grow skill sets that will help them accomplish larger goals while also helping the immediate goals with what the team has now? So, I really think it’s hard. I think the biggest secret is pulling people out at times and understanding what their path can be and the results will filter out throughout to the customer, the data will start pointing in the directions you want, and you’ll just create a really good working environment where people enjoy being, and working, and pushing and pulling in the same direction with each other.

Gabe Larsen: (15:46)
I like that. So, one big thing is just understanding your team, what they’re doing, learning from some of those findings. The second thing that we touched a little bit about was this idea of case analysis and what do customers really need help with? Talk about how that’s been a lesson that you’ve learned and how that applies to kind of transforming service organization.

Derek Hixon: (16:10)
Yeah. Data is key. It’s not the only thing, but you need solid data to make informed decisions. And so it goes back. And so in the very beginning, if I’m shadowing, it’s like if I got a new job at CompanyWide tomorrow to run their global customer support organization, the first thing I would do would be sit down with the team and understand what their day-to-day is like. And it’s not just to make sure their to-kill cliques and to make their day-to-day more simple, but I want to understand what the cases are and what the questions are that they’re answering and asking. I’ve done this primarily, this is nothing new, but I do this primarily through using case-reasons and sub-reasons at the case level. That means like, if it’s a billing question, that would be the case reasoning. And then from there, the sub-reason could be, “When’s my next bill due? I want to cancel. Where do I find?” Once you can bucket out what the customers are writing in about into different reasons and sub-reasons, then you can really start building a map of what people are actually asking the team about. Really, I don’t look at support, I always kind of looked at as support as a secret part of product because that’s what the, people are using a product.

Gabe Larsen: (17:38)
Agreed. Agreed.

Derek Hixon: (17:38)
We’re all consumers and we’re all going to have questions on things at some point in time. So I love working as support just because I think it’s good karma. When people are putting their heads against something, and they have a question, it’s because they’re using the product and it’s not working, or they don’t know how to, or they don’t want to figure out how to, because they still have time to sit down and figure out all the things. So really understanding what the people are asking about and then once you understand what they’re asking about, the real proof in the pudding is what action are you taking on the data, and who are you sharing that data with? It’s always easiest initially, to affect things internally, meaning within the support organization, but when you really start developing at my level relationships with peers across the aisle, and in marketing, in products, in engineering and development, that’s when you can really, really, really start doing some great stuff with the data such as creating internal tools. So you can do better work for the customer, or even better, make those tools available for the customer, or make it so the tool is not even needed because the thing just happens. Oftentimes, just from analyzing product usage data, a lot of places where customers might butt their heads against the wall, aren’t going to show up because they’re going to support those sort of things.

Gabe Larsen: (19:07)
I like that. I mean, sometimes the devil’s in the detail, man. It’s finding that, I love the idea of this case-reason and really being able to figure out what’s working, what’s not working, can be, I mean, it just opens up so much insight as to where you potentially need to go. I liked that one. And then number three, you talked a little about this idea of working in a box. Jump into that for a minute. How does that apply to kind of lessons learned?

Derek Hixon: (19:30)
Yeah. My favorite thing about working within a technical support organization is that, when I’m working at a software company, you work with and you talk to everyone within the company. Like then that goes from a tier one associate on my team to me. We’re talking to account managers, we’re talking to marketers, we’re talking to sales guys, we’re talking to product, we’re talking to engineers. And it’s really nice to have like our tentacles throughout the company that way. And like, what really gets me off is cross-collaboration. I think when you’re working with people with different expertise and skill sets, that’s where true innovation really can happen. That’s where you can really have the biggest impact on the business and the customer experience. So, I try and really foster relationships there. It’s not easy. It can be really hard at times because all the different segments have different goals, and different OKRs that they’re pushing towards. Hopefully everything will roll up to the greater good, but it’s hard for all of it to cross over exactly. And just being realistic with where support lies within the totem pole of things at times, if you can learn how to work within other teams, cross-functional OKRs, and whatnot, you’ll have better success with what you’re trying to do instead of trying to jam a square through a circle hole. I’ve tried to jam a lot of squares through circles, so I’ve learned through a lot of failure, and I’ve been far from perfect. But hopefully I’m getting a little bit of wisdom with age, but to be determined.

Gabe Larsen: (21:14)
Wow. Well, I totally understand where you’re coming from. It seems like I get smarter with age, but then I look at myself and I look at my life and I’m like, “No. I’m not.”

Derek Hixon: (21:27)
Exactly.

Gabe Larsen: (21:29)
BS’ed my way through everything. Well, we covered a lot today, Derek. As you think about other service support leaders out there trying to win, what’s kind of a summary takeaway that you’d leave with the audience based on some of the stuff we’ve chatted about today? Any quick kind of quick summary comment?

Derek Hixon: (21:50)
Yeah. I would just say, know your team and then use the data as a tool. Everything’s a tool. Like, there’s a phrase, “Death by a thousand paper cuts,” and I like to apply life by a thousand paper cuts. We’re always, and like the real big phrase that I say to my teams is, “Green grows and ripe rots.” Meaning like, as soon as you think you’re good and you know everything and you start being stagnant, you’re screwed. And like, I try and have a mindset of always wanting to grow and learn and understand, and we’re always tweaking things, but we’re never making this huge, big, crazy change, but we’re always making series of changes based on the data we’re getting and through just keeping a really open communication within the team. And from there, there’s no whiplash had by the team by all these big changes, but if all of a sudden we look back six months, we’re like, “Oh wow, we did a lot. We used to do things this way? That was crazy.” So I think just really having a high-level view of things and I’m not trying to boil the ocean, but always trying to slowly innovate, push, and move forward. But like, everything starts with the team that you have working for you and if they’re not happy with you or with the role, nothing’s going to work. So that’s where your primary focus has to be initially. You always got to stoke that flame to make sure that they’re happy and cool with you.

Gabe Larsen: (23:15)
I love it, man. Alrighty. Well, a lot to cover. Definitely a lot of experience coming out. I can hear the wisdom in your voice. I’ll have to join you in Boston sometime when things calm down with all that’s going on with the COVID, et cetera. It’d be fun to hear you DJ, man. So anyways, thanks for joining and for the audience, have a fantastic day.

Exit Voice: (23:40)
Thank you for listening. Make sure you subscribe to hear more Customer Service Secrets.