Episode 110 · 17 Nov 2026

What if your contact center became a product team?

Summary

Simplyhealth has been a PolyAI customer since March 2023, starting with a fairly transactional voice use case: resolving FAQs, about 800 calls a week. Three years later, the deployment covers voice, in-app, email, chat, and WhatsApp, and the team driving it no longer reports into a services function. They report to the CTO.

In this episode of Deep Learning with PolyAI, Nikola Mrkšić sits down with Paul Atkins, Simplyhealth's Head of Business Optimisation, to talk about what changed in between. Paul's team moved from buying automation to building their own capability: conversation design, analytics, root cause analysis, journey redesign. The partnership has flipped along the way. Simplyhealth now comes to PolyAI with product requests, instead of waiting to be told what's possible.

Together, Nikola and Paul explore:

  • How Simplyhealth grew from an FAQ voice agent to a CX platform across voice, in-app, email, chat, and WhatsApp
  • Why the team moved from buying automation to building internal capability, and why it now reports to the CTO
  • How Wren, PolyAI's tool for reviewing real calls and recommending fixes to an agent, analyzed repeat calls and identified how to fix the root cause
  • How an internal hackathon repurposed an existing prompt to build a working agent for a different part of the business in one afternoon
  • What's next on the roadmap: a healthcare concierge, WhatsApp for B2B sales, and MCP integrations

Watch the full episode to hear why Paul thinks the operating model matters more than the 30 seconds saved.

Key takeaways

  • Start from adjacent skills, not software engineering: Paul's advice to CX leaders is that advisors don't need to become software engineers. Build on what they already have (conversation design, QA, customer insight, root cause analysis, journey improvement), then add technology skills and give them the freedom and tooling to experiment. Many of his team are now working through an AI apprenticeship built around real Simplyhealth use cases.
  • Repeat contact, explained on day one: Combining Wren with agent memory, Simplyhealth asked why customers were calling back. On day one it found 80 of 550 conversations, around 14%, were repeat callers, and explained why in the context of each customer's lifecycle and products, using the deployment's API integrations, instead of weeks of manual mining and validation.
  • A working agent in one afternoon: At a technology team hackathon, Paul's team repurposed the ID&V prompting from Simplyhealth's health plan agent, which achieves 85 to 90% success, for Denplan's dental practice support line, where ID&V takes around 30 seconds per call. The agent passed QA and was scheduled to deploy the following week.
  • From service function to product partner: Moving the team into technology, reporting to the CTO, removed constraints on how fast it can deliver. It now co-designs experiences with product teams, from a healthcare concierge in Simplyhealth's apps to WhatsApp for B2B sales, and brings product requests to PolyAI rather than waiting to be told what's possible.

Transcript

[00:00:00] Paul Atkins: You don't need to tell your advisors that they need to become software engineers. Right? You can start with like adjacent capabilities they already have, like conversation, design knowledge, qa, customer insight, root cause analysis, journey improvement, and then add the technology skills around those strengths and allow them the, the freedom and the tooling to be able to try, experiment, learn and support them in that way. And as we, you know, as we've learned ourselves and we've learned in our leadership team here at Simply Health, that the results can be incred foreign.

[00:00:41] Nikola Mrkšić: Hi everyone. Welcome to another episode of Deep Learning with Poly AI. In this one we try to help skip leaders get a window into the latest and greatest developments in AI and automation. Before we start reminder to you know, like share and subscribe. And today I have the privilege of hosting Paul Atkins, who is the head of Business optimization at Simply Help, longstanding client of ours and he spent the last three years building one of the most impressive dialogue AI deployments that we've ever had. You know, I think we started off on a very transactional use case basis. Now it's grown into a great partnership, into something much bigger, into a change how teams run. So I kind of maybe want to start there and then we can work through how it all happens. So Paul, thank you, thank you for being here. It's great to have you on.

