Skip to content
28:32 min watch

Support can't do it alone: How to improve cross-team collaboration

In this on-demand webinar, Reg Gray, Head of Product Support at Aquila Learning, and Dan Sayer, Director of Engineering Quality and Support at Deskpro, talk about how they have both improved collaboration across their organization’s Support and Engineering teams to deliver faster results for customers. They share best practices for support leaders who need to work across any other teams or departments to solve complex issues.

Transcript:

Madeline: Hello everyone, thanks for joining us today. This month's webinar we are going to be covering cross-team collaboration on support requests. It's something that I know is on our team's mind a lot here at Deskpro. We work with a lot of customers in B2B customer support, HR, and IT, who all handle complex requests and often have to work across teams to get those requests solved. And I know that's something that our team deals with firsthand as well.

So, I am excited to cover this topic. My name is Madeline. I'm our Senior Content Marketing Manager at Deskpro today. I'm going to be our moderator. And I'm excited to introduce our two speakers. So, without further ado, today we're joined by Reg Gray, who is the Head of Product Support at Aquila Learning, and Dan Sayer, who is our Director of Engineering Quality and Support at Deskpro. So rather than going on a long preamble, I'd like to let each of you introduce yourselves and say a little bit more about your role. So Reg, would you like to introduce yourself first?

Reg: Yeah, thank you, Madeline. I'm Reg. I'm the Head of Product Support at Aquila Learning. We're a software company behind a product called ALARMS, which is a digital learning management system. I'm responsible for our product support function and how we manage the customer support experience. A big part of my role is looking at our support processes, how we work with customers, and how we use tools like Deskpro to make that experience as effective as possible.

Madeline: Great, thanks Reg. And Dan, would you like to introduce yourself?

Dan: Sure. Hi, I'm Dan. I'm Director of Engineering Quality and Support at Deskpro. I look after two teams, the QA team, who sits inside Engineering, and our Customer and Technical Support team. So I get to see a support request from both ends: the customer who's raised it and the engineers who fix it. We also run our own support on Deskpro, so we use the product every day as well as build it.

Madeline: Great, thanks, Dan. All right, so I'm going to share a quick overview of what we're going to cover today. We've got about 45 minutes for this session. So, first, we're going to talk through some of the challenges of getting multiple teams to collaborate on support requests, how to improve those handoffs and prevent bottlenecks.

Reg and Dan are also going to cover some of the processes and technology that they use to improve collaboration on support requests. And while Dan and Reg both use Deskpro as their help desk, that's only one piece of the puzzle. And we hope that this advice is relevant, whatever your tech stack looks like.

Then Dan and Reg are also going to talk a little bit about how they show the impact of collaborative support work across the organization so that you keep getting that organizational buy-in and then share some kind of general best practices for making support a team sport no matter what teams you're working with.

And then we'll leave about 10 minutes at the end for Q&A. There's a little Q&A box at the bottom of the screen. So if you have any questions throughout, drop them in there and we'll get to them at the end. All right. And we'll have a few visuals to share later, but I'll take our slides down for now. And kind of first to just set the stage, I'd love to talk to you both about why it's so important for your organizations to have Support and Engineering working hand in hand. So Reg, could you take that one first?

Reg: For sure, yeah. So for me, it really comes down to the fact that Support and Engineering bring two different perspectives for the same problem. So Support would understand the customer context, the impact an issue is having and how it's affecting the customer from day to day, while the Engineering team brings the technical knowledge needed to investigate and ultimately resolve it. When those teams work hand in hand, you get much better flow of information.

Engineering gets the right context rather than just a technical description of a problem and support gets the information they need to keep the customer informed about constantly chasing for updates. Ultimately, the customer shouldn't really see the boundaries between support and engineering. They just want to know that the issue is understood, being worked on and they're kept informed throughout.

Madeline: All right. Yeah. People don't really care who solves the issue as long as it's getting solved, right?

Reg: 100%. Yeah.

Madeline: All right. And then Dan, same question to you.

Dan: Yeah. Firstly, I agree with everything Reg has said. Every bug a customer reports reaches Engineering through Support. If that handover is poor, the engineer starts by working out what the customer did and the customer has to wait whilst we do that. If it's good, the engineer can start with the reproduction steps and just take it from there. But engineering needs Support just as much. Support is the clearest view Engineering has of how the product behaves in real use. No test environment fully covers everything a customer does with it.

