Why voice AI agents pass in the lab and fail on real calls: Liam Dunne (Klearcom)

Picture of Kane Simms
Kane Simms

Liam Dunne, Co-founder and CEO of Klearcom, joins me to talk about why voice AI agents can pass every lab test and still fail on real calls, and why testing the whole journey is becoming mandatory for global deployments.

More ways to listen and watch

About this episode

Your voice AI agent performs great in the browser. Then a real customer rings from another country and you have 7 seconds latency. Worse yet, the call never connects in the first place and you don’t even know about it.

Liam Dunne, Co-founder and CEO of Klearcom, joins us to talk about what really happens between a caller and your voice AI agent. We discuss why agentic voice AI is the fourth great migration for contact centres, why lab-test latency and real-world latency are so far apart, how in-country personas test the whole customer journey in situ and why testing is becoming mandatory for anyone deploying voice AI globally.

Links

I also talk about this with Klearcom in Testing the future: How Klearcom is powering the voice AI revolution, with Endre Davids of Seamly in From chatbot to voice AI: what changes? and in What does it take to make a voice AI agent reliable?.

Liam Dunne, Co-founder and CEO of Klearcom

Guest

Liam Dunne

Co-founder and CEO of Klearcom

Liam Dunne is co-founder and CEO of Klearcom, a voice AI testing and contact centre assurance company based in Waterford, Ireland. He has more than 20 years’ experience in telecommunications and technology and was a 2025 EY Entrepreneur Of The Year finalist.

Timestamps

00:00|Welcome back to Klearcom
00:36|What’s changed in voice AI since 2025
07:31|Voice AI is now a business priority
13:26|Following one call from your phone to the AI agent
19:35|What real-call testing looks for
24:11|Testing or monitoring?
27:02|In-country personas and real-world latency
32:06|How to fix poor latency
36:47|Why testing gets skipped
40:13|Voice AI adoption and why 2027 is the year
46:46|The people in the middle and the future of the contact centre
51:18|Consolidation across CCaaS, CRM and conversational AI

Transcript

Kane Simms: All right, Liam Dunne, welcome to the podcast, my friend. How the devil are you?

Liam Dunne: I’m doing very good. It’s a privilege, delighted to be on such a reputable podcast and talking about very exciting changes in the market. So last time the diehard viewers of VUX will probably remember the last time

Kane Simms: And we had Klearcom on the podcast, we had Satish Barot, the CTO.

Liam Dunne: I hate to follow Satish, he knows his stuff, I know he’s a ringer now.

Kane Simms: That was in July, I believe, 2025, over a year ago now. So in that time, as it relates to, let’s say, voice AI, voice in general, what’s changed?

Liam Dunne: Whoa. Oh, well, that’s a broad question, right? So much has changed. And really, I kind of like to use frameworks and conceptualize things, I believe, and certainly in this last quarter, I think the market indicators are there, we’re going through the fourth great migration. And that is the migration to agentic voice AI conversation AI, basically true agentic implementation within traditional call center space. And that’s what’s happening right now. And there look at the last quarter, Kane, you see all the conversation AI providers, they’re all across LinkedIn and all the analysts are saying what an explosion they’ve had in the last quarter alone and most of these providers have seen that single quarter growth has eclipsed the previous full year to date. So really we’re at that fourth great migration and I think there’s certain headwinds in the market driving all of this and it’s just a exciting time to be in our world. You know, I think the whole contact centre world, call centre world has, at periods, had kind of a brand, you know, perception there about it’s just all low value. And really that’s because I think we’ve done a couple of things really badly over the last number of years. And agentic voice, conversational AI is actually putting us back into the fore in terms of a true value lever right across the business. It’s not just about cost savings anymore. It’s about efficacy, it’s about scalability and really AI is caught up where we can do some really cool things at scale in voice.

Kane Simms: You mentioned there that, well, firstly, I think you’re right in terms of the growth. I’m looking here, ElevenLabs has now, what is it, 600 million ARR by mid 26, up from 200, it might have been the previous year. Valuation now, the valuation was 3.3 billion in January 25. It’s now worth, apparently, 22 billion, late 26.