[00:01:29] Paul Atkins: Thank you very much. Hello everyone. Yes, it's been a great journey. Right. I think we started off 2023, I want to say March 2023, something like that. And partnership with Polyair really started in the voice channel, as many have and will. And I think we started really small with some kind of transactional use cases around resolving AQs and that kind of thing. And I think since post launch we quite quickly got into building out those FAQs, understanding how it worked and more importantly understanding customer journeys. And we were into resolving around 800 calls a week, which is a decent chunk of what we had. And then since then, yeah, we've, we've kind of evolved to where we are now, which is, which is using all the things you have and helping, helping you, helping you help us dive into new channels like in app and email responses and all chat as well. So we are, yes, we are. We've had quite the journey. So thank you for having me.

[00:02:29] Nikola Mrkšić: Yeah, no, no, absolutely. It's great, it's great to have you on and look, I mean I think that like what's exciting here as you kind of like start, you know, with like a small thing and then it builds and builds while you see the whole technology stack get rewritten and then like new tools come in. You know, I think that the traditional contact center and even like the modern one is a difficult place. Right. I think that you're kind of like a firefighter without a fire hose. You know, like what I've kind of learned at least is that for the most part you're worrying about whether you're going to have enough people. Then if you somehow solve that problem, then you're worried about whether you've ramped them up and onboarded them properly. Right. And only then do you maybe get to kind of like, you know, look at the things they're using and you know, the most urgent things would kind of like get sorted out as you go. But like everything else was just kind of like left in a conceptual status quo. Whereas I kind of feel like now as we bring AI labor into the whole thing to do much of the tier one work, it finally allows people to step back and kind of go like, all right, what are we really doing? There is observability. There's just the chance to actually revamp the process to be a bit more of a product team. And in theory it was always supposed to be that, but I think it was just know you would spend most of the time ensuring that there is obedience with your process that probably wasn't even optimal to begin with and you would rely on humans to do the rational thing when it's not. But anyways, tell me a bit about that. And you know, I've much already. I think I'm, I think for the audience it's much more interesting to hear kind of like how you looked at it when you started and then like what the work looks like today.

[00:04:08] Paul Atkins: Yeah, I think the real story for us isn't that we kind of installed a voice, but I think conversational AI has changed how we think about certain things. Service I would say so we've moved from sort of buying automation to developing internal capabilities with people who can't analyze conversations like redesign journeys, build knowledge test changes and progressively extend that intelligence across, across channels ultimately. So we haven't really, we haven't mainly viewed AI simply as like a headcount based exercise. What's changed is the nature of that work. I would say so as more routine demand can be resolved through, through kind of or AI solutions are people increasingly are starting to focus on conversation, design, knowledge analytics, testing, root cause, continuous improvement. So we're no longer sort of operating a service. Increasingly what's happening in our organization is the people closest to the customer are helping to shape and improve the technology behind that service and dynamically shape our customer journeys. I think for an organization like Simply Health, which is twice as old as the NHS in the UK, it's 150 plus years old and we have a mission to help people in the UK get health care when they need it, as quickly as they need it, and support our NHS in doing that. I think kind of with that mission in mind, we've started to adopt more of a product ownership based approach in which we partner with our product teams. Our products and services from a digital perspective are moving, you know, as quick as, as quick as they ever have been. And what we're doing now is helping architect the experiences and design the experiences that sit behind that so we can keep pace with the, with the product development that's happening over here. Right. And I think that's been the real change and shift change for once since we started the partnership with Poly. It's been from solving service use cases to now being an integral part of our product development life cycles. Right. And evolution ultimately.

[00:06:04] Nikola Mrkšić: Yeah. And I think that in many tech companies you see the same thing, especially in these forward deployed motions where you get this platform builders and then you have people who are actually on the front lines doing it. And I think that at least in customer service for the longest of times, it was so hard to keep the front line to get it to hold that it was just so hard to get any information back. And it's kind of like the paradox of voice of the customer programs costing companies millions while you have hundreds, if not thousands, thousands of people speaking with your customers every day. Right. So how do you see that kind of gap being filled? Is it being filled? Do you feel like there's finally good signal coming back from the contact center into the product?