So Support acts as early warning systems, if you like. Experienced agents get a good gut feel for when something isn't right. And when the two teams work together, we do get to a resolution quickly. The feedback loop is shorter and we react to potential incidents far faster than previously we would.

Madeline: Great. Yeah, and I think we all know it can be challenging to get multiple teams rowing in the same direction. But could you both share some of the specific challenges you found in getting multiple departments to work together on Support requests? And let's start with you on this one, Dan.

Dan: Sure. So I think for me, it's the gap between the micro and the macro view. So Support sees the customer in front of them and they understand exactly how important that issue is to that customer. Engineering sometimes has to take more of a macro view. How many customers are affected and where do we invest the team's limited time and energy to help as many customers as possible? Both views are right and they often point to different priorities. So the challenge is getting each team to see the other's view. Support needs to know why an issue is waiting, and Engineering needs to know why the wait is costing that customer.

Madeline: Got it. Yeah, that makes a lot of sense. I know in my role, I work in the marketing team and we work closely with the sales team and sometimes it can feel like we have different priorities, but everybody is working towards the same macro goals in the end.

Great. All right. So I had a question specifically for you, Reg. So I know before you started using Deskpro, your support team was using Asana, which is a project management tool. Personally, I love Asana. I use it every day for my work, but it's not a help desk or a support tool. It's a project management platform. So I was wondering what some of the signs were that Asana was no longer meeting your team's needs?

Reg: Yeah, absolutely. I mean, as you say, Asana is a great tool for what it is. It's a project management tool, but it is built around project management. It did work well for us, but we started to recognize that our support requirements were becoming more mature and we needed something purpose-built for customer support. We needed better visibility of requests throughout their life cycle, clearer ownership, stronger communication, and better ways of managing things like SLAs, categorization, and reporting. We also wanted to reduce some of the manual handoffs between Support and other teams, particularly Engineering.

As our processes evolved, it became clear that trying to adapt a project management tool around those requirements was creating much more friction than we wanted. That was really at the point where we started looking for a dedicated support platform rather than continuing to adapt the processes we already had.

Madeline: Got it. And so I know you're using Deskpro now alongside Shortcut, which is your engineering team's project management tool. So I'll pull up this visual that you shared. Could you tell me a little bit more about how you're using those two tools and how they're connecting your support and engineering workflows?

Reg: Of course, yeah. I mean, the key thing for us was that we didn't want Support and Engineering to have to work in the same system.

Deskpro is where our support team manages the customer relationship, where Shortcut is where Engineering manages their development work. When something comes into Support that requires Engineering involvement, we can connect that support request to the relevant engineering work in Shortcut.

This gives us a link between the customer-facing requests and the technical work happening behind the scenes. So for Support, that means we have much better visibility of what's happening without constantly having to chase Engineering for updates. And for Engineering, they can continue working in Shortcut without needing to manage customer support tickets as well. I think that separation is really important.

We're not trying to make Engineering become Support or Support become Engineering. We're giving each team the information they need while allowing them to work in the tools and processes that make sense for them. What you can see on the screen is the collaboration that we've set up between Support and Engineering in action. Engineering can provide updates as the fix progresses and Shortcut, while our automations make sure that the right information goes to the right audiences.

Internal details stay internal, and customers are automatically kept informed at key stages of the process.

Madeline: Great. Yeah, I think there's something to be said for not making people work out of new tools that aren't relative or relevant to their day-to-day role. You know, we all already have a number of tools that we're using, and trying to get somebody to use something new can be an uphill battle. So that makes sense that Engineering doesn't need to be directly in the help desk. All right. And then, Dan, I wanted to talk to you a little bit about bringing the Engineering QA and Support teams together at Deskpro. So this has been a relatively recent move within the past six months or so. So, when you first stepped into this role, leading both the Engineering QA and Support teams, what did you see that was already working well? And what areas for improvement did you see?

