Image Title

Search Results for Luke Benkei:

Luke Behnke, Zendesk | PagerDuty Summit 2019


 

>>From San Francisco. It's the cube covering PagerDuty summit 2019 brought to you by PagerDuty. >>Hey, welcome back everybody. Jeff, Rick here with the queue. We're at PagerDuty. Simon in downtown San Francisco at the Western st Francis. I think we've just about busted the seams in this beautiful old hotel. Thousand people. Fourth conference. We're excited to be here. And the big announcement today is around, you know, PagerDuty getting closer to the revenue, getting closer to the customer, getting beyond just break fix and incident response. And a huge partner. Big announcement of that was Zen desk. So we're happy to have today from Zendesk. Luke Benkei, the VP of product. Lou, great to see you. Yeah. Hey Jeff, thanks for being here. Thanks for absolutely. So before we get into the announcements and some of this stuff with the, with PagerDuty, give us kind of an update on Zendesk. We're all happy to see as Zen desk email in our inbox have been, someone's working on are working on my customer service issue. >>But you guys are a lot more than that. We are, yeah. Thanks for asking. Yes. So Zendesk started in, you know, it as a great solution for customer support and solving customer support issues. And we've really expanded recently to think more about the overall customer experience. Uh, and so that means, you know, launching more channels where customers can reach out beyond just emails and tickets to live chat and messaging and really rich experiences to communicate with your customers. But it also means, uh, you know, getting into the sales automation world and kind of helping sales and success work together, uh, on the whole customer experience and the customer life cycle. And underneath all of it, uh, our new sunshine platforms and as sunshine, it's a CRM platform that allows you to bring in a ton of information about the customer. You know, the, the products that customer owns. >>Um, you know, how they, how you've done business with them across all the different systems you have, right, that you do business with. Some, most companies we talked to have hundreds of different systems that store a little bit of information about the customer elusive three 60 degree. I mean, the single view of the customer. You know, I talked to a customer recently that said, Oh, I have 12 CRMs. Like are you going to be my 13th? And we said, no. You had to bring the right bits of information into Zandesk in order to make the right kind of actions that you want to take on behalf of that customer. Whether it's routing them to the right agent at the right time, whether that's making sure this is a VIP customer that has a, a hot deal with your sales team and you want to alert the sales rep if there's an incident that's affecting that customer open right now. >>Or maybe you want to have a bot experience that really solves a lot of the customer, uh, pain with knowing who that customer is, what products they own, et cetera. Right? So, right. That's really been what we've been trying to do with sunshine is, is move beyond just customer support into, uh, a full blown CRM solution. The one, you know, one place where a lot of your customer information can live to deliver that experience. Okay. So then we've got PagerDuty. So PagerDuty is keeping track of have more incidents, not necessarily customer problems per se, but system system incidents and website incidents and all these. How does that system of record interface with your system of record to get a one plus one makes three? That's it. I mean, so you know, if PagerDuty is the source of truth where your dev ops team and your developers and your product team are when there's an incident, you know, I've been part of this, uh, unfortunately we've, you know, if we have an incident at Zendesk, I'm, I'm in there as well kind of understanding what's happening, you know. >>But what's really missing there is that customer context and who's affected, you know, and even as good as our monitoring might be, sometimes customers tell us they're having problems, uh, or, or the extent of the problems they're having before we've fully been able to dig into it. Right? And so taking those two systems, the incident management portal and the customer record on the customer communications portal and bringing those two together, you know, it's better for the dev ops teams. They can learn. Like maybe we're getting some insight from the field about exactly who's affected and it's great for the customer support team because they don't have to sit there and tapping the, the engineer on the shoulder like have you fixed it yet? Right. What's the latest? Right. They can write within Zendesk with the new integration that that the PagerDuty Zendesk integration that we are, that we announced today, right. >>Within Zendesk, you know, reps can see a support, reps can see exactly what's happening in, in pretty close to real time with that incident so that they can keep customers proactively up to date. You know, before the customer reaches out, I have a problem, you know, they can say, Hey, here's the latest, you know, we're working on it. We estimate a fixed in this amount of time. Okay, now we've launched a fix. You should start to see things coming back up. Right. Okay. That that's a one plus one equals three. Okay. This is a two way communication. It's a two way writing. Yeah. I'm just curious, how does it, how does it get mapped? How does this particular Zen desk issue that I just sent it a note that I'm having a problem get mapped to, you know, this particular incident that's being tracked in PagerDuty. >>We got, you know, a power outage at a, at a distribution center right place. How do I know those two are related? So it's a, it's a two way integration, right? So it's installed both into the PagerDuty console as well as into Zendesk support where your agents are. And so, uh, you can create a really, it's all about the incident number and so you can create that out of, out of PagerDuty and then start attaching tickets, uh, as they come in to that incident or a customer's. Our rep could create an incident in PagerDuty, right through Zendesk. And so, you know, you're really working off of that same information about that incident number and then you're able to start attaching customers and tickets and other information that your customer support rep has to that incident number. And then you're all working off the same, you know, the same playbook and you're all understanding in real time if, if the developers are updating what's happening, the latest, the latest on it, you can sort of see that right in Zendesk and it's all based on that, that incident. >>So that's gotta be a completely different set of data and or you know, kind of power that the customer service agent has with this whole new kind of dead data set of potential if not root causes, at least known symptoms. Yeah, exactly. That's right. I mean, you know, part of our job on the product team at Zendesk is to sit with real customers and watch them shadow agents, watch them do their job every day and it's an ma even sometimes I log in and actually field tickets myself for Zendesk and it's an incredible experience to sit there and you log in and customers just start reaching out to you and they want answers, they want information. And you know, we've, we deliver a lot of automation and, and products like that, but still it's up to that customer support rep to quickly get back to that customer. >>And so to have some data right in front of them, Oh, it looks like this customer uses a certain product, that product is affected by this outage. Right. To be able to immediately have that customer support rep kind of alerted there is an outage. It might be effecting this customer, here's the latest information I can give that customer, you know, that's just less back and forth and round trips that they have to do to solve that customer's problem. Right. You know, as customers ourselves, we don't want that. We don't want to have to sit and wait or do they even know my tickets open? Do they have an update for me? I've been waiting 20 minutes, you know, to cut that down to give the agents context, it's, it's huge. It really helps them do their job. And of course the Holy grail is to not be reactive, to wait for the ticket, but to get predictive and even prescriptive. >>That's it. So where's that kind of in terms of, of your roadmap, how close are we to know adding things where we can get ahead, you can get ahead of the clients can get ahead of we see this coming down the road, let's get ahead and nip it in the bud before it even becomes a problem. Yeah, I mean, you know, we all are accustomed to whatever the last great experience we had with a company that suddenly just becomes what we expect next. And I think a big trend we're seeing in the last year or two is really customers want to get more proactive. And so we launched the Zendesk sunshine platform, which is all about bringing more of that data in. And the vision there then is really being able, which a lot of our customers are doing today. You know, they're able to say, I know which customers are using a certain product and when that product has an issue, send a proactive ticket. >>You know, before they even reach out to you were aware of an issue. You might be seeing these symptoms, here's some troubleshooting advice and here's our latest update and we'll keep this ticket up to date. We'll keep this conversation up to date as we learn more. You know, customers are already doing that was NS, but you're exactly right. That is more and more customers are trying to get there because it's becoming expected. You know, customers don't want to have to uh, log in and find that something's down and then try to troubleshoot unplugged re, you know, figure out, maybe it's me, maybe it's them. They want to know, okay, I get it. I can now plan around that. Maybe I'll go have my agents go work on a different, um, you know, updating some knowledge content or maybe put them on a different channel for a little bit or move people around depending on what's happening in the business. >>You know, the other thing that came up in the keynote that I think it's pretty saying that I don't know that people are thinking about is that there's more people that need to know what's going on than just the people tasked with fixing the problem. Whether it's account reps, whether it's senior executives, whether it's the PR team, you know, depending on the incident, there's a lot of people that aren't directly involved in fixing the incident that's still need that information and that seems like a super valuable asset to go beyond the ticket to a much broader kind of communication of the issue. As we actually, as we started to work, uh, with PagerDuty on expanding this integration with Zendesk and PagerDuty, we were talking to their team and we both have the same mantra, which is that the customer experience, it's a team sport. You know, it's not just the developers who are trying to fix the problem on behalf of the customers and it's not just your front line customer support reps who are fielding all those inquiries, right? >>It's everybody's job. In the end, as you said, the sales rep wants to know what's happening with my top accounts. Do I need to get in touch with them? Do I need to put in a phone call? Uh, you know, do I need to alert other teams? Maybe we should stop the marketing campaign that we were about to send. Cause the last thing you want is a buy more stuff, email when the site is down right now. So let's really start to think about this as a team sport. And I think this integration is a really great, uh, you know, how customer support and product and dev ops and engineering can kind of work together to deliver a better customer experience. It's, it's, so, it's, so Kate, you know, kind of multifaceted, so many things that need to happen based on that. Really seeing that single service call, that single transaction. >>Awesome. Well Luke, thanks for uh, for sharing the story and yeah, it's great to hear the Zendesk is still doing well. We are like, I like Zen desk emails like, yeah, I know. The next thing that we'll do is I will start to solve your problem before you even have to get us on that split up. Like we'll be working on your behalf even when you're not getting it. Okay. So Luke, thanks. Thanks Jeff. Appreciate it. See ya. Alright, he's Luke. I'm Jeff. You're watching the cube where PagerDuty summit in downtown San Francisco. Thanks for watching. We'll see you next time.