[00:06:51] Paul Atkins: Yes and no. I think it's improving as we understand this new world and what it can give us and how we deliver that information back into the product evolution life cycle. I think there are still large gaps between staying in the transactional, being metric, focused around resolution, contain whatever you want to call it, and service level agreements on a B2B side of things. I think there's still a huge focus transactionally and in the service sense at that part of the experience that your organization offers. And I think there is still a gap between kind of being able to step back from that and understand what a journey looks like and what the root causes, upstream and downstream impacts are in that journey and being able to then co architect that Use those, build those epics, use cases and work with your product team to almost fold the service wrap into the overall product design experience. I think there's still a gap between those two things occurring, but I think it's getting closer and closer. We work with Edge Tier for a lot of our insights and analytics from a conversational perspective and we use a lot of that data alongside what we get through analyzing our voice interactions with Polly and Wren to help build out those, those use cases and cases for change and transformation, but also to help us continually and dynamically improve the customer journeys that, that support though those experiences that the, you know, the interactions give us feedback about.

[00:08:23] Nikola Mrkšić: I mean, like you mentioned, I think that that's been one of the most exciting developments for me and that at least maybe for the audience. Traditionally, you know, the business side is the business side and they own kind of like the procedures, the operating procedures, the sorts of truth. But then, you know, when you wanted to implement even like an old school dtmf, IBR or anything else, you'd kind of go to it, go like, well, I would like this, right?

[00:08:47] Paul Atkins: Yes.

[00:08:47] Nikola Mrkšić: And I think that in the early days, conversational AI and kind of like, you know, when we started our partnership, we were really still bridging that gap with forward deploy teams where we would come in with our deployment strats and work with you almost as a mercenary army on loan to be your second IT team so that we almost circumvent the traditional enterprise kind of need for like, okay, we want this budget approved next year. Work gets done. Oh, we didn't scope it, right. We need a bit more. We don't have enough budget. So that's, I think, where a lot of this was stuck. Historically, I think the forward deployment at least allowed for a highly motivated group of people on our end to work hand in hand with you. And for large volumes like yours, that made sense. Right? But I think one thing that I've recently been kind of just repeating ad nauseam is when you have a strong partnership like we had, well, the working theory, if you know, the whole 10,000 hours to get good at just about anything. My hypothesis is that a good forward deploy team that is very strongly aligned with the customer can probably do about 3,000 of them. Right? And the first 3,000 are probably, you know, they get you half of the way there and it can be very useful, right? It gets like decent resolution. It can be like a very productive application. Right. But then kind of like as you really work to make it phenomenal, no amount of Motivated external third party will know care, get in as deep with your business as you can. You know, we have like some behemoth deployments where people have worked for, you know, Fortune 50 companies for like three, four years. You know, I joke with our champions there that they're basically like not working for us, they're working for them. That's fun because, you know, if someone joins Polya out of university, they pretty much just worked for that company their whole life. Right. But no matter what, you don't have the authority to then make some of those decisions. Right. And they're not able to just kind of like connect inside the organization. So I think to do the full 10,000, you just have to put the tool in the hands of those that are empowered, that know how to get the data, cross functional agreement of those things. But how have you found that whole experience where, you know, we went from us doing most of the work to us doing all the