Dan: Yeah, so. Before I took this role, we already had this thing called a support rota. So that was a group of engineers who would solely work on the issues behind the support tickets. And that did work well. The change was actually bringing customer and technical support into the stand-ups and the various meetings that the support rota did so that they could work much more closely with QA and Engineering. Support can advocate for customers directly with the people who are doing the work, and the agents get the technical feedback straight from the engineers and can pass that back to customers much more quickly.

Madeline: Great. And can you talk me through some of the improvements you've seen since bringing these two teams together?

Dan: Yep. So we definitely are able to flag critical issues faster, with support being in the stand-ups with the engineers. They can act on them and they can raise any alarm bells straight away.

We can also allocate engineering time to the more technical issues, so including the ones that aren't necessarily a bug in the code but still need an engineer involved to help resolve. And that help actually goes in both directions. So, when support is light on tickets, the agents come on board and help QA with testing. So, we're much more of a flexible team. The rota is getting through a lot of work too. In the last four weeks, we fixed about 100 bugs, and that work is linked to 139 support tickets from 55 customers. So there's definitely more collaboration and focus on solving the issues behind the support tickets.

Madeline: Awesome. That's great to hear. Sort of a similar question to you, Reg. What improvements have you seen since you started using Deskpro and Shortcut together? And I know you had some graphics to share here. I'll pull those back up.

Reg: Great stuff. Yeah, thank you. Yeah. So the biggest improvement has probably been removing a lot of the manual handoffs between support and engineering. Previously, we could have our customer information in one system and development information in another. And someone had to keep checking that the two matched.

Now, Support manages the customer request in Deskpro. Engineering manages the work in Shortcut, but the two are now connected. So as Engineering progresses the work, that information can flow back into Deskpro automatically, including things like development status, the version a fix is targeted for. And that means that Support spends less time chasing Engineering for updates. Engineering gets fewer interruptions asking for status updates. And most importantly, we have much better information available to keep a customer informed.

Madeline: Great. Yeah, I'm sure the Support team appreciates not having to chase Engineering. I'm sure Engineering appreciates not having to be disrupted as much.

Reg: Exactly that. Yes.

Madeline: All right. And I know you've also been using a help center to provide self-service to your customers. So can you tell me a little bit more about how you work with Engineering to create content for that help desk or help center?

Reg: Of course, yeah, so Engineering brings the technical product knowledge and Support brings the customer's perspective. So we work together to make sure the information is technically accurate, but also written in a way that makes sense to the people actually using, for people that are actually using our product. Support requests are also a really valuable source of feedback. If we're repeatedly answering the same question, we can look at whether that should become an improvement in the product or an article in our help center. The aim isn't to stop customers contacting Support, it's to give them more choice and allow them to find answers themselves when that's the quickest option. For us, the best help center content combines Engineering's product knowledge with Support's understanding of the customer.

Madeline: Great. And kind of a follow-up question because I know this is probably a challenge in a lot of organizations, but how do you get Engineering to make time to help collaborate on this help center content?

Reg: Well, it's quite easy because we tell them the benefits of doing so and that stops any kind of requests to them for updates. So we kind of sell them the benefits, sell them the positives, but also explain the customer experience improvements that are underway. So it's quite an easy process. Yeah.

Madeline: Awesome. I think that idea of sharing the benefits leads nicely into the next question that I had for both of you, which is about showing the value and the impact of collaborative support work across the organization. So I wanted to talk to you both a bit about reporting and what you're sharing with the broader organization. So maybe can we start with you, Dan? Can you share a little bit about how you're reporting on support performance across the broader Deskpro team?

Dan: Sure. So every month I present two slides to our company All Hands, which you can see on screen, and it's under one heading: Support and QA. The line on the first slide sums it up really. It's two sides of one job, answer customers fast and fix what's behind the tickets. The first slide is frontline support.

And we take it from Deskpro's reporting using our API and DPQL. It shows how much of the ticket intake we've cleared, how many tickets the team have resolved, the median first reply time, customer satisfaction, and whether we met our first response SLAs. A good example is in the last four weeks we've cleared nearly 1,200 tickets and we typically have a first reply time of 24 minutes. And I'm really impressed with the team. We've maintained a 99% positive satisfaction score on those. So yeah, really proud of the team for that.