Published Date : Sep 24 2019

SUMMARY :

summit 2019 brought to you by PagerDuty. you know, PagerDuty getting closer to the revenue, getting closer to the customer, getting beyond just break fix and incident Uh, and so that means, you know, launching more channels where customers can reach out beyond just Um, you know, how they, how you've done business with them across all the different systems you have, I mean, so you know, you know, it's better for the dev ops teams. You know, before the customer reaches out, I have a problem, you know, they can say, Hey, here's the latest, And so, you know, you're really working off of that same information about that incident number I mean, you know, part of our job on the product team at Zendesk is to sit with real customers I can give that customer, you know, that's just less back and forth and round trips that they have to do you know, we all are accustomed to whatever the last great experience we had with You know, before they even reach out to you were aware of an issue. you know, depending on the incident, there's a lot of people that aren't directly involved in fixing the incident that's a really great, uh, you know, how customer support and product and dev ops and We'll see you next time.

SENTIMENT ANALYSIS :

ENTITIES

EntityCategoryConfidence
JeffPERSON

0.99+

Luke BenkeiPERSON

0.99+

LukePERSON

0.99+

Luke BehnkePERSON

0.99+

San FranciscoLOCATION

0.99+

20 minutesQUANTITY

0.99+

RickPERSON

0.99+