[00:11:11] Paul Atkins: stonework? Enlightening. Right. I think it's been, and it's been really interesting in terms of the dynamics of a, of a partnership. Right. It's not, it's not been like your traditional deployment partnership that you might get with other organizations or you know, indeed a third party deployment partnership. I think it's been really interesting that kind of. My team specifically actually have grown in terms of skill and knowledge and using the platform, the software quite drastically over that time since we started when we heavily relied upon upon the teams at Poly AI and I think now it's almost flipped on its head. We're coming to you guys saying, hey, can we do this? Have you got something that can do this? You know, how do you think the product can flex to what we want to do? We want to look at an app, we want to look at email responses and stuff. How can we push the product to, to meet our business demands, but hopefully provide you some product insight as well. Right. And some avenues for product evolution as well. So it's been quite symbiotic in that sense, I would say in that there's been winners all around the camp. Right. I think in terms of how we've managed to get great value out of the team, improve our skills using the software, solve real time business cases on a large scale. Right. Deliver value back into the organization as well as hopefully help the evolution of Polyar as a product as well, and help inform that and give some real user experience of what the functionalities and various elements can bring in the real world. And I think to your point on Ren, that's been a bit of a game changer for us. Right. It's dramatically for us, reduced the distance between customer conversation and actionable insight. So things that you might have spent hours manually reviewing. And that's, you know, that has been the case. People spend less time looking for things, less time building and checking things in the customer journey within the platform itself, and much more time now thinking about actually how we are strategically building these, these customer experiences. Ultimately, a really good recent example, we combined REM with agent memory and asked it to analyze repeat contact for us. A question you're going to get asked a million times by your operational leadership. Right. Why am I getting repeat contact? What is it? Is it changing? And on day one, it identified that kind of 80 of the 550 conversations we had, around 14% were repeat callers. And the important thing was it didn't just give us that number, it was starting to tell us why those people were coming back in the context of their. Because we've got some good API integrations now, right. So in the context of their experience, their customer lifecycle, what the products they have and all that kind of stuff. And yeah, it was, it was brilliant to be able to get that rather than having to put all the legwork into, you know, mining that information out, guesswork, validate with quality qualitative information, all that kind of stuff. Right. It was, it was there. And so the, the life of a team like mine, which is transformation and support based, has been changed dramatically by this, by this tooling. Right. It allows us to be able to answer those things way, way quicker than we previously were. So, yeah, and now we're using obviously Ren within the platform itself to, as I said, I gave you an example earlier of how we kind of hacked together a. We did a hackathon in our technology team and we spent an afternoon building out a new agent for sales support teams and the whole team got involved, did it looked at the FAQs, looked at the journey, looked at the systems, looked at the contact data. And then we used Ren and we built, we built an agent and we're going to deploy it next week. And we did that, you know, as a team, as a group bonding exercise, but also, you know, it served a practical purpose and it solved the business problem as well. Right. In the space of a few hours. So, yeah, incredible.

[00:15:02] Nikola Mrkšić: I mean, I think like Ren has been just like an absolute, like, you know, lightning in a teacup moment for us where, you know, as we kind of like had like our previous tool, Smart Analyst, which was like A good, I think, analytical tool. And, you know, it was used, but, you know, it was just one part of the platform. There was a point where, you know, as coding agents started becoming sufficiently good that we allowed it to do more and more. And then at one point I realized that with some of the beta customers that had it, there were a few people that were sending 2,3000 messages per month back and forth. And I think in that whole, like, technological leap, like the CX people became the builders because it stopped being about justifying the effort so that other people can go do the work, get the data back. Because those things I feel were like if you were on a roll, if one thing worked and maybe you got to ask for another and maybe another, but the cost of it regardless was quite high. Right. You would have to go and just do the work, listen to the calls. It was hard. And listening to calls, whether it's closed between humans or between AI, my working theory is like, if you can do 50 a day, you're like an absolute tier one hero. Right? It's boring. It gets really boring. Right. So no human being can do what AI can in terms of just surveying them all. But tell me a bit about that transition of the team from service to tech. I'm not really sure if it's service or tech. To me, it's just really that whole combined effort. But

[00:16:31] Paul Atkins: yeah,

[00:16:31] Nikola Mrkšić: yeah.