The second slide is the engineering slide. So we use Linear to track our engineering work, much like Reg with Shortcut. We keep Engineering and Support in separate tools. The slide shows how many customer-driven issues we fix and how many support tickets were linked to those fixes. That one gets the most attention because anyone in the company can see which customers our fixes helped.

Both slides are generated from the data from Support and Linear. So it's not being rebuilt by hand each month.

Madeline: Great. Yeah. And obviously, I'm sitting in those All Hands meetings. And I know one thing that I really appreciate is being able to see some of those customer names. Obviously, on the slide here, this is just mock data. But I think that kind of really helps ground the impact for me and a lot of other people in the organization.

All right. And I'll pass it over to you, Reg, to talk a little bit about how you approach reporting at Aquila Learning.

Reg: Yeah, that's great. Thank you. So reporting is really important to us because it helps us understand, because it helps us move away from simply looking at how many tickets we're closing and towards understanding how effective the overall support experience is.

Within Deskpro, we're looking at things like ticket volumes, response and resolution performance, SLA performance, types of issues being raised, and where those requests are coming from. But for me, the real value is in the trends. Are we seeing the same issues repeatedly? Are certain areas of the product generating more support demand? Are there opportunities for better help center content, training, or changes within the product itself?

That means that reporting isn't just useful for Support, it gives us information we can take back to Engineering and the Product team and the wider business and use it to identify where we can make improvements that ultimately reduce friction for the customer.

Madeline: Great. Yeah, I think that's a great point that the Support team should be sort of a voice of the customer and a source of feedback for the rest of the organization. All right. I'll take the slides down for now. So one kind of broad question that I wanted to ask you, because I know some people on this call, they may be working across different teams, not necessarily just Engineering.

So, based on your experience, what advice would you offer to a support leader who needs to work across any other team in their organization to get requests resolved? And I'll start with you on this one, Dan.

Dan: Yeah, so for me, I think it's all about the handovers. Picking one handover and fixing that first. So for us, it was the bug report. We sat down with the other team, we agreed what good looks like, and we wrote it out as a template and then we owned it on both sides. After that, making progress visible. So nobody has to ask for it.

If a ticket is linked to the work the other team is doing, the status comes back to Support automatically. So for us, that's a Deskpro ticket linked to a Linear issue. I'd also have each team spend time in the other's work, bringing support agents into bug triage and getting engineers reading real tickets. Once people have seen what the other team has to deal with, the requests they send each other get better naturally.

Madeline: Great. And then Reg, what best practices would you share?

Reg: Yeah, of course. So my biggest piece of advice would be to start with the processes and the relationship between the teams rather than starting with the technology. Take the time to understand how the other team and other departments work, what information they actually need from Support, and equally what support you expect from them.

One thing we've always recognized is that different teams naturally have different priorities and different ways of working, and that's absolutely fine. The objective shouldn't be to force anyone into the same tools or processes. It should be to make the handoffs between those teams as simple and transparent as possible with clear ownership and enough visibility that people aren't constantly chasing each other for updates. Then you can look at how technology supports that process.

That's been important for us with Deskpro and Shortcut. Each team can work in the environment that makes sense for them while still having a connection between the two. Ultimately, successful collaboration isn't about having everyone doing the same thing. It's about making it easy for different teams to work towards the same outcome.

Madeline: Great. Yeah, I feel like that advice maps really well to my experience with Sales and Marketing as well. So thank you. All right. So we've been making good time on this. So we have we're happy to spend plenty of time on questions at the end if anybody wants to drop any questions in the Q&A.

I've also added QR codes here if you're interested in connecting with Reg and Dan on LinkedIn. I know you're both active on LinkedIn. Dan, I believe you've posted some articles on there as well. So definitely worth a follow. So let me jump over to our next slide here. And if anybody has any questions, please feel free to drop them in the Q&A now and we can cover them. So I'll give everyone a minute here.

All right. So one question, and maybe this one can be for you, Dan. How do you prioritize customer issues against roadmap work?