Liam Dunne: These figures are, to me, in this instance, they’re justified. This isn’t just SaaS, this isn’t just AI. There’s real world examples of where all of these companies are adding value. We see it every day, it’s not just them. It’s all the providers when they see. So I believe that this is a new dawning for voice. I do believe that as well. It’s just been a fourth great migration, we’re entering a golden era of voice. Voice itself has so many benefits, it’s nearly four times faster than typing, first of all, it’s much more intimate in terms of it and instant in terms of communication vehicle. And I think you know that previously what our industry hasn’t done well and it has had an impact. I think chat was something that has been executed really poorly. put in place in our industry as a way of deflecting voice calls. And it wasn’t because the customer was actively looking for it, it was a cost-saving measure. And it was done poorly. And what’s happening is the components of why we were driven to chat can be true voice AI, or voice AI without sacrificing delivery. And that’s been a huge thing. So it is the real world. What I’m seeing voice AI achieve for enterprise customers in a multilingual multinational complex scenario that’s been and now couldn’t have been delivered a year ago, let alone two years ago. So it’s democratizing voice. We all know and sometimes I think boards are afraid to announce it. But the reason that this growth is happening is one of the reasons is cost. And because the most expensive component of voice is the human at the end of it and boards are pointing to saying, hey, can you take a portion of that calls that have been handled by humans and have agentic AI managed them? And they can and they should, because the benefits on everybody’s side, the consumer doesn’t want to have to wait. First of all, the consumer doesn’t want to have to dial into an IVR, press digits, say keywords and wait three minutes before they get to an agent for a very simple task. I want to speak to an agentic AI, and if it’s a simple task, like an account inquiry or an order update, I want to get straight to it. And then for the agents, and I come from that world, my first job in college was in AOL doing tech support back in the days when you’re dialing in a modem, you loaded your internet from a CD, and I was on the front line listening to all those simple technical queries that in now in this world, an agent is too highly skilled and high-valued. Actually, what it’s going to do is it’s going to move the human capital up the value chain, and it’s going to increase the value in terms of how that human contributes to the call center world overall. So I think this repositioning, it’s going to help kind of, it’s going to democratize, but also going to take away all that grunt work so that human capital in the call center world will really become subject matter experts. And it’s going to, I believe genuinely, and it’s going to reignite the whole contact center world and industry overall by this one massive paradigm shift. And I talk about it at the outset as the fourth great migration. So again, I’m here all my life from my call center work back in 1999. I’m giving my age away, right, back in the old days where you had server rooms at ISDN boxes, and nobody could even look at the door of the server room unless you had the right security clearance. So we went from PSTN SIP first one, then it went from on-prem to the cloud. Then we went on our third one, DTMF to speech. It wasn’t AI, it was machine learning. And now the fourth great migration is moving to this probabilistic world. And with that comes challenges that have to be de-risked. It’s not just a technical deployment anymore. If a company chooses to utilise agentic AI, it’s a business and many more board seats that are looking at it. risk

Kane Simms: And you kind of explained last time we spoke which I think was quite interesting in terms of, you know, you’re right. It’s a more, it’s not an innovation thing anymore, it’s well and truly like companies It’s on the agenda.

Liam Dunne: If you’re not doing it, you are truly left behind. I don’t think both the enterprise or the consumer will say businesses, when they talk about communications channel, not deploying the agentic AI because the scalability is there for both sides. So this is an actual fundamental need and deployment.

Kane Simms: Absolutely. With that then it used to be that certain teams that are deploying this technology could get away with a little bit more because the business isn’t looking at it quite as intently as it is now. So the risk is great not only because of the probabilistic technology as you mentioned but also because everybody’s eyeballs are on this now whereas it wasn’t before and when I think what a lot of businesses probably don’t appreciate is when your customer makes a call to your voice AI agent it’s not just their phone connecting to your voice AI agent there’s a whole load of stuff in the middle and a whole lot of dependencies in the middle that can turn something that you’ve built and when you test it, it’s fine, into something in the real world that actually doesn’t quite work quite so much. I wonder if you can shed some light on what’s going on behind the scenes when someone calls your voice AI agent, where are the dependencies and getting around to what Klearcom do is how do you validate that those dependencies are in safe hands. Where are the dependencies and

Liam Dunne: It’s interesting ultimately what people don’t realize that this lands on data centers and hardware in so many different instances and so much can go wrong. So in that question there, what’s great is you’re surfacing challenges that the market need to be aware of. So there’s risks across multiple different levels. One of them, to answer this question, is around the technical deployment. So I pick up the phone and I ring a toll free number in any country. It’s many links in that telecom chain that sends the call from customer to agent. So first of all, you’ve got the local in-country carrier. So typically, businesses will deal with and aggregate services like Tata, BT Global Services, AT&T, the new guys like Bandwidth and so on. and those guys will all have their own individual network. But outside of the network, they’re blind. So when a call lands onto a carrier network, it has to distribute internationally, it’s so different to a country. Network BT can only see what’s happening on their network in the UK, Eir in Ireland here, AT&T in the US and so on. And physically the call has to transfer across networks. And that’s just the first leg, that’s the carrier leg. Then you’ve got and within that carrier leg, there’s multiple different data centers and routing and hops within each one of those countries. Then you’ve got this leg, which is it’s landing in on your Genesys, your Five9, your NICE, your 8×8 and so on. And those guys have their own network. And again, within their network, they can only see what’s happening on their own corporate network, they’re not within each country. And then from there, it goes into the agentic voice providers. And what we’re seeing as well as for the large multinationals, they’re typically deploying minimum three agent providers, because you don’t want to rely on just one it gets to the enterprise. So that’s four links with individual data center locations, individual connections between each one thing that’s clear in all of this is that each provider can see what’s happening on their own leg of the chain, but I could have my conversational AI working correctly, but the call coming into my CCaaS from my carrier that ultimately sends into the conversational AI might be working. spot in all of these deployments, what we call the fourth great migration to conversation AI creates the fourth great blind spot because it’s another provider. provider in the tech stack. It’s another link in the chain. And what that does is it presents, I suppose, a challenge to enterprise customers. But when something goes wrong, how do I pinpoint it? What team do I scramble to investigate? I’ve got all these different providers. And how do I ultimately have my mean time to detection and mean time to resolution as optimum as possible. So to lead it on to my company and my side of the. And thank you for getting me there. We’ve basically built an Agentic AI platform that allows our customers to generate personas In all the major markets, using all the major carriers, and using all the major languages, and testing it like a synthetic or we call it a digital customer, it’s an agentic customer in each one of those countries and we’re testing from the outside in across that. carrier network to ensure each link in telecoms chain works. And if there’s any issues, then we’re pinpointing and stating to our customers where that issue has arisen. So we’re effectively like a persona sitting in each market. And when everything works… You’ve got a quality confidence metric. You’ve got the benchmark on performance. And when there’s issues, we’re simply telling our enterprise customers team to scramble to resolve it.