[00:16:32] Paul Atkins: And the role. The role is a hybrid role for all intents and purposes. Right. I think organizations will have different thoughts on where they place a team like mine. And it can be in service, it can be in technology, it can be in a transformational unit of some description. But I think where it really started for us was with the expertise already in the team. So I had people that had worked in the service center and people that were customer experience specialists, but had really strong organizational knowledge as well because of their. Because of their tenure that had also had some great predisposition to be able to work with technology, interest in technology, at an interest in automation, stuff like rpa, and just had a real interest. So it kind of. We created a group of those people ultimately that were like journey managers, customer experience experts, CX analysts, and then started to kind of put real problems to them around the customer experience. So how do we fix these journeys? What do we, you know, what can we build to solve some of these business problems? And then I think what evolved over the time was a real specialism for both being a journey architect or CX expert, but also being able. So, for example, a lot of my Team are going through their AI apprenticeship now with company called Cambridge Sparks. So they're kind of AI qualifications where they get into prompt engineering, have to use a real life practical example within the business. And obviously we've got many, lots of them are centered around the use of Poly AI. And so really kind of it's about getting that balance right and using what exists within the organization and then sprinkling in the expertise and tech know how in and around that to round out the team. And that has happened. It happened relatively organically. But when we realized it was happening, we wanted to then accelerate it and use it as a real USP for the team. And the results have been incredible. Right. I think we've managed to build out and deliver more transformation than most other parts of the business have in a relatively short space of time. And that's been recognized within the business and we've kind of been moved closer now to the teams that can help enable us in a speedier way. So we've moved into technology. I now report to the cto Tim, and that's really to take any of the restraints off the team and how quickly they can deliver optimization back into the business using tools like Poly as kind of like our headline game changing tool. And that has then opened up the doors for these evolutionary conversations about our use of PolyAI from being a voice channel solution into okay, how can we use it within the marketing process and customer engagement lifecycle, how can we use it within the product experience in our applications, how can we use it in terms of its integration with our financial systems and then use it to almost get into some conversations around MCP now, like deeper integrations around how we might be able to kind of have Poly in the box for some of our, some of our systems. So we're getting the conversations really quickly, you know, exploded into a fest of the business saying, oh, we've thought this would be really interesting. We thought this would be really interesting. It's kind of like, okay, we need to kind of manage this a little bit. But it's really, really exciting. Really exciting.

[00:20:03] Nikola Mrkšić: Look, I mean I think it's like the most exciting era to work on anything that is like technology adjacent. And I think like what I've gotten a lot of personal pleasure from is, you know, through our early years as we work with contact center teams, you know, there was always this like thought of like, hey, we are creating more interesting careers for people orchestrating it. But then it was also like, you know, what will happen to the headcount? That was always like in the back of our minds. But the truth is like the work was never really getting done fully and like the Jevons paradox, like we're just insatiable as humanity. We want more of everything, right? So you just get to build like a bad thing with it. But as I look to just like you know, can like the next COO come from like a contact center? I think like you know the most AI pilled kids of today will be like revising through the orgs fastest and I think that is the areas where there is enough data for them to do incredible things that will produce the next like leaders. And I think finally now in the contact center this is now where you know, you have someone, you know, 22 year old using Wren, just you know, sending 2, 3000 messages back and forth. And you know when I look at cloud code usage even in our engineering teams like in terms of AI pilling and learning, I think some of our customers, I think like when we were preparing for this, I checked her dashboard. Amy Corcoran from your team is I think either number seven or number three in our entire customer base. And just like voracious consumption of the tool, like you know, using it to make changes and iterate it is just like so fun and like the effort is so much lower. So then you can actually do all that you ever wanted to, right?

[00:21:39] Paul Atkins: You can experiment, right. And you can try things and you can learn through that, that process. And I think I remember being a business analyst years ago, too long ago, decades and, and learning how to write Sass, SQL, spss and the most, the best way I got to learn all of that was by, by trying and doing and failing and learning and stuff. And I think this is, this is where kind of the kind of more low code, no code solutions at the front end of your platform are really appealing to those people that have, that have that kind of attitude and ambition as well to try those things. And I think you're right, it offers opportunity. And I would say kind of my advice to CX leaders would be to kind of, you don't need to tell your advisors that they need to become software engineers, right? You can start with like adjacent capabilities they already have like conversation, design knowledge, qa, customer insight, root cause analysis, journey improvement and then add the technology school skills around those strengths and allow them the, the freedom and the tooling to be able to try, experiment, learn and support them in that way. And as we, you know, as we've learned ourselves and we've learned in our leadership team here at Simply Health that the results can be incredible. If you can do that and if you can do that organically, even better.