Dan: Ooh, okay. Yeah. Actually, so at Deskpro, we keep the two separate. Our sprints are two weeks long, and each engineer rotates onto the support rota once every three sprints. So, at any time, a third of the engineering team is on the rota, and the rest stay on roadmap work. The rota has its own roadmap for bugs and issues, and that's completely separate from the feature roadmap. That's really helpful because it lets us pivot quickly to whatever the issue of the day is. Um, so it could be an infrastructure issue, a newly found bug that we need to fix and patch quickly. You know, when nothing urgent has come up, the rota works through the backlog of issues, which we prioritize by severity and priority. And it also means that feature work isn't interrupted every time something urgent comes in.

Madeline: Great, yeah, that makes a lot of sense. All right. And Reg, I think I'm going to give this next one to you. How do your SLAs work when another team is responsible for the fix?

Reg: So I mean the key thing for us is that passing something over to Engineering doesn't mean passing ownership of the customer with it. So Engineering might own the technical investigation and fix, but Support continues to own that customer relationship and communication. So a fix might take longer depending on its complexity, but we can still make sure that the customer knows what's happening and isn't left wondering where their issue has gone. So having Deskpro connected with Shortcut gives Support the visibility without constantly needing to chase. So we might not always control how quickly a fix can be delivered, but we can control how well we communicate with the customer throughout that process.

Madeline: Okay, got it. And we've got another question that's kind of related, so I'm going to give this one to you as well, Reg. What's your approach to communicating with customers when there's a blocker in another department? Okay, so I think the biggest thing is not going silent just because another team has the next action.

Reg: So as I mentioned before, Support still owns that relationship, the customer. So if there is a blocker, we're open about where things are and what happened, what's happening next. But we also try not to hide behind another department. So we don't say we're waiting for Engineering because from a customer's perspective, they're dealing with us as an organization.

So, even when we don't have a resolution, we can still provide a meaningful update, and that visibility between Deskpro and Shortcut makes that a whole lot easier. Right. Yeah, I think it comes back to that idea that customers don't really care about where the resolution comes from as long as they're getting the resolution and the organization is communicating with them if there are any delays. Indeed. Yeah.

Madeline: Great. And we have one more. So I'm going to pass this one to you, Dan. Have you experienced any pushback from other teams when rolling out new processes for handling support requests? And if so, how have you dealt with that?

Dan: Yes. We have had some. And I think to preface this, I think it's healthy. I think pushback is a healthy thing to have. Any new process is extra work at first, and people want to know why before they actually change how they work.

To deal with it, I think you need to involve the other team or the people involved in the change as early as possible. Establish that it's not the final product. We never sort of one-shot something, it's always work in progress. You do MVP and then you build on it and iterate until it becomes a sort of established process.

Making sure that that's clear, involving people early on, and making sure people feel engaged in the change and that their concerns are heard is how we deal with things at Deskpro.

Madeline: Great. We've had one more question come in. I think this is a follow-up to the one that we just covered, Reg. This is to follow up on that question: how do you elicit feedback from customers after numerous attempts to contact them have gone silent? This is an interesting one. I'd love if you could both weigh in on that. And Reg, Dan, do you have a preference on who starts? If anybody already has thoughts on that.

Reg: Yeah, I can take that. Yeah, so how we follow up with customers if they go silent. So we have a number of automations in place inside Deskpro which allows us to communicate with the customer automatically and that depends on the status of each individual request as well.

So if we are waiting for a response from a customer and that response has taken over a period of time, we'll send an automatic update or response back to that customer just to follow up and chase them to see if there's any further assistance we can provide to that customer. So we utilize the tools already available inside Deskpro.

Madeline: Great. And Dan, I know our processes may look a little similar. Is there anything else you would add to that?

Dan: Yeah, I was smiling because it sounds very, very similar to what we do at Deskpro. I think what one of the ways we do it, whilst we do have automations, we push the ticket from a pending state back into an awaiting agent state so that the agent's able to personalize the message and follow up. But yeah, it is very similar. We try to contact a number of times, but we always, if we're unable to reach the customer, we always close the ticket with a statement that they can, if they want or need our help, they can respond and it will reopen the ticket and we'll jump straight back into it.

Madeline: So that's helpful. Thank you both. All right, we have covered all of the questions that came in. So I think we've been efficient today. So we can give everybody 15 minutes back. But Dan and Reg, thank you again so much for your time. And thank you for everybody who joined us today. We will be sending out a recording of this after the fact.