Kane Simms: So am I understanding this correctly then? If I caught, let’s say I’m on EE in the And if there’s any pinpointing and I call, for one of the better example, let’s say I call my bank, and my bank has

Liam Dunne: Well first of all BT will have to it depends where you’re calling from so they’re going to if you’re in the UK and that call center services or Philippines, for example, that call us be routed to the Philippines, then into the CCaaS provider, and then into the agentic AI What their link in that And we give them to see from the customers perspective in that local market. at the end destination. Because all of that routing, Routing, that changes based on so many permutations. The carrier can route calls based on time of day, based on data centre volume. The CCaaS provider is the same thing. As a data centre in London and Frankfurt and Dublin over here in Ireland, and depending on certain times of day, that routing can change. The same with the conversation AI provider. And remember, these guys are growing so fast. That change is based on so many permutations. We’re spinning up new data centre instances every week and month. and all of that adds complexity that changes in real time. But the customer should not be affected by those real-time changes, but they are. are and that’s why you have to provide the capability to test from the customer. We’ve got a Kane sitting in the UK and Kane’s persona is testing and validating that he can get through to that bank. up new data-center instances every that. That pharmaceutical company, and if you can’t, we’re saying don the dependency on disgruntled customers and stakeholders is clear. sticky and affecting your wider customer base.

Kane Simms: Right. So that call then that leaves my phone goes to the BT network, goes to the Philippines, goes to the CCaaS, Is it that BT network remains holding the call the whole time, or is it passed off and then that’s disconnected from that network now and then it becomes a Philippine network problem and then it gets

Liam Dunne: You know, it’s great, you know, because remember, BT will own, it’s like it’s so different to a country. They will own their network in that market. It physically has to traverse to the other country. And jump onto PTL or whoever it is in the Philippines and so on. And that’s in a very simple, basic scenario. If you’re a multinational with multilingual capabilities, with numbers all across the world, it adds, it’s like Inception. problem within a problem, and all this routing can change. All those four links, not just the carrier, but the CCaaS, the actual conversation AI, and the enterprise themselves, all of that routing can change in real time. And what happened was the backup mirror had not been updated. And as a result, the calls just literally changed from one time of the day. I think it was like between 12. experience was completely different because. one vendors down in the tech stack, down in the chain, had not done a mirror on this backup on their site. So there’s all of these elements that create the complexity. Theesides is knowing, when, and ultimately the challenge, I suppose, really is about, about making sure that your And my customers will always say to me, issues are not a challenge. Nobody likes that word intermittent, because it’s very hard to replicate, repeat, and remove. If you can replicate it, force find the issue, remove it. That’s where the best practice is in terms of all this area. And it’s funny because we move into this more cloud-based, The issues are still there. It’s just, moving him down the chain because I don’t have the data centres, but the carrier has the data centres, the CCaaS has the data centres, the conversation AI has the data centres. data centers, but your customer doesn’t care about that. Your customer is ringing, you’re toll free. They’re ringing 1-800-VUX. And when they get. They want Kane services to be up and running. CCaaS provider, agentic, carrier, whatever, causing the issue, they’ll blame you., So the important thing is that you as an enterprise, if you own the number, And when that’s going good you own that positive views you’re getting everywhere and when things go wrong you have to own that as well.

Kane Simms: Interesting. So what are the kind of things that you’re looking for when you’re doing that kind of testing then? Is it that you’re looking for calls dropping between one network to another? Are you looking for an impact on latency?