[00:23:02] Nikola Mrkšić: Can you, can you tell us a bit about that? Just kind of like, you know, how, how did those evolve? How did you decide on the roadmap around channels and like expanding the capabilities?

[00:23:11] Paul Atkins: Yeah, I think it's really interesting. So yeah, I think as I alluded to earlier, we kind of started out in the boys channel, right? And then we, I think, and this is kudos to Polyai I think because our partnership's been so strong, we've achieved some great results and, and kind of partnership and deployment team has been brilliant in helping us identify those use cases. It was always inevitably going to raise the question of okay, well how do we go faster? The more time we spent with the product, the more we learned about how it works. And then, you know, subsequently our migration to the Jupiter platform and use of, you know, use of some of the more enhanced tooling and no code solutions kind of have fed into that desire of well, we could do this, right? And it's. Or we, we could do this. So one of our ambitions, you know, kind of web, our web and phone applications is to have a healthcare concierge. This is a product design thinking. This is something that helps people answer real world questions rather than just giving them a product carousel and kind of letting them choose and, and have their own, you know, leaving them to their own devices. This is more about surfacing answers to people that have questions and in a, at a point of need. Right. And so when we kind of started to learn from product that that was the product design ambition and they wanted to do some testing and build that out. My team immediately, well, we have some of these capabilities with a Poly AI platform, right? How about we bring those to bear to that, you know, to that product design thinking and look at how we can build something. Poly AI is here. It's our platform, it's, it's on a state, it's the capability is here. We can build, we can experiment, we can a B test, we can auto qa, we can do all of this, the stuff that means quick deployment, all the things product teams love to hear, right? And so immediately I had that first conversation with one of my peers, our head of health plan product and he was incredibly interested, as you'd expect. He was kind of like, okay, let's talk about this some more. Let's understand kind of how we can do that and do we want an SDK? Do we want to go headless? What do we want to do in terms of how we get this functionality over? And we're having that conversation right now with yourselves and with our product team. And that's just one example. Right. We've since got into sales and sales support and because our remit as a team has expanded out of service now to being the entire organization. So how do we put optimize. How do we optimize the organization? The product's moving so fast over here. How do we take the as is organization and match that pace? And that's really what my, my team are there to do. And Poly AI is one of the main tools in our toolkit to do that. So sales, we're now talking about how we can assist the sales process with PolyAI in various channels, but also with next best action and expanding those capabilities out. So chat and WhatsApp being a great tool for sales teams, especially B2B. WhatsApp is an interesting one because it allows people to think they have an open conversation with an organization and gives a bit of a concierge feel, but is great for resource. Right. A lot easier to resource. It's asynchronous. So yeah, you can see there. I've already touched on another plot of things that we're starting to look at. So I think up people's natural curiosity because of the positivity around Poly AI in the business has led to lots of people starting to knock on the door and say, could we do this or could we do this? And then we had that conversation with our brilliant account team and they say, we're not sure. Give us a few, give us a few days and we'll come back to you. And they, they do. And they say, well, we could try this and we can. And we're starting to co create solutions together now. Right. Which is a brilliant place to be in. Right. For a partnership. It's a fantastic place to be in.