ZendeskORGANIZATION

0.99+

Thousand peopleQUANTITY

0.99+

13thQUANTITY

0.99+

12 CRMsQUANTITY

0.99+

KatePERSON

0.99+

twoQUANTITY

0.99+

threeQUANTITY

0.99+

hundredsQUANTITY

0.99+

two systemsQUANTITY

0.99+

oneQUANTITY

0.99+

todayDATE

0.99+

bothQUANTITY

0.99+

two wayQUANTITY

0.99+

PagerDutyTITLE

0.99+

Fourth conferenceQUANTITY

0.98+

LouPERSON

0.98+

60 degreeQUANTITY

0.97+

last yearDATE

0.97+

SimonPERSON

0.96+

PagerDutyORGANIZATION

0.96+

single transactionQUANTITY

0.95+

Western st FrancisLOCATION

0.94+

ZenCOMMERCIAL_ITEM

0.93+

PagerDuty summitEVENT

0.89+

PagerDuty Summit 2019EVENT

0.89+

one placeQUANTITY

0.88+

single service callQUANTITY

0.88+

two way integrationQUANTITY

0.81+

PagerDuty summit 2019EVENT

0.8+

two way communicationQUANTITY

0.8+

ZenORGANIZATION

0.73+

ZandeskLOCATION

0.73+

single viewQUANTITY

0.73+

systemsQUANTITY

0.53+