Liam Dunne: I would say like all of them, right? But that’s one simple view of just the technical component. And I think you articulated really well at the outset. When a business does deploy the business is deciding, okay? What that means is that the agent speaks for the business overall and what technical thinks looks good. There’s other teams that are involved in selecting or making the decision to deploy agentic AI and what looks good for them is different as well. So that technical is really important, the latency, the packet loss. The silence, um, the silence, all those elements that you’d expect, but other elements that we’re seeing coming into it as privacy, for example, whether the right to disclosure was given in a local market in that local language. I don’t know. Know what your Japanese is like, what can you tell when, if you’re looking at your transcript of a Japanese privacy statement was correctly played or the customer operations ask whether the problem was resolved. So the call successfully or been terminated to your AI and it obviously stating the correct disclosure statement. Was the problem resolved or was there security scenarios where a refund was incorrectly released and that they had no right to there’s, there’s more than one conversation, conversation, but there’s four different definitions of success, is what we’re seeing. And really what how we’ve come at this, Kane, is that we see us as kind of a we’re a business risk operating system for multinationals deploying multilingual, agentic conversation AI. So what we do? We give each department the ability to create evaluators and so that they can determine what success is like for each one of those departments. But from a real world perspective, and independent of all the providers and making sure that we provide the live risk evidence for each one of those. operating system for assurance but every team gets to own their own set of standards if that makes sense.

Kane Simms: And then, presumably it’s like the content, The contact holistically is your predominant kind of like user base, and then different teams within that contact centre will set things up slightly differently depending on what they care about, is that right?

Liam Dunne: Exactly, so like, you might have an engineer, and he’s all about… 40 reachability, audio quality, and so on. Okay, ultimately, the carrier leg is up, the CCaaS leg is up, you might have a privacy and data team, and they’ve got approved geographic disclosures and ways of handling information in local markets. to make sure that nothing authorized is disclosed. Then you’ve got legal and compliance. their job is to make sure that approved policy information requirements, standard, all of those adhere to the local. you’ve got operations, you’ve got financial and commercial. leg is Identity checks and resistance to control bypasses. That’s a huge thing. So as you try and barge your way through agentic AI, again, add the complexity of. Multilingual, multinational and you can see how businesses, it’s not just, can I technically deploy agentic AI, when I do deploy it, how do we mitigate those risks? identity And the big thing as well is being able to provide enterprises with a kind of one shared body of evidence. one clear ownership of every standard and then one true view end,, to end and by using a third party, not just like us, but anyone in this industry, what we’re doing is ensuring that all, all the providers are adhering and working correctly, but also them as an enterprise in terms of their requirements in each local market has been adhered to as well. So that’s where we’ve come in, you know.

Kane Simms: And is that more of a monitoring thing then or is that a testing thing? Because you make sure that certain legal things are happening certain notices are being read properly you’re abiding by GDPR AI act all this kind of stuff like that seems to me to be something that’s something that needs to be done on every call as opposed to necessarily something as well as perhaps something that needs to be done as you’re kind of building something, where does it live in terms of the life cycle of kind of an AI project? Is it, is it a testing thing? Is it a. is it a monitoring thing, is it both?

Liam Dunne: I think there’s kind of multiple layers to this. It depends on how the business looks at mitigating risk. You’ve kind of got your lab testing, your pre-production, shall we say, if we equate it to the old world. world. That’s validating that everything works before it’s deployed live on the TFN in country. country, and observability, I always struggle with that word, it has an important place capturing the issue live as it’s affecting your customers. With real-world testing, you have to actively challenge to deploy journey. And you’re, not just doing it before release to customers, you’re doing it throughout production, you’re doing it against each department standards so that you’re capturing in real-time. And you’re helping, again, all of our customers, what we’re seeing now is they’re, they’re using our test results in real-time to help that reinforcement learning. So what they’re doing is they’re taking those live results and whether they’re successful in a quality confidence metric or whether it’s an issue that we’ve captured that maybe, say there was an unauthorized, refund for example, they’re all been fed in real time into the conversational AI platform or ultimately the underlying LLM so that everything is learning. So I suppose what we’re to do with all of this here is a correct way of looking at this is that looking at them in an individual way is important. You’re going to have different stages of release, but there’s only one way to truly test both negative occurrences and the actual say happy paths as well and ensure that reinforcement learning is continuous and that’s true testing. So from our perspective, what we’re seeing is customers want both. But to truly train the LLM and the conversational AI, you have to test. So observability will capture, the crash has already happened. But what we’re doing is we’re effectively crash test dummies, and what we’re doing is effectively testing it and making sure that training and learning reinforcement learning is reinforced so that you as the end customer don’t become the crash test dummy, you