[00:26:50] Nikola Mrkšić: No, no, look, I mean, I think we've been like tremendously successful and you guys pushed us as well. But you know, I think that kind of like, especially like that use of Ren as a coding agent has allowed like the abundance of work on both sides of the kind of collaboration where we're. No, you know, the same way that the contact center was constrained, I think. And do you have enough people to just do failure management and like pick up the phone call. You solve that. Waiting times are zero. You get some time back. You get some time back for people to actually then do more of this kind of work. Right. And then like with A coding tool, you lower the cost of doing any of that work and you don't need like a massive bill for the it to do anything. And then, you know, the iterations accelerate and next thing you know, you're not just doing that like first goal and failure management, but you're really kind of like wrapping yourself around the journey. And I don't think there's any rule around it all has to be AI or humans, but I think it's exactly that, like, what do people actually want? Right. And if you can afford to experiment, then you find the better thing and then you crush your competitors if you have a better experience.

[00:27:51] Paul Atkins: Correct. What's the customer effort in this? What is it that they are trying to do or seek an answer for? And if you start to journey design not around how do we resource demand, but around what should the ideal customer journey be? And if you think about some of the transactional questions that people want to answer and they want an answer at their fingertips. Well, think then about the channel that you want to have that interaction in and where they want to receive that information. And then think about also the journeys that you do want. A human, you know, service like bereavement, for example, or somewhere where you do want empathy and you want, you know, multiple activities happening on the back of an interaction that requires more skill, more depth of thought, more contextual and emotive understanding, all that kind of stuff and design that way, rather than the traditional cx, which is like, you know, the Pareto and get, you know, give me your volume and your failure demand and we'll just work from the top downwards. Now it's become about architecture, you know, experience architecture and how AI and automation tooling complement that, that architecture. I think that's how the gains changed for me, I think certainly over and accelerated over the last few years, that's for sure.

[00:29:01] Nikola Mrkšić: Yeah, yeah, you meant. You mentioned the hackathon that you did. What were the use cases that ended up being built?

[00:29:08] Paul Atkins: Yeah. So we chose a practice. This was part of like a team day across technology. Right. And then we broke out into our rooms and myself and my team had a pr, had a selection of practical problems we could solve, but we chose a practical problem within our practice support team, which is how can we identify. So this is in the Den plan, part of our business. So dentists, when I say practice, I mean dental practice. Sorry. So how do we.

[00:29:34] Nikola Mrkšić: Very happy customer for about eight years now. So

[00:29:38] Paul Atkins: happy to hear that. Happy to hear that. Well, you know, my contact details, if you've Got any problem? Don't be bypassing Poly AI though when you call, right? Don't be hitting those speak to prompts. Nicola?

[00:29:50] Nikola Mrkšić: Never.

[00:29:51] Paul Atkins: Cool. Yeah, so we picked it, we picked a problem in our practice support team around IDMV which is identifying and verifying practices. And we know it works in Simply Health Agent, but we've not really explored it a huge amount over in the dental practice support teams. So in Simsi Health for example, it's achieving 85 to 90% success, which is brilliant. And we identified that over in the Denplan part of the business. It takes around 30 seconds per call to complete that. So to keep it quite simple for the hackathon, we wanted to introduce an IDMV solution. So identify and verify solution for that practice support team to take potential routine work away from the advisor. So then we used Wren, we looked at the existing health plan journeys, we looked at how we would need to repoint some of the prompting to Denplan and kind of the data sources there and validate some of that. We looked at the current FAQs that existed in Denplan, the dentistry part of our business, and we looked at the current journey and any supporting system. So we had various parts of the team in the room doing those various different activities. And then so we built a, a bit of an MVP by repurposing some of our health plan prompting and re engineering it to face into the other, the Denplan part of the business. And we then started to do a bit of live QAing on it and running some scenarios and trying calling up the phone lines and trying different stuff ourselves. Within the afternoon we built out a feasible solution that has since sailed through all the various QAs and been tested and is going into deployment next week. So an afternoon of the team's time doing a bit of team bonding I think has built a practical solution and I think that was a really interesting approach to solving that business problem. But it was great seeing all the different parts of my team working together using, using Ren and using Poly AI to build out the solution. And I think the exciting thing for me isn't about the 30 seconds, you know, IDMV save, which is brilliant, right from a business perspective. But it's the operating model behind it, it's the team spotting the opportunity, being increasingly capable through Ren of analyzing that problem, prompting something, testing it, putting it into deployment again, using Ren to help us understand and complete those stages and doing it in a encapsulated piece of time. Right. A time bound exercise. I think that was pretty cool and a really interesting exercise. I think other organizations that are in partnership with Poly should. Should try the same thing. I think it's. It's quite, Quite a cool, cool exercise to do.

