WEBVTT
00:00:13.359 --> 00:00:18.239
Hello and welcome to episode one hundred and sixty-seven of the Customer Support Leaders Podcast.
00:00:18.239 --> 00:00:19.839
I'm Charlotte Ward.
00:00:19.839 --> 00:00:28.960
The theme for this week is Slack support, so stay tuned for five leaders talking about that very topic.
00:00:28.960 --> 00:00:36.159
I'd like to welcome to the podcast today, Fletcher Richmond.
00:00:36.159 --> 00:00:38.880
Fletcher, it's lovely to have you join me this week.
00:00:38.880 --> 00:00:42.000
First things first, would you like to introduce yourself?
00:00:42.960 --> 00:00:44.719
Yeah, thanks so much for having me.
00:00:44.719 --> 00:00:53.759
Um so my current role is um leading product for a product line called HALP, which is part of the Atlassian family.
00:00:53.759 --> 00:01:00.399
We were acquired about six months ago by Atlassian, and um I was previously the CEO of that company.
00:01:00.399 --> 00:01:07.680
So um now just in charge of all things product related to uh business inside of Atlassian.
00:01:07.680 --> 00:01:10.879
I recently also uh moved to Austin, Texas.
00:01:10.879 --> 00:01:13.599
So calling in from there today.
00:01:14.319 --> 00:01:14.799
Awesome.
00:01:14.799 --> 00:01:15.680
That's cool.
00:01:15.680 --> 00:01:22.640
Um so I I feel like you're one of the very people I ought to be speaking to this week about Slack support.
00:01:22.640 --> 00:01:30.319
Um and I have to admit, this is one support channel that I have never really done in anger.
00:01:30.319 --> 00:01:38.159
Um like like I think a lot of people, a little bit of accidental Slack support, but not much else.
00:01:38.159 --> 00:01:42.560
So uh so I'm kind of I'm I'm gonna let you lead this.
00:01:42.560 --> 00:01:44.640
What maybe maybe we start at the beginning.
00:01:44.640 --> 00:01:47.280
Where where do we begin with Slack support?
00:01:48.640 --> 00:01:51.120
Yeah, so I I think you're not alone.
00:01:51.120 --> 00:02:05.760
Um I know a lot of folks in support who they hear the those two words together, Slack and support, and I think immediately have a kind of a scary allergic reaction, which I think is actually totally reasonable.
00:02:05.760 --> 00:02:12.800
And um I think there are actually a lot of ways you can do slack support really wrong and really badly.
00:02:12.800 --> 00:02:17.680
Um, and it can be a nightmare for both sides uh of the equation.
00:02:17.680 --> 00:02:37.120
Um, but I don't think that's a good reason to just dismiss it outright and and totally say this is not something we're ever, ever going to do, because there are ways to do it well, and there are ways that if you're really thoughtful about it, um, it can be absolutely delightful, I think, actually, for for both sides, uh both the support person and the the customer.
00:02:37.120 --> 00:02:41.039
Um and that's kind of the business that we're in in the end is delighting customers.
00:02:41.199 --> 00:02:43.199
So that's quite a promise.
00:02:43.199 --> 00:02:44.479
Absolutely delightful.
00:02:44.479 --> 00:02:50.319
I I hope that's where we'll get by the end of this episode is is absolute delight at Slack support.
00:02:50.319 --> 00:02:53.680
So so yeah, so so sorry, I completely interrupted you then.
00:02:53.680 --> 00:02:56.400
You I think you were about to tell me where we should all begin.
00:02:57.520 --> 00:03:06.400
Yeah, so the the two specific things that I think Slack support is really good for, it depends on the the organization size that you're working at.
00:03:06.400 --> 00:03:21.360
So if you're working at a small startup, really early stage and you're you have early customers, or let's say you're working on a brand new product inside of a bigger company, but generally talking about products that are newer and don't have very many customers.
00:03:21.360 --> 00:03:29.759
Um so maybe you're the first support person, or maybe you're even just doing support as a part-time job, then uh shared shared channels in Slack.
00:03:29.759 --> 00:03:35.599
So and there's this is also a thing I'd be very specific about is the way you set it up is is important.
00:03:35.599 --> 00:03:40.159
Um, what I generally recommend is using Slack now calls this Slack Connect.
00:03:40.159 --> 00:03:43.680
It's still a relatively new Slack piece of functionality.
00:03:43.680 --> 00:03:50.879
But what you're doing is actually creating a channel that exists in two completely separate Slack workspaces.
00:03:50.879 --> 00:03:58.000
So you're taking your channel from that from your instance and you're saying, I want this channel to be available in someone else's Slack instance.
00:03:58.000 --> 00:03:59.199
So there's no new account.
00:03:59.199 --> 00:04:07.599
There's no, if if I'm logged into my Slack account and that's where I talk to all my coworkers all the time, I can now join this specific channel and talk to somebody in another organization.
00:04:07.599 --> 00:04:17.040
So what works great is if you set up these shared channels, one individual channel for each one of your early access or early adopter customers.
00:04:17.040 --> 00:04:22.560
So call it the first 20 or so roughly customers that you do this for.
00:04:22.560 --> 00:04:28.480
And what you'll find is that it really just decreases the distance between you and the customer.
00:04:28.480 --> 00:04:37.680
And so you get really quick feedback loops, they'll tell you what they like or don't like about the product, they'll ask for features, they'll um report really small bugs, really big bugs.
00:04:37.680 --> 00:04:44.800
They're really just going to build a pretty tight relationship with you, and you can throw your engineers in there and they can talk and quickly debug and fix things as well.
00:04:44.800 --> 00:04:50.000
So that's one really great um, I think, use case for Slack support.
00:04:50.000 --> 00:04:56.800
And then the other one is if you're larger and you have a ton of customers, is to specifically offer it as premium support.
00:04:56.800 --> 00:05:07.199
And I see this really as the evolution of um we instead of having a direct phone line, uh, which is the old way of doing premium support, we're now giving you a direct Slack channel.
00:05:07.199 --> 00:05:10.480
Um, and so I've seen companies charge more money for this.
00:05:10.480 --> 00:05:17.759
Um, they're actually making a profit on it because they're charging a lot of additional money for that, that is a support service specifically.
00:05:17.759 --> 00:05:28.879
Um, and they're um retaining their customers better, they're building good relationships, and the customers are willing and happy to pay for it, especially if you have a product that is a developer-focused product.
00:05:28.879 --> 00:05:33.279
So if you're selling to developers and engineers, they want to stay inside of Slack.
00:05:33.279 --> 00:05:42.879
And so um, we tend to see larger enterprise customers that um larger enterprise companies that are B2B do this uh shared Slack channel thing.
00:05:42.879 --> 00:05:46.000
That's also what I'll say is if you're a B2C company, this doesn't apply.
00:05:46.000 --> 00:05:54.560
If you're like it's a very specific set, B2B companies selling into other enterprises who are also technology focused and also use Slack.
00:05:54.560 --> 00:05:58.560
Um, so there's a pretty specific um set of cases where it makes sense.
00:05:58.560 --> 00:06:02.720
And I think a lot of people use it outside of those contexts, and then you have bad experiences.
00:06:03.120 --> 00:06:06.240
I I I I love like a couple of things that you said there.
00:06:06.240 --> 00:06:12.000
And I think first of all, that that distinction you make, this isn't a transient channel, is it?
00:06:12.000 --> 00:06:23.360
That that kind of you know the the retail type of support does not sit in Slack, you know, no nobody's gonna be returning a pair of shorts in Slack, let's face it.
00:06:23.360 --> 00:06:36.879
Um but I think what what I really liked particularly about those two use cases was something you said in the first one, which is in that early stage, how it decreases the distance between you and the customer.
00:06:36.879 --> 00:06:39.199
I thought that was a really interesting way of putting it.
00:06:39.199 --> 00:06:43.199
And that actually carries through to the second use case you gave as well, doesn't it?
00:06:43.199 --> 00:06:57.680
When you've got when it's a much more premium channel and you've got these bigger customers, actually, inside these enterprise level organizations, there are teams that you want to actually develop really close bonds with, and it's great for that, right?
00:06:58.720 --> 00:06:59.519
Right, exactly.
00:06:59.519 --> 00:07:03.360
And that's you need to have buy-in from the rest of the organization on that concept.
00:07:03.360 --> 00:07:12.959
Because if the whole org is just thinking, how do we decrease costs and make our support as low touch as possible and have as few tickets as possible, then this isn't for you.
00:07:12.959 --> 00:07:20.560
But if your organization is customer-centric and wants to build these great relationships with some of your best customers, this is a really good way to do it.
00:07:20.560 --> 00:07:36.560
Also, one thing I thought of that is also, I think, important in this context is depending on the complexity of tickets, this can be a much nicer way to debug more technical problems because you can share files, you can share code snippets, you can quickly jump on a call.
00:07:36.560 --> 00:07:41.759
It's it just decreases that back and forth time between responses on the customer side as well.
00:07:41.759 --> 00:07:48.720
So you're getting these fast responses from customers every time you ask a question instead of the, hey, yeah, can you send me the logs for this thing?
00:07:48.720 --> 00:07:53.519
Six days later, you get the logs back because that engineer is not checking their email ever.
00:07:53.519 --> 00:07:59.920
So um it it can actually improve your resolution times on more complex tickets as well.
00:08:00.480 --> 00:08:22.959
I'm guessing it's quite transparent as well, because I think that particularly if you're if your team is very distributed and you have people based all around the world in a bunch of time zones, it's not obvious if your customer is coming in through email or through a support portal, who's going to be answering the ticket, if somebody's available to answer the ticket at that point.
00:08:22.959 --> 00:08:35.279
Um and I think that the sense I get from Slack probably is that you you get an immediate sense of who's there, if someone's there, and you get the conversation going really quickly.
00:08:36.000 --> 00:08:37.840
Yeah, I think that's that's definitely true.
00:08:37.840 --> 00:08:39.679
It just feels more human too.
00:08:39.679 --> 00:08:43.039
It's it's you realize you're just two humans talking to each other.
00:08:43.039 --> 00:08:48.879
You have there's an actual face, and there's you can use emojis and you can you can express yourself, I think, a lot deeper.
00:08:48.879 --> 00:08:58.480
And that's a lot of where the the connection and the um deeper loyalty and relationship, I think, comes from is the fact that it's just so much more expressive.
00:08:58.480 --> 00:09:01.679
Uh everything from what you mentioned, just hey, is this person online or not?
00:09:01.679 --> 00:09:14.080
Well, I'm not gonna bug them if they're not online, to um using emojis, using gifts, using all the fun things that we get to use now in in the workplace, and and doing that um in those conversations feels pretty natural.
00:09:15.919 --> 00:09:28.559
Operationally, then one thing that I have always felt nervous about is how we track this, how we measure it, how we proceduralize it, if that's a word.
00:09:28.559 --> 00:09:38.639
You know, from the support support perspective, from my own organization's perspective, how can I support my support folks in supporting customers through Slack?
00:09:39.440 --> 00:09:48.639
Yeah, so I I would uh get a butt kicking from my marketing people if I didn't plug our our product a little bit at least here.
00:09:48.639 --> 00:09:57.840
So that is definitely a very good reason why a lot of folks choose to use the help product inside of their shared channels in Slack.
00:09:57.840 --> 00:10:01.279
Um basically you take any message in Slack, you turn it into a ticket.
00:10:01.279 --> 00:10:05.120
We can then sync that ticket with either Zendesk or GeoService Desk.
00:10:05.120 --> 00:10:11.440
Um so if a lot of our shared channel customers, I'd say, are primarily in Zendesk for the rest of their tickets.
00:10:11.440 --> 00:10:15.039
We don't want to force them to go to another place and have to manage another queue.
00:10:15.039 --> 00:10:20.399
Um and so you can just kind of easily sync all of those conversations with your existing ticketing system.
00:10:20.399 --> 00:10:23.120
So great, great reason to check out help.
00:10:23.120 --> 00:10:26.799
Um, but I think you're right that um that is really important.
00:10:26.799 --> 00:10:36.240
If we think back to our two use cases, if we're talking about the early access sort of startup, uh one, I think it's maybe a little bit less of a problem.
00:10:36.240 --> 00:10:41.200
It's it's kind of okay if maybe you're just having a lot of lightweight conversations and the ball gets dropped on a couple of them.
00:10:41.200 --> 00:10:50.960
But yeah, Slack is just not great for tracking status and following up on things, and there's threads everywhere and conversations happening and who's assigned to what.
00:10:50.960 --> 00:11:04.720
And so really, even just adding that layer of status assignment and some tracking and being able to go back and both I think for accountability purposes and reporting purposes, that that is really important and something something folks could should be considering.
00:11:04.720 --> 00:11:08.879
What I'll what I'll say as well is just generically, Slack does have an amazing app store.
00:11:08.879 --> 00:11:11.679
So there's thousands of apps in the in the Slack App Store.
00:11:11.679 --> 00:11:18.320
So um, whether it's us or or some other product, um, feel free to check out uh all the stuff in the Slack App Store.
00:11:18.320 --> 00:11:21.200
And there's lots of great products being built around this concept.
00:11:21.279 --> 00:11:26.720
So uh yeah, you're right about the trackability and and everything in Slack.
00:11:26.720 --> 00:11:35.519
It's a great communication tool, but it's not necessarily a an incident management tool or or a conversation management tool in that sense, is it?
00:11:35.519 --> 00:11:51.279
Um final question I have for you, which is just kind of an extension of like how we help our support folks support people through Slack, is aside from the tooling, are there any tactics?
00:11:51.279 --> 00:11:53.679
Any is there any advice?
00:11:53.679 --> 00:12:04.639
Is there a way of doing or being on Slack as a support person, do you think that that just facilitates this whole relationship?
00:12:05.120 --> 00:12:07.279
Yeah, so a couple of things I'll say.
00:12:07.279 --> 00:12:15.200
I think one thing we do is we consider this to be, I think you mentioned this, but I would just very much consider this to be its own channel.
00:12:15.200 --> 00:12:30.799
And so the same way that you're gonna have different response time expectations and SLAs for your chat versus your email channel, I wouldn't just automatically bucket this into chat because it's something a little bit different than chat, than the website chat type concept.
00:12:30.799 --> 00:12:33.279
This is an intercom, it's a different thing.
00:12:33.279 --> 00:12:41.279
And so we have different SLAs and different response time expectations for chat versus Slack versus email.
00:12:41.279 --> 00:12:51.279
Um, so I would make sure that there's alignment there around um creating accountability and metrics for what your expectations are of your support team.
00:12:51.279 --> 00:12:58.240
One thing we have noticed is sometimes it's so easy to reply in Slack that we are almost a little too trick too quick to the trigger.
00:12:58.240 --> 00:13:08.559
Um, and there is something to be said about you don't want to create the expectation for your customer that you're gonna always respond within five seconds or 10 seconds or something like that.
00:13:08.559 --> 00:13:13.440
And so they do need a little bit of time to just um report what the actual problem is.
00:13:13.440 --> 00:13:16.960
They might solve it themselves, they might have follow-up questions or things.
00:13:16.960 --> 00:13:19.919
I even find myself sometimes just being like, okay, the thing lit up.
00:13:19.919 --> 00:13:21.519
I got the pop-up Slack notification.
00:13:21.519 --> 00:13:24.000
Let's just hold on to it for a little while.
00:13:24.000 --> 00:13:26.000
Um just take a breath.
00:13:26.000 --> 00:13:27.679
Exactly.
00:13:27.679 --> 00:13:32.159
So just making sure it's clear what the expectations are at the same time in Slack.
00:13:32.159 --> 00:13:36.639
I think there is a moment, uh, if it's over 24 hours, it's kind of feels like you're ignoring somebody.
00:13:36.639 --> 00:13:43.200
And so there's gonna be a fine balance there of don't respond too quickly, but also don't keep people waiting.
00:13:43.200 --> 00:13:47.840
Um, and just make sure that you're measuring that stuff and that you're um clear with your customers.
00:13:47.840 --> 00:14:00.799
The other thing I would say is try to empower your customers to um sort of understand the protocol and context for how to how to report a ticket inside of Slack because different people use Slack in different ways.
00:14:00.799 --> 00:14:02.080
Are they supposed to use a thread?
00:14:02.080 --> 00:14:02.720
Are they not?
00:14:02.720 --> 00:14:05.519
Are they supposed to upload all the attachments there?
00:14:05.519 --> 00:14:07.679
Do they need to include more information?
00:14:07.679 --> 00:14:12.720
Like, what are you expecting from your customers when they're reporting something in these in these Slack channels?
00:14:12.720 --> 00:14:14.320
When do they get the Slack channel?
00:14:14.320 --> 00:14:16.320
Who should be in it on their side?
00:14:16.320 --> 00:14:24.240
Um, a lot of these things you can just be pretty clear with your with your customer about what your expectations are, and they don't know there, this is still a relatively new thing.
00:14:24.240 --> 00:14:32.720
And so they'll be totally willing to sort of follow your lead on that um and say, hey, we we'd like you to have three representatives from your organization in this.
00:14:32.720 --> 00:14:35.840
Here's the the different people that we expect to be in here.
00:14:35.840 --> 00:14:43.360
Um when you report an issue, we we try to respond within 30 minutes and we'll thread the issue and it'll be in this thread.
00:14:43.360 --> 00:14:45.759
And please upload any attachments inside of that thread.
00:14:45.759 --> 00:14:47.120
Just simple stuff like that, right?
00:14:47.120 --> 00:14:55.679
You can use like the um you could link to a Google Doc in the description of the channel as an example of a way to do that.
00:14:55.679 --> 00:15:02.559
Um, so yeah, just be really clear, measure what you're doing, and make sure those expectations line up with your customer.
00:15:05.600 --> 00:15:06.480
That's it for today.
00:15:06.480 --> 00:15:12.879
Go to customersupportleaders.com forward slash one six seven for the show notes, and I'll see you next time.
00:00:13.359 --> 00:00:18.239
Hello and welcome to episode one hundred and sixty-seven of the Customer Support Leaders Podcast.
00:00:18.239 --> 00:00:19.839
I'm Charlotte Ward.
00:00:19.839 --> 00:00:28.960
The theme for this week is Slack support, so stay tuned for five leaders talking about that very topic.
00:00:28.960 --> 00:00:36.159
I'd like to welcome to the podcast today, Fletcher Richmond.
00:00:36.159 --> 00:00:38.880
Fletcher, it's lovely to have you join me this week.
00:00:38.880 --> 00:00:42.000
First things first, would you like to introduce yourself?
00:00:42.960 --> 00:00:44.719
Yeah, thanks so much for having me.
00:00:44.719 --> 00:00:53.759
Um so my current role is um leading product for a product line called HALP, which is part of the Atlassian family.
00:00:53.759 --> 00:01:00.399
We were acquired about six months ago by Atlassian, and um I was previously the CEO of that company.
00:01:00.399 --> 00:01:07.680
So um now just in charge of all things product related to uh business inside of Atlassian.
00:01:07.680 --> 00:01:10.879
I recently also uh moved to Austin, Texas.
00:01:10.879 --> 00:01:13.599
So calling in from there today.
00:01:14.319 --> 00:01:14.799
Awesome.
00:01:14.799 --> 00:01:15.680
That's cool.
00:01:15.680 --> 00:01:22.640
Um so I I feel like you're one of the very people I ought to be speaking to this week about Slack support.
00:01:22.640 --> 00:01:30.319
Um and I have to admit, this is one support channel that I have never really done in anger.
00:01:30.319 --> 00:01:38.159
Um like like I think a lot of people, a little bit of accidental Slack support, but not much else.
00:01:38.159 --> 00:01:42.560
So uh so I'm kind of I'm I'm gonna let you lead this.
00:01:42.560 --> 00:01:44.640
What maybe maybe we start at the beginning.
00:01:44.640 --> 00:01:47.280
Where where do we begin with Slack support?
00:01:48.640 --> 00:01:51.120
Yeah, so I I think you're not alone.
00:01:51.120 --> 00:02:05.760
Um I know a lot of folks in support who they hear the those two words together, Slack and support, and I think immediately have a kind of a scary allergic reaction, which I think is actually totally reasonable.
00:02:05.760 --> 00:02:12.800
And um I think there are actually a lot of ways you can do slack support really wrong and really badly.
00:02:12.800 --> 00:02:17.680
Um, and it can be a nightmare for both sides uh of the equation.
00:02:17.680 --> 00:02:37.120
Um, but I don't think that's a good reason to just dismiss it outright and and totally say this is not something we're ever, ever going to do, because there are ways to do it well, and there are ways that if you're really thoughtful about it, um, it can be absolutely delightful, I think, actually, for for both sides, uh both the support person and the the customer.
00:02:37.120 --> 00:02:41.039
Um and that's kind of the business that we're in in the end is delighting customers.
00:02:41.199 --> 00:02:43.199
So that's quite a promise.
00:02:43.199 --> 00:02:44.479
Absolutely delightful.
00:02:44.479 --> 00:02:50.319
I I hope that's where we'll get by the end of this episode is is absolute delight at Slack support.
00:02:50.319 --> 00:02:53.680
So so yeah, so so sorry, I completely interrupted you then.
00:02:53.680 --> 00:02:56.400
You I think you were about to tell me where we should all begin.
00:02:57.520 --> 00:03:06.400
Yeah, so the the two specific things that I think Slack support is really good for, it depends on the the organization size that you're working at.
00:03:06.400 --> 00:03:21.360
So if you're working at a small startup, really early stage and you're you have early customers, or let's say you're working on a brand new product inside of a bigger company, but generally talking about products that are newer and don't have very many customers.
00:03:21.360 --> 00:03:29.759
Um so maybe you're the first support person, or maybe you're even just doing support as a part-time job, then uh shared shared channels in Slack.
00:03:29.759 --> 00:03:35.599
So and there's this is also a thing I'd be very specific about is the way you set it up is is important.
00:03:35.599 --> 00:03:40.159
Um, what I generally recommend is using Slack now calls this Slack Connect.
00:03:40.159 --> 00:03:43.680
It's still a relatively new Slack piece of functionality.
00:03:43.680 --> 00:03:50.879
But what you're doing is actually creating a channel that exists in two completely separate Slack workspaces.
00:03:50.879 --> 00:03:58.000
So you're taking your channel from that from your instance and you're saying, I want this channel to be available in someone else's Slack instance.
00:03:58.000 --> 00:03:59.199
So there's no new account.
00:03:59.199 --> 00:04:07.599
There's no, if if I'm logged into my Slack account and that's where I talk to all my coworkers all the time, I can now join this specific channel and talk to somebody in another organization.
00:04:07.599 --> 00:04:17.040
So what works great is if you set up these shared channels, one individual channel for each one of your early access or early adopter customers.
00:04:17.040 --> 00:04:22.560
So call it the first 20 or so roughly customers that you do this for.
00:04:22.560 --> 00:04:28.480
And what you'll find is that it really just decreases the distance between you and the customer.
00:04:28.480 --> 00:04:37.680
And so you get really quick feedback loops, they'll tell you what they like or don't like about the product, they'll ask for features, they'll um report really small bugs, really big bugs.
00:04:37.680 --> 00:04:44.800
They're really just going to build a pretty tight relationship with you, and you can throw your engineers in there and they can talk and quickly debug and fix things as well.
00:04:44.800 --> 00:04:50.000
So that's one really great um, I think, use case for Slack support.
00:04:50.000 --> 00:04:56.800
And then the other one is if you're larger and you have a ton of customers, is to specifically offer it as premium support.
00:04:56.800 --> 00:05:07.199
And I see this really as the evolution of um we instead of having a direct phone line, uh, which is the old way of doing premium support, we're now giving you a direct Slack channel.
00:05:07.199 --> 00:05:10.480
Um, and so I've seen companies charge more money for this.
00:05:10.480 --> 00:05:17.759
Um, they're actually making a profit on it because they're charging a lot of additional money for that, that is a support service specifically.
00:05:17.759 --> 00:05:28.879
Um, and they're um retaining their customers better, they're building good relationships, and the customers are willing and happy to pay for it, especially if you have a product that is a developer-focused product.
00:05:28.879 --> 00:05:33.279
So if you're selling to developers and engineers, they want to stay inside of Slack.
00:05:33.279 --> 00:05:42.879
And so um, we tend to see larger enterprise customers that um larger enterprise companies that are B2B do this uh shared Slack channel thing.
00:05:42.879 --> 00:05:46.000
That's also what I'll say is if you're a B2C company, this doesn't apply.
00:05:46.000 --> 00:05:54.560
If you're like it's a very specific set, B2B companies selling into other enterprises who are also technology focused and also use Slack.
00:05:54.560 --> 00:05:58.560
Um, so there's a pretty specific um set of cases where it makes sense.
00:05:58.560 --> 00:06:02.720
And I think a lot of people use it outside of those contexts, and then you have bad experiences.
00:06:03.120 --> 00:06:06.240
I I I I love like a couple of things that you said there.
00:06:06.240 --> 00:06:12.000
And I think first of all, that that distinction you make, this isn't a transient channel, is it?
00:06:12.000 --> 00:06:23.360
That that kind of you know the the retail type of support does not sit in Slack, you know, no nobody's gonna be returning a pair of shorts in Slack, let's face it.
00:06:23.360 --> 00:06:36.879
Um but I think what what I really liked particularly about those two use cases was something you said in the first one, which is in that early stage, how it decreases the distance between you and the customer.
00:06:36.879 --> 00:06:39.199
I thought that was a really interesting way of putting it.
00:06:39.199 --> 00:06:43.199
And that actually carries through to the second use case you gave as well, doesn't it?
00:06:43.199 --> 00:06:57.680
When you've got when it's a much more premium channel and you've got these bigger customers, actually, inside these enterprise level organizations, there are teams that you want to actually develop really close bonds with, and it's great for that, right?
00:06:58.720 --> 00:06:59.519
Right, exactly.
00:06:59.519 --> 00:07:03.360
And that's you need to have buy-in from the rest of the organization on that concept.
00:07:03.360 --> 00:07:12.959
Because if the whole org is just thinking, how do we decrease costs and make our support as low touch as possible and have as few tickets as possible, then this isn't for you.
00:07:12.959 --> 00:07:20.560
But if your organization is customer-centric and wants to build these great relationships with some of your best customers, this is a really good way to do it.
00:07:20.560 --> 00:07:36.560
Also, one thing I thought of that is also, I think, important in this context is depending on the complexity of tickets, this can be a much nicer way to debug more technical problems because you can share files, you can share code snippets, you can quickly jump on a call.
00:07:36.560 --> 00:07:41.759
It's it just decreases that back and forth time between responses on the customer side as well.
00:07:41.759 --> 00:07:48.720
So you're getting these fast responses from customers every time you ask a question instead of the, hey, yeah, can you send me the logs for this thing?
00:07:48.720 --> 00:07:53.519
Six days later, you get the logs back because that engineer is not checking their email ever.
00:07:53.519 --> 00:07:59.920
So um it it can actually improve your resolution times on more complex tickets as well.
00:08:00.480 --> 00:08:22.959
I'm guessing it's quite transparent as well, because I think that particularly if you're if your team is very distributed and you have people based all around the world in a bunch of time zones, it's not obvious if your customer is coming in through email or through a support portal, who's going to be answering the ticket, if somebody's available to answer the ticket at that point.
00:08:22.959 --> 00:08:35.279
Um and I think that the sense I get from Slack probably is that you you get an immediate sense of who's there, if someone's there, and you get the conversation going really quickly.
00:08:36.000 --> 00:08:37.840
Yeah, I think that's that's definitely true.
00:08:37.840 --> 00:08:39.679
It just feels more human too.
00:08:39.679 --> 00:08:43.039
It's it's you realize you're just two humans talking to each other.
00:08:43.039 --> 00:08:48.879
You have there's an actual face, and there's you can use emojis and you can you can express yourself, I think, a lot deeper.
00:08:48.879 --> 00:08:58.480
And that's a lot of where the the connection and the um deeper loyalty and relationship, I think, comes from is the fact that it's just so much more expressive.
00:08:58.480 --> 00:09:01.679
Uh everything from what you mentioned, just hey, is this person online or not?
00:09:01.679 --> 00:09:14.080
Well, I'm not gonna bug them if they're not online, to um using emojis, using gifts, using all the fun things that we get to use now in in the workplace, and and doing that um in those conversations feels pretty natural.
00:09:15.919 --> 00:09:28.559
Operationally, then one thing that I have always felt nervous about is how we track this, how we measure it, how we proceduralize it, if that's a word.
00:09:28.559 --> 00:09:38.639
You know, from the support support perspective, from my own organization's perspective, how can I support my support folks in supporting customers through Slack?
00:09:39.440 --> 00:09:48.639
Yeah, so I I would uh get a butt kicking from my marketing people if I didn't plug our our product a little bit at least here.
00:09:48.639 --> 00:09:57.840
So that is definitely a very good reason why a lot of folks choose to use the help product inside of their shared channels in Slack.
00:09:57.840 --> 00:10:01.279
Um basically you take any message in Slack, you turn it into a ticket.
00:10:01.279 --> 00:10:05.120
We can then sync that ticket with either Zendesk or GeoService Desk.
00:10:05.120 --> 00:10:11.440
Um so if a lot of our shared channel customers, I'd say, are primarily in Zendesk for the rest of their tickets.
00:10:11.440 --> 00:10:15.039
We don't want to force them to go to another place and have to manage another queue.
00:10:15.039 --> 00:10:20.399
Um and so you can just kind of easily sync all of those conversations with your existing ticketing system.
00:10:20.399 --> 00:10:23.120
So great, great reason to check out help.
00:10:23.120 --> 00:10:26.799
Um, but I think you're right that um that is really important.
00:10:26.799 --> 00:10:36.240
If we think back to our two use cases, if we're talking about the early access sort of startup, uh one, I think it's maybe a little bit less of a problem.
00:10:36.240 --> 00:10:41.200
It's it's kind of okay if maybe you're just having a lot of lightweight conversations and the ball gets dropped on a couple of them.
00:10:41.200 --> 00:10:50.960
But yeah, Slack is just not great for tracking status and following up on things, and there's threads everywhere and conversations happening and who's assigned to what.
00:10:50.960 --> 00:11:04.720
And so really, even just adding that layer of status assignment and some tracking and being able to go back and both I think for accountability purposes and reporting purposes, that that is really important and something something folks could should be considering.
00:11:04.720 --> 00:11:08.879
What I'll what I'll say as well is just generically, Slack does have an amazing app store.
00:11:08.879 --> 00:11:11.679
So there's thousands of apps in the in the Slack App Store.
00:11:11.679 --> 00:11:18.320
So um, whether it's us or or some other product, um, feel free to check out uh all the stuff in the Slack App Store.
00:11:18.320 --> 00:11:21.200
And there's lots of great products being built around this concept.
00:11:21.279 --> 00:11:26.720
So uh yeah, you're right about the trackability and and everything in Slack.
00:11:26.720 --> 00:11:35.519
It's a great communication tool, but it's not necessarily a an incident management tool or or a conversation management tool in that sense, is it?
00:11:35.519 --> 00:11:51.279
Um final question I have for you, which is just kind of an extension of like how we help our support folks support people through Slack, is aside from the tooling, are there any tactics?
00:11:51.279 --> 00:11:53.679
Any is there any advice?
00:11:53.679 --> 00:12:04.639
Is there a way of doing or being on Slack as a support person, do you think that that just facilitates this whole relationship?
00:12:05.120 --> 00:12:07.279
Yeah, so a couple of things I'll say.
00:12:07.279 --> 00:12:15.200
I think one thing we do is we consider this to be, I think you mentioned this, but I would just very much consider this to be its own channel.
00:12:15.200 --> 00:12:30.799
And so the same way that you're gonna have different response time expectations and SLAs for your chat versus your email channel, I wouldn't just automatically bucket this into chat because it's something a little bit different than chat, than the website chat type concept.
00:12:30.799 --> 00:12:33.279
This is an intercom, it's a different thing.
00:12:33.279 --> 00:12:41.279
And so we have different SLAs and different response time expectations for chat versus Slack versus email.
00:12:41.279 --> 00:12:51.279
Um, so I would make sure that there's alignment there around um creating accountability and metrics for what your expectations are of your support team.
00:12:51.279 --> 00:12:58.240
One thing we have noticed is sometimes it's so easy to reply in Slack that we are almost a little too trick too quick to the trigger.
00:12:58.240 --> 00:13:08.559
Um, and there is something to be said about you don't want to create the expectation for your customer that you're gonna always respond within five seconds or 10 seconds or something like that.
00:13:08.559 --> 00:13:13.440
And so they do need a little bit of time to just um report what the actual problem is.
00:13:13.440 --> 00:13:16.960
They might solve it themselves, they might have follow-up questions or things.
00:13:16.960 --> 00:13:19.919
I even find myself sometimes just being like, okay, the thing lit up.
00:13:19.919 --> 00:13:21.519
I got the pop-up Slack notification.
00:13:21.519 --> 00:13:24.000
Let's just hold on to it for a little while.
00:13:24.000 --> 00:13:26.000
Um just take a breath.
00:13:26.000 --> 00:13:27.679
Exactly.
00:13:27.679 --> 00:13:32.159
So just making sure it's clear what the expectations are at the same time in Slack.
00:13:32.159 --> 00:13:36.639
I think there is a moment, uh, if it's over 24 hours, it's kind of feels like you're ignoring somebody.
00:13:36.639 --> 00:13:43.200
And so there's gonna be a fine balance there of don't respond too quickly, but also don't keep people waiting.
00:13:43.200 --> 00:13:47.840
Um, and just make sure that you're measuring that stuff and that you're um clear with your customers.
00:13:47.840 --> 00:14:00.799
The other thing I would say is try to empower your customers to um sort of understand the protocol and context for how to how to report a ticket inside of Slack because different people use Slack in different ways.
00:14:00.799 --> 00:14:02.080
Are they supposed to use a thread?
00:14:02.080 --> 00:14:02.720
Are they not?
00:14:02.720 --> 00:14:05.519
Are they supposed to upload all the attachments there?
00:14:05.519 --> 00:14:07.679
Do they need to include more information?
00:14:07.679 --> 00:14:12.720
Like, what are you expecting from your customers when they're reporting something in these in these Slack channels?
00:14:12.720 --> 00:14:14.320
When do they get the Slack channel?
00:14:14.320 --> 00:14:16.320
Who should be in it on their side?
00:14:16.320 --> 00:14:24.240
Um, a lot of these things you can just be pretty clear with your with your customer about what your expectations are, and they don't know there, this is still a relatively new thing.
00:14:24.240 --> 00:14:32.720
And so they'll be totally willing to sort of follow your lead on that um and say, hey, we we'd like you to have three representatives from your organization in this.
00:14:32.720 --> 00:14:35.840
Here's the the different people that we expect to be in here.
00:14:35.840 --> 00:14:43.360
Um when you report an issue, we we try to respond within 30 minutes and we'll thread the issue and it'll be in this thread.
00:14:43.360 --> 00:14:45.759
And please upload any attachments inside of that thread.
00:14:45.759 --> 00:14:47.120
Just simple stuff like that, right?
00:14:47.120 --> 00:14:55.679
You can use like the um you could link to a Google Doc in the description of the channel as an example of a way to do that.
00:14:55.679 --> 00:15:02.559
Um, so yeah, just be really clear, measure what you're doing, and make sure those expectations line up with your customer.
00:15:05.600 --> 00:15:06.480
That's it for today.
00:15:06.480 --> 00:15:12.879
Go to customersupportleaders.com forward slash one six seven for the show notes, and I'll see you next time.