Kane Simms: That makes sense. One of the things I’ll put these I’ll put these links in the show notes, I was looking at the agentic assurance webpage that you have other things that you kind you kind of alluded to a little bit earlier on was about the kind of personas that are created that make kind of local calls in the respective market. I kind of, I understand that, but I think I Good for you to shed some light on this. I think I understand the idea of making the call from the local market because that’s where you’re going to actually test them end to end the reality of the thing. And we’ve seen lots of issues. In fact, I had a conversation, I think it was with Seamly AI, and we were discussing about latency issues and stuff like that, and all of these AI platforms, some of them at least, have a view of latency. So they’ll be like a little bar and it’ll be like, okay, what’s your latency? Estimated latency is like two seconds and then within that, you’ve got, this is made up of speech recognition and speech generation and models and this and the other. But that’s just what it’s like in either in the browser In the browser or in that link. Exactly. So it’s like when you actually get a call and you record the call the latency is miles away and you’re like what the hell is going on here?

Liam Dunne: The deviation that we’re seeing from what’s been reported in the lab versus the real world. That is actually significant. So we’re seeing like say latency shown as less than two seconds in the lab and within a CCaaS dashboard. And when that’s deployed live in country, we’re seeing if anything 20 seconds plus. Like, the impact is significant. And I suppose the highlight is really how important that is. A call that never reaches the conversation platform may leave no record in its dashboard. Now think of that. So your dashboard and your conversational AI, is showing everything is green. but your customer is sitting in 110-plus countries, if you’re a multinational, using all these different languages and could be having significant issues, but that dashboard is green. So a correct looking transcript may conceal a misheard digit or quite meek say may contain no examples of a vulnerable caller requesting an exception. An absence of alert is not even evidence for those scenarios. You know, you company’s customer experience. You have to dial in country. And another thing to add on for the audience to be aware of. of, if in particular if you’re using toll-free numbers, okay, if a toll-free number, a free phone number in Europe, you can’t ring that number unless you’re physically located in that market. So the free phone number that you’ll dial in the UK is different to the free phone number in Ireland. And I can’t ring yours and you can’t ring mine, okay? So the only way to test and validate that entry point is to have pops like we have within each country so you can generate the test call locally. And even if you don your number in the UK, it’s going to take a different path to you ringing it, because you’re dialing there. So again, whether you’re free phone or non free phone. The only way to be, absolutely clear that your customer can get you to your services is to be able to dial exactly as your customers do across fix the mobile with all the major carriers in that market. And that’s just os the first leg. Then to prove the conversation AI works, you have to be able to generate personas. So that’s just, it’s Kane in the UK, it’s Liam here in Ireland. And typically you will create a persona that matches the profile of your customer base. So if they’re typically dialing in London from BT or Vodafone or wherever it is, you’ll create a persona a London accent, background street noise, dialing again from within country and validate that persona depending on the use case, because obviously you have to give the context around what you want them to do within that persona itself. And then you’ve generate, create all these evaluators depending on with one single test that can dial across the full tech stack end-to-end and another thing as well that’s really important. It’s got to make that simple. Like with us, you can generate persona, set up your evaluators, you can do it all in minutes. You can be up and running globally within a few hours and testing and validating that your agent your agentic AI is working across all those major markets. And nobody else can provide, solve this for this problem in the way that we can do.

Kane Simms: The reason why I was kind of asking about the latency element is that, well I want to get back to personas and touch on some of what you touched on there, but I want to just wrap up on this latency thing first because let’s say that you are, let’s say that the platform that you use reports really great latency and you deploy it in the country that you deploy it in or the countries that you deploy it in, and then you realise actually the latency is really bad. I know we’re getting hung up on latency here, but I think it’s latency does damage conversations. And so let’s say that you identify that the latency is poor. What are your options to resolve that? Cause if it’s not sitting in the platform and it’s something to do with the network, have you got any levers that you can pull to affect any, any other thing or what?

