TRANSCRIPT 🔗
WEBVTT
00:00:08.240 --> 00:00:09.679
Hello and welcome.
00:00:09.919 --> 00:00:21.120
I'm Rob Wilkinson, and today we're taking a closer look at outcome-driven AI in customer experience and why CX leaders are demanding proof rather than promises these days.
00:00:21.760 --> 00:00:36.159
So if you're challenged with making AI pay off in real customer loyalty or if you're exploring automation without damaging the customer relationships, stay with us because you're going to get some practical takeaways you can use in your organization this quarter.
00:00:37.039 --> 00:00:41.520
Because today I'm joined by Brad Bernbaum, CEO and co-founder at Customer.
00:00:41.840 --> 00:00:43.679
He's very much an expert in this space.
00:00:44.159 --> 00:00:53.280
And his role gives him a very unique vantage point, really, on the decisions and risks or even opportunities, I guess, that CX leaders are seeing uh in this space today.
00:00:53.439 --> 00:00:54.719
So welcome, Brad.
00:00:54.880 --> 00:00:55.840
Thanks very much for joining me.
00:00:56.560 --> 00:00:57.840
Oh, so good to be here today, right?
00:00:57.920 --> 00:01:00.000
I really uh really appreciate you having me here.
00:01:01.039 --> 00:01:08.079
So recently uh there was an announcement from customer around your new uh architect uh element of the platform.
00:01:08.239 --> 00:01:17.599
So and in that announcement, um you talked around how um CX AI has been being measured by kind of the wrong standards.
00:01:18.159 --> 00:01:24.480
Just to kind of before we we get into the detail of that though, can you kind of break that down and set the scene for our audience?
00:01:24.640 --> 00:01:30.959
What is what is it that's broken about uh deflection rates and handling time as success metrics nowadays?
00:01:31.599 --> 00:01:33.519
Sure, no, um happy to.
00:01:34.239 --> 00:01:48.000
So as the world of AI has been evolving and it's certainly evolving quite rapidly, um, I think initially people were happy to see AI do anything it could it could do for them, right?
00:01:48.079 --> 00:01:59.040
If it could, if it could help a little, if it could deflect, which is a word we don't really like around here, um, but provide some form of perceived value or or not perceived, actual value.
00:01:59.359 --> 00:02:21.520
Um as people have been doing more and more of that on our platform, on other platforms, just generally in the industry, um, we're noticing, and we we we certainly feel it as well here at Customer, that the shift now needs to go from using a lot of AI to actually making sure you're getting proper benefit from the AI, which of course would be the outcomes, right?
00:02:21.680 --> 00:02:28.319
So, not just to use AI for AI C, because that um you know that that doesn't get too much value, right?
00:02:28.400 --> 00:02:33.199
We we we see in the world people, when AI first started, everybody's like all about token maxing, right?
00:02:33.280 --> 00:02:34.560
Like that's about token max.
00:02:34.719 -->
Load full transcript
00:02:50.879
And people are realizing quickly, like, just because you spend$5,000,$8,000 per person per month on tokens, as maybe a developer or or or somebody doing marketing, it's it's not about the use of the tokens, it's about the value of the tokens, it's about the outcomes that those tokens are going to drive you.
00:02:50.960 --> 00:02:52.960
And the same maps to CX.
00:02:53.280 --> 00:03:04.960
And that's really where this next generational shift needs to go, is focusing not around having AI do something for you, but getting the value of that of that something, um, getting the outcome of that something.
00:03:05.039 --> 00:03:12.879
And that that's really where we're where we're helping drive, uh hopefully helping drive the industry's mind shift towards.
00:03:13.840 --> 00:03:14.800
It does make sense.
00:03:14.879 --> 00:03:21.520
And and we really do have to be mindful of this, because you mentioned the how fast this space is is evolving.
00:03:21.680 --> 00:03:32.080
And with that evolution of technology comes evolution of people's roles and for this kind of conversation, those metrics that drive everything or that kind of monitor everything.
00:03:32.159 --> 00:03:38.560
And sometimes, you know, are delivering you know the border pack that says this is the ROI we're getting off investment.
00:03:38.879 --> 00:03:43.120
So we really shouldn't um we really should uh let those evolve as well.
00:03:43.360 --> 00:03:44.639
So it's really, really important.
00:03:45.360 --> 00:03:53.840
Um I guess um you you s you talk to different organizations, different sectors all the time, and you see how they're doing this.
00:03:54.240 --> 00:03:57.439
So can you kind of share a bit of insight into what you're seeing?
00:03:57.680 --> 00:04:14.719
If if we're swapping out uh the kind of uh the old school ticket metrics, for want of a better phrase, uh, to these more fo like outcome-focused um metrics, what would be the kind of the three measures that you would say this has got to be in the board pack for a CX leader today?
00:04:15.199 --> 00:04:15.599
For sure.
00:04:15.759 --> 00:04:21.600
Um, well, first and foremost, it completely varies on the type of company that you are, right?
00:04:21.759 --> 00:04:28.639
So if you are a retailer, um you might care about increasing revenue.
00:04:28.879 --> 00:04:39.519
You might care about if somebody is returning um a sh a black shirt, you maybe want to try and get them to buy the gray shirt instead, instead of just processing the term, right?
00:04:39.680 --> 00:04:42.639
So um there's there's revenue could be a very big piece of it.
00:04:42.720 --> 00:04:45.360
But again, it depends on the on the type of business you are.
00:04:45.519 --> 00:04:52.560
Um but I think the best way that I would distill it is the businesses need to know what's most important to them, right?
00:04:52.720 --> 00:04:54.800
What's what's their north star?
00:04:55.040 --> 00:05:04.639
Um, and we're seeing that CX is helping
drive non-conventional CX North star, you know, not non-conventional CX North Star.
00:05:04.959 --> 00:05:12.240
So um historically, CX was all about CSAT and and handle time and how quickly did you get a response out.
00:05:12.319 --> 00:05:15.040
Those are still very important metrics, to be clear.
00:05:15.360 --> 00:05:21.279
But now as we're moving towards outcome-driven metrics, it's how can you help the business, right?
00:05:21.519 --> 00:05:26.319
So it's not just um the conventional metrics anymore.
00:05:26.399 --> 00:05:28.560
It's it's how am I helping grow revenue?
00:05:28.720 --> 00:05:33.600
How am I helping customers think about retaining their subscriptions for subscription-based business?
00:05:33.680 --> 00:05:38.399
If you're a B2B SaaS business, um, how are we upselling other products along the way?
00:05:38.480 --> 00:05:40.480
How are we recommending other products, right?
00:05:40.639 --> 00:05:51.680
So there's there's many different ways to think about business outcomes that then get layered on top of conventional CX metrics and ways that you know those of us have been doing this a long time.
00:05:51.759 --> 00:05:58.399
The call center, there's they're still important, those metrics, but but the outcomes layer on top, and the AI should help drive that.
00:05:58.720 --> 00:06:08.879
So it's a hybrid, I would say, of those conventional and and these these newer ones that I would just say I can't give you three because it's really depends completely on your business.
00:06:10.480 --> 00:06:15.439
You know, if you're if you're if you're in travel, um, you know, we have some travel customers.
00:06:15.600 --> 00:06:23.600
If you're in if if you're in travel and a flight gets canceled, um the outcome should be to get you on another flight, right?
00:06:23.680 --> 00:06:28.319
Um, one that works best for your timing and your location and hopefully the cost, right?
00:06:28.480 --> 00:06:35.439
So like the outcomes are completely dependent, in my opinion, on the business and what's most important to the business.
00:06:35.600 --> 00:06:54.240
Um, but really it's it's marrying um improving customer satisfaction and what customers desire, which is immediate, amazing responses, hopefully with the resolution that they desire, um, but coupled with now how the business can also benefit from that great experience.
00:06:54.399 --> 00:06:56.480
And that that's really how I would think about it.
00:06:57.600 --> 00:07:01.519
It's a it's an interesting uh approach that to monitor those two things.
00:07:01.680 --> 00:07:09.120
And I'm glad that you didn't have you know three stock ones to to throw in the mix because it's not always you know the the right thing to do.
00:07:09.279 --> 00:07:11.120
And I think we're all learning, aren't we?
00:07:11.279 --> 00:07:20.879
So the fact that um these uh these outcomes are gonna be more closely measured and they're gonna be done in the way that you suggest that that's that's only a good thing.
00:07:21.040 --> 00:07:35.040
Um and it's complementary to um kind of the more uh more traditional stats that we still monitor, um but but that obviously they can't they don't they don't translate into the world of AI, so they've got to be kind of uh you know kept over there where they belong.
00:07:35.279 --> 00:07:42.079
So um something that we do see a lot of uh organizations looking at now is um observability.
00:07:42.480 --> 00:07:49.120
So um what does that basically what does AI observability look like in CX work?
00:07:49.519 --> 00:07:57.360
We've got leaders all the time talking around, yeah, but you know, how does the AI uh sorry, how does the AI uh reach the outcome?
00:07:57.439 --> 00:07:58.639
How does it come up with the answer?
00:07:58.720 --> 00:08:01.680
And and can we trust it to do what it's done?
00:08:01.839 --> 00:08:09.759
Uh you know, it's it does that kind of especially for new people to this, there's there's a kind of a concern and a risk attached to that, isn't there?
00:08:10.720 --> 00:08:25.680
Yeah, look, I think if you pick the right product, the right partner in your AI transformation journey, they will help you with that and they'll they'll they'll provide you a lot of the tooling that you do require to focus on trust, right?
00:08:25.759 --> 00:08:32.799
So in a customer, trust and and now AI governance is really a part of trust, is something we're we're very, very focused on.
00:08:32.879 --> 00:08:35.360
And AI governance is uh you know a new buzzword, right?
00:08:35.440 --> 00:08:37.120
Everybody's talking about AI governance.
00:08:37.279 --> 00:08:44.320
Um, because you do have to to um make sure that it's behaving correctly and doing the right things.
00:08:44.480 --> 00:08:50.080
And you know, there's there's examples out there on the internet of of AI doing kind of wacky things, right?
00:08:50.240 --> 00:09:05.519
So I think the way that that we think about it is one, from the ground up, we've always believed that you know trust must be woven into all facets of delivering CS experiences and AI in particular needs it needs it you know all over the place.
00:09:05.840 --> 00:09:11.679
So for us, you know, there's a lot of ways to think about trust and governance in our platform.
00:09:11.840 --> 00:09:32.240
Um one is is just simply as you're creating uh what we call our procedures, um we have an incredibly complex and sophisticated uh evaluation platform and framework that will make sure that the AI delivers the results you expect every time, right?
00:09:32.399 --> 00:09:38.960
So we'll you'll you'll run it through and run many, many, many, many iterations because AI is non-deterministic, right?
00:09:39.200 --> 00:09:44.639
You might get this slightly different answer for something you ask virtually the same way every time, right?
00:09:44.720 --> 00:09:46.320
It's it's it's theoretically possible.
00:09:46.480 --> 00:09:49.039
So you need to tune and make sure your prompts do that.
00:09:49.200 --> 00:09:54.159
So we've got a really rich evaluation framework that will run against that.
00:09:54.320 --> 00:09:57.039
Um, and then we use AI to help build AI.
00:09:57.120 --> 00:10:07.120
It's kind of inception-like, but you know, so we have um assistants that are a part of our evaluation framework that evaluate um evaluate the evaluations.
00:10:07.200 --> 00:10:20.320
That's an interesting one, but evaluate the evaluations and make recommendations on how to tune um your your procedures uh to get even better out output and better, sorry, better out uh better responses.
00:10:20.639 --> 00:10:25.039
So, you know, that's just one way that we see this happening.
00:10:25.200 --> 00:10:42.799
Um, you know, other other ways are moving to uh sticking within certain boundaries from a governance perspective, making sure AI doesn't veer off that way or that way and stays keeps you on the straight and narrow path of what it is that you want to talk about and not allowing you to go this way or not allowing you to go that way.
00:10:42.960 --> 00:10:45.200
So there's a variety of ways that you can do it.
00:10:45.279 --> 00:10:46.480
But yes, it is important.
00:10:46.799 --> 00:10:50.159
Um it's important that you find a partner who understands that.
00:10:50.240 --> 00:11:00.240
It's important that you find a partner who um whose products you know will enable that and and put it first and front and center.
00:11:01.840 --> 00:11:19.200
So it's it's it's exciting to hear that um the you know that with the evolution of AI, we now have bots monitoring bots and uh fine-tuning and helping them to improve and to ensure that that kind of uh that trust is there and that that observability is in there.
00:11:19.519 --> 00:11:28.080
So it's really yeah, some people might kind of historically, and I think in a couple of like 18 months ago, two years ago, it was kind of people's like big brother scenario.
00:11:28.720 --> 00:11:31.120
If they'd have heard about that, that they'd be they'd be worried.
00:11:31.200 --> 00:11:48.720
But it's it's it's I think uh everybody's seen how uh robust now uh the this AI is and uh some of these things are only possible now because it's uh the technology's shifted, it's improved, and and it's so much stronger than it than it was even just a year ago.
00:11:49.039 --> 00:11:54.399
And and the speed at which it's continuously improving is is is quite hard to keep track of.
00:11:54.559 --> 00:11:57.279
So it's uh yeah, it's it's really interesting to hear.
00:11:57.360 --> 00:11:58.399
So thanks for that.
00:11:58.559 --> 00:12:13.759
I think we've gone into uh I think we've got a nice grasp on kind of the operational impact and and I want to talk a little bit more around the kind of the broader strategy, the market, the the wider market kind of uh let's look at um look at things in a in a bit more detail.
00:12:14.000 --> 00:12:26.480
So if we've got messy stacks and we've got inconsistent knowledge, how can you
recommend an approach to rolling out CXAI without any chaos attached?
00:12:26.639 --> 00:12:32.399
Um where should people start and what's the thing that they've got to do or got to have to be true first?
00:12:32.960 --> 00:12:33.679
Sure, sure, sure.
00:12:33.759 --> 00:12:34.639
No, it's a great question.
00:12:34.799 --> 00:12:37.039
We are asked this all the time here at Customer.
00:12:37.200 --> 00:12:42.720
Um, we obviously have a point of view um that we're the way that we think is correct.
00:12:42.960 --> 00:12:48.080
But when we see, and this has been true for the contact center for for decades, frankly.
00:12:48.240 --> 00:12:51.440
It's it's how customers started almost 11 years ago.
00:12:51.679 --> 00:13:04.080
Um we believed having a variety of disjointed tools to try to service the one the one effort of providing amazing support experiences makes it really challenging.
00:13:04.159 --> 00:13:07.600
Um and that's what customer has always been about since day one.
00:13:07.840 --> 00:13:21.360
Um being the centralized platform to match your customer, to um to take care of all the exchanges, all the interactions, all the data, and orchestrate all of it together, right?
00:13:21.440 --> 00:13:34.080
So not having 15 or 20 different tools to manage things because when they inevitably try and work together, you get a little crisscross, a little confusion, um, probably a suboptimal experience.
00:13:34.399 --> 00:13:38.240
Well, um, as it relates to AI, we see that the same way.
00:13:38.399 --> 00:13:48.240
So there's a lot of you know, bolt-on tools out there, we call them, um, where they will sit on top of something else and they'll they'll they'll do their best to do a good and fine job.
00:13:48.559 --> 00:14:18.559
But when you have everything in a cohesive system and a product that can interrogate everything and all everything we know about the customer, the CRM capabilities, um coupled with all the abilities to talk to third-party systems via MCP, via our app platforms, app integrations, via OpenAPI, those two things in unison really do provide a rich experience to help avoid the chaos and help provide the cohesive data set that the AI can build on top of and take full advantage of.
00:14:18.720 --> 00:14:32.000
Even simple things like your knowledge base, having your knowledge base inside of the AI platform has value because AI needs, they're all the models are trained on the same general public data.
00:14:32.240 --> 00:14:35.600
Um they're not trained on your company-specific data.
00:14:35.679 --> 00:14:38.080
So therefore, you know, and nor should it be, by the way.
00:14:38.240 --> 00:14:46.399
Um, so it's gonna rely on all the data sources it can it can use to create those proper responses and to give the customers the best answers.
00:14:46.639 --> 00:14:52.559
So when you have all of the knowledge coming from all the different places, that's how you're honestly gonna get the best outcomes.
00:14:53.039 --> 00:14:53.360
Right.
00:14:53.600 --> 00:14:54.879
Yeah, it's like anything.
00:14:54.960 --> 00:14:59.120
We we all work this base in this industry, we we evolve all the time.
00:14:59.200 --> 00:15:00.960
We have new technology all the time.
00:15:01.519 --> 00:15:05.759
I don't think there's a better place for technology in than contact centers and CX.
00:15:06.240 --> 00:15:16.159
Um and I think we've in the past we've actually managed really well to adopt those technologies, uh, and we do it by getting the foundations right, don't we?
00:15:16.240 --> 00:15:20.080
And it's always the data needs to be right and the foundations need to be in place.
00:15:20.159 --> 00:15:22.960
And I guess you're saying it's not that's the same now with this.
00:15:23.600 --> 00:15:30.320
These are the kind of fundamental things that just because AI is really clever and powerful, it's not a miracle worker.
00:15:30.559 --> 00:15:33.120
Yeah, you put rubbish in, you get rubbish out, don't you?
00:15:33.200 --> 00:15:35.679
So yeah, that context is so important.
00:15:36.000 --> 00:15:45.840
Um and yeah, if you've got too many uh tools talking to each other, the risk of that context getting muddy is is is too high, really.
00:15:46.399 --> 00:15:52.000
Um there's such a lot of noise around AI agent dry now.
00:15:52.320 --> 00:15:55.200
Um so I want to try and cut through that a little bit.
00:15:55.440 --> 00:16:02.000
Um CX specifically then, where should uh leaders allow autonomy today?
00:16:02.399 --> 00:16:08.480
Um and where should they be saying actually human in the loop, absolute necessity, non-negotiable?
00:16:09.279 --> 00:16:09.600
Sure.
00:16:09.679 --> 00:16:12.480
Um again, every business is gonna be different, right?
00:16:12.639 --> 00:16:23.759
If you're um selling an incredibly high-end expensive product, you might need a little bit more human oversight um than a than a more modestly priced product.
00:16:23.840 --> 00:16:25.600
So I do think it depends on every business.
00:16:25.679 --> 00:16:29.600
I think it depends on the use cases and severity of your of your business and your outcomes.
00:16:29.759 --> 00:16:32.320
So I'd preface it by by saying that.
00:16:32.399 --> 00:16:35.279
Um but what I what I would say is AI is getting very good.
00:16:35.440 --> 00:16:38.000
RAI is great, just in general, it's great.
00:16:38.080 --> 00:16:44.240
And the models, we all live off the same frontier models, and they are incredibly powerful and getting more powerful by the day.
00:16:44.399 --> 00:16:53.840
Um, and we're just gonna continue, you know, in our opinion, those are gonna continue to exponentially get better and better and enable all of us to just provide even better and better and better outcomes.
00:16:53.919 --> 00:16:59.600
So we're going to see containment rates going up, we're going to see outcomes improving.
00:16:59.759 --> 00:17:03.440
That's, you know, to me, that's that's a given at this point in time, right?
00:17:03.519 -->
00:17:07.200
Our our products and our applications will continue to become better, the models will become better.
00:17:07.279 --> 00:17:08.240
So that's gonna happen.
00:17:08.319 --> 00:17:14.720
However, we're definitely not in a world where AI can handle 100% of everything.
00:17:14.880 --> 00:17:16.799
I I don't I don't see that yet, right?
00:17:16.960 --> 00:17:19.119
Maybe certain use cases, yes, but generally no.
00:17:19.200 --> 00:17:25.279
I mean, we're seeing at customer we're seeing really high containment rates of you know 70% for some of our customers.
00:17:25.359 --> 00:17:28.720
So like we are able to see some of that magic truly happen.
00:17:28.960 --> 00:17:37.359
Having said that, um, we generally believe in a world of of AI doing a lot of work, but humans also in the loop, right?
00:17:37.440 --> 00:17:38.960
We we we we still see that.
00:17:39.119 --> 00:17:40.960
Um there's a variety of reasons.
00:17:41.119 --> 00:17:43.200
Um humans have empathy, right?
00:17:43.279 --> 00:17:44.960
Uh AI has less empathy.
00:17:45.599 --> 00:17:49.920
I'm hearing stories where it's it's getting better, actually, but like it's not there yet, right?
00:17:50.160 --> 00:17:53.119
So I think there's a there's a fine line.
00:17:53.200 --> 00:17:59.599
So I think one, there's just operational things you may say that like, oh, any return under$100, yeah, I can always handle.
00:17:59.759 --> 00:18:04.880
Any any return, you know, between$100 and$1,000, you know, you can have a few boundaries.
00:18:04.960 --> 00:18:09.440
And any return over$5,000, then you know, human must approve, right?
00:18:09.599 --> 00:18:13.119
So like you can define those those guidelines, those boundaries, if you will.
00:18:13.200 --> 00:18:15.440
And I and I do see some companies doing that.
00:18:15.680 --> 00:18:22.640
Um, other examples though, where I see AI and humans working together, um, maybe sometimes goes back to the empathy example.
00:18:22.720 --> 00:18:26.559
Let's say I want to return, you know, a shirt, a simple, a simple item.
00:18:26.720 --> 00:18:33.039
I want to return a shirt and the company's return period is 30 days, and I try and do it at six months.
00:18:33.359 --> 00:18:35.839
And the AI is just not gonna allow it.
00:18:35.920 --> 00:18:42.079
It's gonna, it's generally gonna say, you know, look, our return policy is 30 days, you know, we're really sorry.
00:18:42.240 --> 00:18:46.319
Um, you know, thanks for your loyalty, but you know, it's 30 days.
00:18:46.400 --> 00:18:53.200
And if the customer continues to push inside and say, like, well, no, I had extenuating circumstances, or this happened, or that happened.
00:18:53.440 --> 00:18:58.559
Um we can actually have the AI say, look, we should give this to a human to look at.
00:18:58.720 --> 00:19:04.720
So it'll it'll move from an AI conversation to a human that will look at it.
00:19:04.880 --> 00:19:11.920
And where they go, where they work so so well together is the human may take a look and be like, oh wow, like Brad's extenuating circumstances were real.
00:19:12.319 --> 00:19:16.240
Um, and Brad's a really loyal customer, and Brad spends a lot of money with the business.
00:19:16.480 --> 00:19:17.759
We should just approve that.
00:19:18.000 --> 00:19:41.119
But where they where where the the humans in the loop work really well is, and we're one of the few companies that I think does this very effectively, is it goes from AI to human, but the human can look at it, could intervene, or the human could look at it and say, you know what, I'm just gonna approve this thing, approve this exchange, return, whatever it is, and it'll go back to the AI agent to actually process it and say, Oh, all right, like, yeah, we're gonna make that exception for you.
00:19:41.359 --> 00:19:49.759
So you're letting the AI do the more routine and mundane tasks, and then processing the return or exchange and collecting the information, like a human doesn't need to do that.
00:19:50.000 --> 00:20:07.359
So it can actually move between agentic human back to agentic, and customers really, really appreciate that about our platform because it it lets the human do, you know, the the parts that it needs to think about, but yeah, it can do most of most of heavy lifting.
00:20:07.440 --> 00:20:17.359
And um, you know, we kind of have a phrase around here, a slogan, if you will, uh buzz is is just our our objective is to turn humans from creators to reviewers.
00:20:17.839 --> 00:20:21.200
And that's just an example of of that, right?
00:20:21.279 --> 00:20:29.279
So rather than having to do all the work and create the response and create the actions, and they would review the suggestion, they'd review the recommendation.
00:20:29.359 --> 00:20:36.799
Um, and in doing so, one, you know, AI is doing the heavy lifting and the mundane tasks, but two, you're able to just be that much more effective.
00:20:36.880 --> 00:20:42.640
And when you are, um the companies are happy because they're reducing costs, the customers are happy because they're getting responses right away.
00:20:42.880 --> 00:20:44.160
Everybody wins, right?
00:20:44.240 --> 00:20:46.720
Um, and it helps businesses scale.
00:20:46.960 --> 00:20:50.480
So, you know, we're that is how I see AI moving.
00:20:50.640 --> 00:21:02.400
That's that's customers' point of view for how we see AI moving in the in the contact center is um conventional agent roles are gonna convert from from creators to reviewers.
00:21:03.680 --> 00:21:12.079
I like that that phrase, and it's it's very um very appropriate for the the the evolution of that role, isn't it?
00:21:12.559 --> 00:21:28.960
Um and you know they need to be supported, they need to be uh you know trained to deal with these different types of uh inquiries more often than how to be resilient because they're not gonna have the password reset easy things to do and uh their days are gonna be more intense.
00:21:29.119 --> 00:21:31.359
But I
think everybody understands that.
00:21:31.519 --> 00:21:44.880
Um I am interested in what you think though, is if we were to say that's today and that's kind of where we're at, um how long is it gonna take for AI to be able to do the reviewing as well?
00:21:45.599 --> 00:21:46.559
Because it's gotta be.
00:21:46.720 --> 00:21:50.880
I mean, if you'd have asked us if AI could do what he can do today two years ago, you'd have said no.
00:21:51.359 --> 00:21:56.640
So do you think there's a possibility that that that that role is is is down the line?
00:21:57.839 --> 00:21:58.480
I do.
00:21:58.640 --> 00:21:59.519
Um I do think.
00:22:00.319 --> 00:22:10.000
That there will be other models or other prompts that might actually work hand in glove and potentially do some of those reviews as well.
00:22:10.240 --> 00:22:15.359
But you could also argue that the creation of it should be so robust it doesn't need that.
00:22:15.519 --> 00:22:18.799
But I'll give you a slightly different analogy in the coding world.
00:22:18.880 --> 00:22:23.359
Um, and and we do a lot of AI coding, pretty much all AI coding at customer at this point.
00:22:23.680 --> 00:22:30.960
Um we've converted um all code always needed human reviews in the past, right?
00:22:31.039 --> 00:22:35.680
We we made sure of that to make sure that we're we're we're maintaining trust and security and writing good code, et cetera.
00:22:35.759 --> 00:22:42.559
It's a common practice in software engineering, but we now have multiple third-party products that are doing AI code reviews.
00:22:42.640 --> 00:22:50.559
So it's in the in the engineering world, there's AI creating the code through tools like Claude and Cursor, et cetera.
00:22:50.720 --> 00:22:58.799
But then we have other tools, once that code gets pushed up before it merges in, other tools that are then reviewing that code and providing feedback.
00:22:58.880 --> 00:23:00.240
And it is AI working together.
00:23:00.319 --> 00:23:02.799
So, like in the coding world, that's very much happening today.
00:23:03.039 --> 00:23:05.200
We we do that currently.
00:23:05.440 --> 00:23:12.880
Um and I joke because sometimes we we have multiple products doing the reviews because we want to have the best code we can, and sometimes they fight with each other a little bit.
00:23:12.960 --> 00:23:18.000
One will say do this, the other will say do that, and then it'll do that, and then the other, and we'll see a little bit of the fighting between them go back and forth.
00:23:18.079 --> 00:23:21.119
But generally speaking, it does an incredible job, right?
00:23:21.279 --> 00:23:26.319
Um, and I think as products and models continue to get better, they're gonna they're gonna do more.
00:23:26.480 --> 00:23:29.519
So I do think there's worlds where that may evolve into.
00:23:29.920 --> 00:23:32.240
Um I do actually.
00:23:32.400 --> 00:23:33.920
I do think that there are worlds of that.
00:23:34.000 --> 00:23:46.240
And I do think that we have two, I shouldn't say I think I know that we have tooling within the customer platform that is constantly reviewing how some of our AI is working and suggesting recommendations, suggesting ways to optimize it.
00:23:46.400 --> 00:23:57.359
So to a certain extent, that is reviewing your config on a on a regular basis and saying, hey, we notice customers are talking about this, you may want to optimize some of your prompts or the procedures to do that.
00:23:57.519 --> 00:24:07.279
So we are seeing that up today in our products, and I do think that we're gonna see that more um at the end user level at the at the at the customer to agent level.
00:24:07.599 --> 00:24:13.440
Realm it's real time, constant customer kind of continuous improvement in in real time.
00:24:13.680 --> 00:24:15.680
It's kind of amazing.
00:24:16.000 --> 00:24:18.720
Um so we're we're running out of time a little bit.
00:24:18.880 --> 00:24:31.039
So I just want to kind of um before we wrap up, I want to kind of have a look at your just get that give our audience the benefit of you know your your knowledge and what you what you've seen in the space.
00:24:31.440 --> 00:24:38.160
And and I want to my I want to put the TX leader hat on for just for one minute and I want to think about what are the right things to be doing.
00:24:38.240 --> 00:24:53.119
In fact, sort of a sensible step-by-step plan um to prove value from uh this uh this technology, um, kind of without overpromising to my business that the you know that we're gonna fail to deliver on those promises.
00:24:54.079 --> 00:24:59.200
Yeah, no, um, first off, I really do think that the world of AI is is amazing, right?
00:24:59.279 --> 00:25:01.839
I I often you know call it magic, right?
00:25:01.920 --> 00:25:05.759
Because it it is it is evolving so fast.
00:25:05.920 --> 00:25:13.039
The the tooling, the application, the models is it's is truly in in very interesting time to be in this world.
00:25:13.279 --> 00:25:20.559
Um and you know, I often I often tell people like my crystal ball is currently broken, like I no longer know where where things are going, right?
00:25:20.720 --> 00:25:25.440
We have a vision, of course, a customer, but like I can't see five years out anymore, right?
00:25:25.519 --> 00:25:34.319
I feel like I used to be able to, and I I don't know that I can because I can't predict the the power of these models and and the evolution of where they're going.
00:25:34.559 --> 00:25:41.440
Having said that, um I do think that there's really interesting ways to get started, right?
00:25:41.519 --> 00:25:45.440
I do think that um you should have reasonable expectations.
00:25:45.519 --> 00:25:53.039
I don't think you should expect that you're going to one one hour in, you know, handle 100% of everything perfectly.
00:25:53.200 --> 00:25:58.880
Like I don't, I don't, that's an unreasonable expectation on our product, or frankly any product, in my opinion.
00:25:59.119 --> 00:26:03.920
But I think what
you should start with is defining some of the most important business outcomes.
00:26:04.000 --> 00:26:07.359
I think you should think through what is what is most important to your business.
00:26:07.440 --> 00:26:14.559
And it might, your initial business outcomes might actually just be hand, you know, uh handling customers faster, right?
00:26:14.640 --> 00:26:15.920
Like getting to them right away.
00:26:16.079 --> 00:26:26.559
Because we've seen over the years, um CSAT directly correlates, conventional CSAT directly correlates to response time, right?
00:26:26.640 --> 00:26:32.079
If you get an immediate response, your CSAT levels are generally higher than if you had to wait a while, right?
00:26:32.240 --> 00:26:35.440
So um, and it seems obvious, but it's it's true, right?
00:26:35.519 --> 00:26:37.039
We have we have data behind that.
00:26:37.359 --> 00:26:51.599
So, you know, some people may want to just say, let me take a couple of my most important business outcomes, let's get started on that, let's get those up and running really, really quickly, let's learn, let's figure out how to go, and then we're just gonna keep adding and adding more ways that AI can help.
00:26:51.680 --> 00:26:55.039
Um, and that's generally what we see our our customers doing.
00:26:55.200 --> 00:26:58.799
Um, you know, boiling the ocean is probably not the way to go.
00:26:59.039 --> 00:27:01.359
Um, it's an evolution.
00:27:01.440 --> 00:27:03.359
So let's get you started, let's get you up and running.
00:27:03.440 --> 00:27:05.519
We get customers up and running very, very, very quickly.
00:27:05.599 --> 00:27:07.839
So to be clear, it's not a very long process.
00:27:08.000 --> 00:27:16.799
Um, basic things like uh basic RAG, retrieval of method generation off of our knowledge base, that's up and running in minutes or maybe an hour.
00:27:16.960 --> 00:27:22.880
So like you're already getting a lot of value where you're talking to your knowledge via chat and email, et cetera.
00:27:23.039 --> 00:27:24.880
So that that's like instant value.
00:27:25.039 --> 00:27:40.799
But then going further and making these more advanced procedures to take these actions to drive those those next level outcomes, you figure them out, you keep evolving them, you keep tuning them, and you keep adding additional ones as you're seeing them, as you're seeing the benefit, as you're seeing what's working.
00:27:40.960 --> 00:27:43.599
Um, yeah, pay attention to trust and governance.
00:27:43.759 --> 00:27:47.359
Make sure that you're writing proper evals, that you're not going off the rails.
00:27:47.599 --> 00:27:50.880
But you know, a good partner like us will help you with that.
00:27:50.960 --> 00:27:52.640
Um, we provide great tooling for it.
00:27:52.720 --> 00:27:55.039
So you're not writing code, but we'll provide you great tooling.
00:27:55.119 --> 00:27:58.240
But find a partner that's that's gonna that's gonna help you with it as well.
00:27:59.839 --> 00:28:00.880
That's fantastic.
00:28:01.039 --> 00:28:04.720
I think um, yeah, I think I think there's a lot to unpack there.
00:28:04.799 --> 00:28:06.240
So thanks so much, Brad.
00:28:06.319 --> 00:28:08.960
That's uh that's that's really useful stuff.
00:28:09.039 --> 00:28:11.920
Um unfortunately, it it is all we've got time for.
00:28:12.079 --> 00:28:14.559
So thanks again for joining me and answering all those questions.
00:28:14.720 --> 00:28:17.359
Um really enjoyed it.
00:28:17.599 --> 00:28:24.640
Um for anyone who's watching this though, uh uh maybe they want to kind of explore this in more detail, maybe look at what you guys are doing.
00:28:24.799 --> 00:28:26.319
What's the best way for them to do that?
00:28:26.720 --> 00:28:32.880
Oh, um, there's a tremendous amount of information on our website, www.customer.com with a K, customer with a K.
00:28:33.279 --> 00:28:45.440
Um and love for you to check it all out, check out our products, um, learn more, and then happy to schedule, you know, schedule time with people who want to learn more, see demos, understand how they can use our product and the value of it.
00:28:45.519 --> 00:28:51.119
We've got a great process to show you how how we can provide benefit to your company.
00:28:51.680 --> 00:28:52.480
That's great.
00:28:52.640 --> 00:29:00.720
Um, and don't forget, you can also find a wealth of related resources, uh, stories and other videos just like this one at cxtoday.com.
00:29:00.799 --> 00:29:03.039
Uh, but uh for now that does wrap everything up.
00:29:03.119 --> 00:29:05.279
Uh, I'm Rob Wilkinson for CX Today.
00:29:05.440 --> 00:29:07.119
Thanks very much for joining us.
00:29:07.599 --> 00:29:08.240
Thank you.