[00:32:27] Nikola Mrkšić: No, it's incredible. And I think, you know, the one thing that, like, gets me going here is, like, it's just fun. And, you know, when you kind of like, give someone, like, an ability to have fun doing the work they do and probably already love, but then when you amplify it with this level of fun in it, you know you're onto something really good.

[00:32:46] Paul Atkins: Yeah.

[00:32:46] Nikola Mrkšić: And, like, forget the business value. It's great that it pays for itself if it's at all successful. And it by and large is and continues to be in, like, greater and greater, like, you know, incidence rates, but it's more just like, it's really fun. Right?

[00:33:00] Paul Atkins: Yeah.

[00:33:00] Nikola Mrkšić: And like, it also, like, completely closes that loop between, like, the builder is the person who knows what a good experience is. So it kind of like just that communication of backup. You build me this. Oh, you don't get it. You didn't do this. You said this is the wrong way. How is this not obvious to you? You know that classical, like, business and IT teams pointing fingers and blame at each other. It's like, hey, go to your IT team to make sure that it works with, like, a huge workload, that it's provisioned the right way, that it's safe, that it's all the things that those guys are actually like. They have fun doing that. Right. Because that's why they are in like it. Right. Whereas, like, the people who are, like, in CX are there because they want to create great experiences. So

[00:33:40] Paul Atkins: you might as well

[00:33:41] Nikola Mrkšić: cut

[00:33:41] Paul Atkins: out

[00:33:42] Nikola Mrkšić: bottleneck, right?

[00:33:43] Paul Atkins: Absolutely correct. And I think that's been part of our move into tech. And what was great in the room during the hackathon, right, was that we had. Some of the team haven't used Poly as much as others, but it was actually contagious that the. I want to give this a try. Right. When can I go in?

[00:33:59] Nikola Mrkšić: Yeah.

[00:33:59] Paul Atkins: And I think, as you've alluded to there, right, the safety elements and the release protocols and the stuff that our tech teams own, and rightly so, having moved into technology now, we're closer to that. Right. And we're kind of joining up the party a bit here between the. The people that can understand poor business operations and poor process and inefficient process and failure demand, but also customer experience and championing the customer experience closer to the people that can facilitate the solutions. It creates a pretty powerful business unit, I would say. So. Yeah, a few things there that we took out of that exercise, that's for sure.

[00:34:38] Nikola Mrkšić: Yeah. Awesome. Well, look, it was really, really good to have you on here. Really excited to hear about all the moments and thank you for sharing them with the audience as well. I'm really excited about just like seeing what you guys will build over the next period. I feel like, you know, time has now collapsed and we'll probably build more in the next six months than within the last

[00:34:55] Paul Atkins: three

[00:34:55] Nikola Mrkšić: years.

[00:34:57] Paul Atkins: We've got some exciting things coming, that's for sure.

[00:34:59] Nikola Mrkšić: Yeah.

[00:34:59] Paul Atkins: Thank you very

[00:35:00] Nikola Mrkšić: much. Thank you. Thank you again so much for me. It was great to have you. For the viewers, please like share, subscribe and we'll see you in the next one.

[00:35:07] Paul Atkins: Brilliant. Thank you. Sam.

About the show

Hosted by Nikola Mrkšić, Co-founder and CEO of PolyAI, the Deep Learning with PolyAI podcast is the window into AI for CX leaders. We cut through hype in customer experience, support, and contact center AI — helping decision-makers understand what really matters.

Hear a voice agent on your own calls

Book a 30-minute demo and we’ll run a conversation from your world through a live agent.