Liam Dunne: I like that you’re doubling down on this, right? Because like, like we were talking about one dashboard from one provider can indicate everything is green. But when that customer dies in that local market, what we’re seeing is that the true in-country experience of that customer can be vastly different. First thing is if you don’t measure, you can’t know. Yeah. So you have to measure that customer side things. And then what you need is you want one true view so you can leave with all your providers. So that means you need one single test. What we use in our world is the CDRs, the call detail records. So that’s a trace that went into my CCaaS provider when I’m speaking to my agentic AI provider or when I’m speaking to my carrier, they have to be able to trace these tests or results within typically 24 to 48 hours or disappear from the system logs. Because you can imagine a carrier has hundreds of thousands of customers, millions of calls logs, the CCaaS providers are the same, the agentic conversation AI voice providers are the exact same as well. So you’re able to give them the information They can trace it internally, because it’s not a game of you versus them. They want to resolve these issues, but they need you to help them. And the only way to do that is to be able to give them multiple CDRs across multiple carriers and help them isolate the issues that they can resolve. So you’re able to take that one single view and share that with your respective providers to help them see which link is causing that and ultimately improve it. Because remember, we’re generating these test calls locally there’s the CLIs or the ANI’s, you can see them on every test. So when we’re reporting and we have a whole managed service around this as well, not to keep bringing it back to Klearcom, but we have a managed service on this, Kane, where we can actually manage this on behalf of our customers. So we’re like an outsourced NOC. So we’re not just testing in an operating system. We can do all, well, we do all the triage so you don’t have to, but then we can liaise with the respective providers directly. But you have to do it in a collaborative way. It has to be genuinely simple for them to trace on their system logs. And then once you do multiple tests over multiple day parts and help isolate when this is typically happening, that’s when you can affect change. So it is. But 100%, we see all of the latency and all of those issues, like silence in the line, a huge one. So silence in the line is an indicator for us that some API call hasn’t worked. You know, your call has been answered successfully. The carrier has done their part. agentic AI kicks in, but say you’re at that stage of giving an account number or some security information, and suddenly silence kicks in there. Oh, that’s when customers just freak out and start hanging up, because I think that’s over two seconds, pretty much. We’re just waiting for that. Do you know? So, and that’s going to become more part, we’re, there’s a rush to deploy agentic AI everywhere. Ultimately it’s going to depend on the pipes to deliver that computing capability. So it’s going to deploy, it’s going to, it’s delivery is dependent on the underlying service there. And that’s why the likes of us exist, because if you think about the, the, what’s involved in that stack, that delivery stack. you’ve got the models like your GPTs, you’ve got the AI applications, you’ve got your CCaaS, your voice, you’ve got the carriers. And because that data centric topography, you need AI assurance and that’s where we can help our customers de-risk the deployment across the world.

Kane Simms: And what if, I mean, the challenge with all of this, by the way, you’re preaching to the choir with all of this kind of stuff. The challenge, I suppose, is to get your thoughts on terms of what you’re hearing from customers, is that I don’t think that. There is a proper appreciation of the importance of testing and validating these probabilistic technologies. And then you’ve got the additional challenge of trying to get people’s heads feeds out of the platform, the AI platform, and trying to help them understand that this conversation is going to take place in the world in a broader environment with lots of different moving parts. So, the kind of, what I see typically with business is, we’re not just with voice AI, Is that there is a big pressure to just release them, just get them out there. So it’s not maybe they know that they should be perhaps doing more when it comes to testing, but it seems to be something that I often observe being skipped. Do you see the same thing? and what’s your advice to companies that are in that situation where they’re under pressure to get something out the door and they’re struggling about how do we apply resources for testing when we’ve got to build this thing and all that kind of stuff like what’s your thoughts on that?

Liam Dunne: From the multinational perspective what I see is there’s a race to deploy some in conversation AI in typically two markets and typically starting off in like North-American or UK or an English speaking market. And that’s just to get to the start line. And then what’s happening is there’s a pause because after getting to the start line, the real enterprises are realizing that there’s a significant complexities about deploying globally at scale in a non-English world. And that’s where we’re seeing actually a flip. So up to that point, up to the old world, I think testing is seen as a nice to have. I think now it’s been seen as a mandatory to deploy at scale globally. So while there’s a race to just start and to kind of ease the pressure from the board to be able to say, we started on this and we’ve got two call flows, which are low value call flows with not necessarily frontline, but it’s been deployed. And what they’re discovering is that the QA process manual and so cumbersome in just that simple example, to deploy that globally is a much more complex thing. So we have a very large retail, retail customer who did that got into one market, realized the complexities and needed a way to systematically programmatically de-risk that deployment globally. And actually we were told in our early access days, as we were AB testing a lot of this with our customer base, we were actually told we need to speed up ourselves as a service provider because they can’t roll out because we hadn’t rolled out at the time. So actually I see there’s a huge shift now from getting to the start line, which is saying I’m using some conversation AI in low value capacity to actually deploying it at scale. It’s a different world.

Kane Simms: And it’s only getting bigger. I think you mentioned at the very beginning of the call, I’ll have to try and dig out the study that the study which surprised me in that the adoption of voice AI agents was actually frighteningly low I thought it was going to be like miles bigger than it currently is because that’s all I’ve been doing for the last eight years so you’ve been doing for the last however long so there’s enough of a market there but the point of this piece of research was saying, look, this is so early and the interest over the course of 2026 has been so much that, I think it might have been Gartner, they’re forecasting like the rise in adoption is gonna be going through the roof over the next kind of few years, which I can completely see. But I’m wondering if, you know, what’s your perspective on where we are now, where we’re going, what does the future look like.

Liam Dunne: Yeah, I think when we look at now in terms of that bell curve of adoption, we’re at the very bottom. I don’t think even we’re at the bottom. the soft indicators, customer queries, inbounds, that type of thing from even just us as a business. I speak to all my peers all across the world, whether they are competitors or adjacent businesses. We work a lot with the carrier world as well. We can test every single voice conversation AI provider in the world. So it’s small, you know, this game, we’re in a small world. It’s about to get a lot bigger next year. We’re going to start with the large enterprise adoption curve. Right. And then what’s going to happen is it’s going to that innovation is going to move to the core. We’re going to see a whole spread of mid-market adoption. And as the everybody looks up to the large enterprises and if they’re doing it well, how can it deploy mid-market? And we’re going to see this kind of natural, cyclical approach to adoption of any technology. I think the next three to five years, it’s going to be a systematic programmatic approach to moving away from IVRs because the savings I have a one customer who’s saving 20 million on called call by moving to conversation. And that’s just the phone bill. Nothing else. You could imagine the cost savings everywhere else, not just in terms of human capital, but all the other elements of the business and training, a support and all those things. The compound effect is so significant. The benefits are so significant. But what from the customer side as well. They are so happy that we don’t have to wait and cue like look at Spain. Spain are bringing in their own legislation where nothing more than three minutes in terms of call wait time. So you have to dial back in. Look at everything I’m talking about here. Look at the other headwinds. I’ve talked about soft indicators from us as a business, but look at the headwinds. One of the massive ones is going to be AI regulation. All how that’s coming to the fore now in the next 24 months. Look at what’s happening in California, what’s happening in New York versus happening in the EU. Even not even in the EU as a whole, the individual countries, APAC, there’s so many legislations that are going to drive the need for third party compliance and an auditory. We have another customer in the pharma world, right, who have asked, can we store results for a minimum 25 years? Because it’s a particular oncology drug that when customers deal or engage with that particular voice box, we have to be able to provide those test results and store them for a minimum of 25 years. And that’s just one element. You imagine all the different industries when the AI acts kick in what dependencies and third party audits are going to drive in all of this, hugely exciting. We’re just that we’re not at the start line yet, we’re only we’re coming up, we’re in the blocks. We’re about to get to the start line, 2027 is where we hit go.

Kane Simms: Nice. And it makes me think, you know, a little bit about, we’re at the very beginning, it seems, even though I always say this, and it always seems weird to say, because, you know, I’ve been working with voice AI for, you know, nine years almost, and it feels to me as though it’s obvious that the writing has been on the wall this whole time and I’m, like, What’s taking us so long?

Liam Dunne: You and I were in this bubble of, why isn’t it going faster? Why aren’t they moving more? It was the probabilistic nature on what LLMs can truly discern on themselves. And the fascinating thing in all of this is that there’s only so much we know. human. I hand you a script and Kane has to go and learn that. I don’t know how Kane learns that, the LLM is no different. But I can test and validate that you have learned. So a lot of the characteristics of the human experience as call center agents are being transferred to the LLMs. We still have to test and validate because you can have good days and bad days on the phone. I certainly did. There was days where I was answering fast. There was days when I was hanging up. I probably should admit that. But anyway, it happened to the odd time. But all of that’s happening now in the agentic AI world. The conversation AI bots are hanging up, as well. You have to test and validate. You have to reinforcement learning. If those real time alerts to discern who hung up, was it you as the end? or was it the customer or was it the agentic bot? All of those characteristics play out in LLM, no different to a human and we have to test and validate. And it’s just, there’s so- growing at scale and the fact that multilingual, I. I think the big difference in the last year has been the multilingual capability The fact that we’re able to step outside of North American English, it means we’ve got true global scalability. And that was probably a factor as well in terms of when I see the adoption, like customers race to A, B test as far as English. But if I want to truly adopt agentic AI, I need to be able to do in the global scale to get the global benefits. And that’s where 2027 is going to be all about.

Kane Simms: What about kind of, I know it’s hard to, it’s hard to pontificate beyond that. But I can see a world where, I’ve wrote about this recently on my Substack, which is all about what I’ve called the people in the middle, which is that what AI is incredibly good at is take the grunt work and the mechanical elements out of process. And so really, if I look at the way that I use Grok Bot, we run a lot of the kind of marketing and content side of things all through Grok Bot. And it takes away so much of the mechanics that it’s all the stuff that you realize you used to spend a lot of time on, but it’s just kind of like a thankless tasks. All that really matters, for example, is this conversation we’re having, the insights and getting these insights in front of people that would find them interesting. So the creation of the insight is important, the getting it in front of the people that matter is important, but everything else in the middle… is just mechanics and AI is so good at the mechanics and I’m just using a very simple example here you have content marketing but how many businesses in the world do content marketing if you can do content marketing then what else can it do It’s just that we essentially just a series of people fulfilling processes, but AI essentially can take the mechanics out of the process and therefore the people are not needed in the process and I can entirely see a world where the contact center as we know it really doesn’t need to exist because the mechanics of the process can be figured out by AI. And as long as the input is sound and the output’s got some kind of validation require significantly less people. And then if you’re going down that route, then…

Liam Dunne: Yeah, which is a serious rabbit hole. And there’s much bigger implications than that.

Kane Simms: But let’s just say that we’re on that sort of path. Then you also have to ask yourself the question of, well, what is the infrastructure that all of this stuff exists on? And Is it telephony infrastructure and contact centers or is it internet infrastructure and AI agents? Does that make sense? What I’m asking is,

Liam Dunne: The CCaaS world over the last number of years. A lot of them have been eating up each other. There’s no doubt the same is going to happen with conversation AI. Then we’re going to see probably a blending of CCaaS with conversation AI. We’re already seeing CCaaS and CRM blending. So what we’re seeing is from the public perspective, we’re seeing companies merge, But underneath that tech stack, there still is data-centered topography, there’s still call routing, there’s still complexity in terms of my, I suppose, my need to be resolved. A call, a connected call to business can still fail from my personal outcome, because I didn’t get my call resolved. But I do think we’re going to see a natural flattening of the constituent components that make that up. but even before that you’re moving from PSTN to SIP, moving from on-prem to the cloud. Naturally, it flattens the amount of links, the amount of components. So we’re naturally going to see all of that. but I do see that we’re going to, from a voice perspective, it’s going to become more ubiquitous. It ain’t going to be just on a phone and dialing a number. It’s going to be within the apps. it’s going to be within wherever the sits and wherever you are as an enterprise, what’s as friction as possible for the customers. And AI, you know, that was going to speed that up. And God knows where that’s going to go. Okay. That’s for another day. That’s for a couple of points.

Kane Simms: Absolutely. And we’re already seeing exactly what you described there. You know, even in the last two weeks, you’ve got, you know, Five9 acquiring Level AI, Salesforce acquiring Cresta before that it was a thing. You’ve got all this stuff happening where CRM providers, CCaaS providers, before that it was nice and Cognigy, then you’ve got Automation Anywhere acquiring Boost.ai, all of this consolidation is happening to a point where I think it all kind of ends up in some kind of like, I don’t know, if you want to call it a customer experience management platform for whatever better phrase, which is CRM, CMS. You know. It’s not called central by itself.

Liam Dunne: It’s like, it’s a way of working. It’s an operating system. I see it as a, it’s more, it’s a customer focused operating system. There’s a big difference there because the operating systems that previously existed based on the technology that was available at the time. But now that technology has caught up, we’re actually putting the customer first, and how I as a customer want to engage with you as a business. It’s not dependent on your tech stack. It’s dependent on how I want to engage with you. And that’s why things like value, in terms of the customer, ultimately, you can’t rely on disgruntled customers and stakeholders to be informing you as an and I think we’re there actually where poor experience, I don’t even want to say customer experience, just poor experience will not be tolerated. It means we want instant value and instant positive outcome. And anything that helps the enterprise deploy that, train, highlight and relay real-time issues, it’s what’s important for the next number of years for the market. So they get as frictionless as possible, you know.

Kane Simms: Brilliant. Liam, this has been an absolute pleasure. Really, really good stuff. I’ll put the agentic assurance links into the show notes. I’ll stick your LinkedIn in there as well. klearcom.com for those of you that want to jump there right now. K-L-E-A-R-C-O-M.com. And yeah, thank you so much. It’s been an

Liam Dunne: Love this. Hope to see you again sometime.

Kane Simms: Absolutely. Nice one. Appreciate it. Thank you all for tuning in, and we’ll see you again Bye.

Share

A customer's AI agent just called. Now what?

This research looks at how businesses are responding to personal AI agents.

Take the 5-minute survey

Everyone who takes part gets first access to the results

Weekly newsletter

The latest in AI-powered customer experience. Make better strategic decisions with the help of our weekly newsletter.

Host

Kane Simms

A strategic AI advisor who, for the past decade, has helped business leaders and product owners transform customer experience using conversational and generative AI.

Share

✓   Link copied

A customer's AI agent just called. Now what?

This research looks at how businesses are responding to personal AI agents.

Take the 5-minute survey

Everyone who takes part gets first access to the results

Weekly newsletter

The latest in AI-powered customer experience. Make better strategic decisions with the help of our weekly newsletter.

Top articles and podcasts

Related content

Brands are split on personal AI agents. Where does yours stand?
Personal AI agents can now phone businesses and pay on a customer's behalf, but some brands are already blocking them. I'm running research to find out where businesses stand.
AI is stripping brand value: Matt Clare (UJET)
Matt Clare, VP Product Marketing at UJET, joins me to explore what happens when your customer's AI agent is the one calling, and why AI is stripping away the brand and experience value businesses have relied on to stand out.
How Sling TV’s AI agent converts 25% of sales conversations
Sling TV's AI agent converts nearly 25% of sales conversations and the team behind it shared how it grew from answering simple questions to selling at scale.
24 reasons why giving your chatbot a voice isn’t as simple as it sounds
Teams giving their chatbot a voice soon find that time, attention, latency, messy language and handoffs change the whole design job.

AI Breakfast: Keeping Control of Enterprise AI Agents. London. 26th November.

Meet VUX at CCW Europe, Amsterdam, October 5-7

Register now: Why your contact centre playbook is obsolete