label: Me

text: Hey, good afternoon. It's a pleasure to make your acquaintance.


text: Good afternoon.


label: Voice 2

text: Yeah, thanks for joining. We're looking forward to hearing what you've


text: got.


label: Voice 3

text: I know we don't have a ton of time today, I'll really jump right into things.


text: As far as an agenda, I just wanted to start with a couple of hellos and then


text: Mhmm.


text: I don't actually have an agenda slide, so I should probably create one of those. I'll make a note


text: to do that afterwards. But


text: let's just say that we'll, look at our AI assisted whiteboard,


text: talk very briefly about Rhyme's, history and and why we're we're quite unique. Then really dive in, spend the most of our time talking about areas you're looking to improve with your current voice solution, that you use a a nice Cognity for. I also have a a brief custom demo. I'd love to show you. And then afterwards, we can get some feedback and talk about potential next steps. Of course, along the way, please don't hesitate to stop me for any questions. Sound good?


text: Yeah. That sounds fine. Just to be clear, what exactly are you hoping to get from this first conversation?


text: Really just an understanding of


text: the reasons that you decided to take the meeting today and some of the challenges you're facing.


text: Well,


text: get pitched a lot.


text: Our priority is reliability and


text: not creating risk.


text: So,


text: reliability is a


text: pain point?


text: Sometimes.


text: Yeah.


text: Especially during peak call times.


text: Though, to be honest,


text: any change has to be justified.


text: We don't swap


text: corn for the starting


text: obviously, my name is Colin. I'm the founding account executive here


text: Perhaps you guys could do a quick round of intros on your side?


text: Oh, of course. I'm Dana.


text: I'm over customer experience. I own the metrics around


text: customer satisfaction and containment.


text: I'm Marcus.


text: IT and systems. I care about integration, security, and not breaking in what's already working. And I'm Priya from procurement.


text: I come in when there's a clear business case,


text: cost clarity, and


text: risk controls.


text: Super helpful.


text: Just so you know, so we're using an AI


text: whiteboard today, so it's gonna just help us organize a couple thoughts and really,


text: make sure we track what's most important to you so we we lose track of anything. And I


text: can still be present without taking a million notes. So let me jump into that and,


text: let's go from there.


text: Oh, you know, one last thing just so you have a bit of context on us. So we're at Rhyme. We're


text: three years old, started by Lilly Brookton Ares.


text: And


text: we take a little bit of a different approach to this problem. You know, we we come from a linguistics background


text: primarily as well as a


text: having a lot of AI engineers. And when when we sat down to tackle it,


text: we rather than using, you know, Actor generated training data or


text: podcasts like everyone else did, we actually set up a recording studio.


text: And we we started having, you know, legal folks actually speak


text: for thousands of hours that we can capture natural human communication


text: in a much more nuanced


text: realistic manner than the


text: models that are created with the traditional data.


text: But the proof of all that is just, you know, looking even as a small


text: we're now powering tens of millions of calls every month for


text: healthcare, telecom, enterprise support,


text: we're all over.


text: Just even last month, did a study with 100,000 calls that we


text: help sponsor.


text: A third of those were with us and then two were from our competitors. And


text: although no one actually loves receiving calls, this was a politics survey, so it's


text: legitimate.


text: We had the lowest hang up rate amongst any of them and the fastest completion rate.


text: So people actually do enjoy speaking to our AI.


text: But anyway, you're you're you're primarily to talk about voice AI at Assurant.


text: It would be great to understand how you're generating speech today, what tools, and


text: you know, what sort of outcomes you're you're looking for if things work


text: and then maybe a little bit about where things are breaking.


text: We use NICE with


text: Cogniggy for orchestration.


text: It works, but


text: voices can feel, they're robotic.


text: Yeah. And when customers are already frustrated about


text: device protection claims or warranties, that doesn't help.


text: Technically, we are stable, but


text: latency spikes happen during peak


text: and


text: integration touches are non


text: We don't


text: have appetite for heavy lift unless


text: return is obvious.


text: That makes a lot of sense. So you're talking about


text: the


text: reliability and the robotic voices. Could you talk a bit more about the impact of those issues?


text: Why do those Chatter.


text: When voices feel robotic, customers tend to


text: repeat themselves or ask for a human that hits


text: containment and increases cost per call.


text: It also impacts CSAT.


text: Quite directly.


text: And I guess just to double picture,


text: obviously, we're we're familiar with


text: CESAP, but why does that really matter?


text: Because lower satisfaction drives complaints


text: and churn.


text: And our clients notice.


text: Also, spikes during peak create longer handle times, so


text: that's


text: more cost.


text: Even small deltas add up at our scale.


text: And that's where we get nervous.


text: We need clear ROI, not just a better vibe.


text: That makes sense. So


text: would you say one of the the the best ways to measure


text: success would be a significant increase in CSAT?


text: Yes.


text: But


text: also look for improved containment.


text: Without


text: increasing escalations and stable handle times.


text: And from my side,


text: clear cost predictability and


text: Who who's speaking you?


text: Priya.


text: Procurement.


text: Just thought you na


text: early.


text: And so what were you saying again?


text: We need a clear cost predictability.


text: And risk mitigation.


text: Cost predictability and risk mitigation.


text: So that that that's a a


text: pain or a success criteria.


text: That's success criteria.


text: And


text: to be clear, if this is a rip and replace


text: that's a much higher bar.


text: We need to understand how this fits


text: without introducing operational risk.


text: Yeah. I mean, very simply put, you know, we'll we'll get into


text: some of the details of our solution later. I'm really focused on on understanding


text: your concerns right now, but


text: absolutely,


text: by virtue of being natively compatible with your orchestration layer,


text: it's simply a matter of changing a couple API endpoints. There's very little configuration


text: required. Perhaps we'll do a a a few, you know, special awards that


text: might be unique to your business to get those


text: working with model, but we have a a


text: few ways of doing that very effectively.


text: And, yeah, that's it's


text: it


text: the actual getting a POC up and running is is incredibly


text: fast and low cost.


text: Okay.


text: Any other pain points


text: Marcus, I haven't heard a lot from you yet.


text: Main thing is we can't


text: afford downtime or surprises.


text: If anything touches PII, security review


text: gets deep fast.


text: And we don't wanna manage multiple new vendors for


text: niche pieces.


text: Yeah. So would would you say that having a a sock


text: two, Type two solution that's hosted on prem would would help a lot with your security concerns?


text: Yes. That helps. But my


text: bigger concern is still operational risk.


text: If


text: we were to switch TTS providers, that is.


text: And can can you speak a bit more about that concern?


text: We have tight SLAs.


text: Outages or latency spikes have contractual


text: implications. So any change has


text: to be basically invisible or


text: demonstrably safer.


text: That makes a lot of sense.


text: I, yeah, would be happy to share some of our SLAs and,


text: reliability stats with you later. But


text: certainly, what I can say is that by having an on prem


text: solution with


text: extreme predictability when it comes to


text: concurrency


text: limits and GPU requirements. It's a very well run model that's


text: already hosting, you know, tens of millions of calls every month. So there there's just no issues there.


text: Okay.


text: Any other concerns or we haven't talked about yet?


text: Just that we get pinched


text: constantly.


text: So


text: we need specificity.


text: Not


text: generic AI promises.


text: Yeah. You know,


text: if there's no other concern so so far, we we've talked about the outages and latency spikes


text: and the SLA requirements, the need for predictability.


text: The operational risk, security review, and


text: just not being able to afford downtime.


text: If there's nothing else you you wanted to add, I I can, hop into a quick demo.


text: Yeah.


text: Freeze is


text: good.


text: Let's try it live. Wish me luck.


text: Alright.


label: Voice 4

text: Hello, and thanks for calling NorthStar Device Protection. This is a demo, and the call may be


text: recorded.


text: I'm NorthStar's virtual claims assistant.


text: How can I help you today?


text: Oh my gosh. I just broke my phone.


text: Oh, yeah. That's, that's pretty naturalistic.


text: Thank you, Tal. With your broken phone, I just need to verify your identity.


text: Can you please provide your ZIP code?


text: Yeah. 94105.


text: Thanks for that, Colin.


text: I see your policy is active and covers accidental damage.


text: When the damage to your phone happened,


text: It happened July 11.


text: Thanks, Colin.


text: Was the damage accidental, liquid related, mechanical, or something


text: Oh my god, I was getting ready for this really big presentation to these amazing people, but


text: I was so excited I knocked my phone off the table and it it cracked the screen.


text: Totally an accident.


text: Got it. Accidental damage.


text: Does the phone still power on and work for you?


text: It


text: does.


text: Great. And do you still have the device with you?


text: I


text: do.


text: Yep.


text: What should I do?


text: You'll need to keep the device. Yes.


text: Just to confirm, your iPhone 16 Pro had an accidental drop on July 11.


text: Screen cracked, but it still powers on, and you have the device with you.


text: Yes. Is that


text: correct?


text: Uh-huh?


text: Your claim number is CLMDemo2049 The deductible for screen repair is $29 I can send a secure link to upload any documents needed to the phone number we have on file.


text: Would you like me to send that now?


text: Sure. Or would you prefer to talk to a device


text: claims specialist?


text: I'll talk to a specialist as well.


text: You're not connected to a device claim specialist who has all your claim details.


text: They'll assist you further from here.


text: Hi, Colin.


text: This is the device claim specialist here.


label: Voice 5

text: I understand you have claimed CLM demo 2049 for accidental


text: screen damage.


text: And I'm here to assist you with any questions have


label: Voice 6

text: available. Mais est-ce


text: que vous pouvez le mettre en français


text: Bien ça.


text: Les pouvons continuer en français.


text: Merci Colin.


text: Si vous voulez parler directement à un conseiller en français, je peux vous transférer.


text: C'est c'est gentil, mais mais c'est ce que j'ai besoin. Bon journée.


text: Très bien Colin. Merci d'avoir appelé le


text: to what you have now?


text: Honestly,


text: smoother than I expected.


text: Less robotic.


text: But


text: I'm curious how it performs at scale under peak.


text: From a CX lens, tone felt


text: calmer, less robotic. That's good.


text: I'd wanna see how customers actually respond in our


text: context.


text: And for me, it


text: still comes down to commercials and risk.


text: Sure.


text: Let me address Let address all of


text: these.


text: Just so for context, this is something I made myself in just a few minutes. I'm I'm not


text: part of the engineering team. So, obviously, a production grade


text: system would be a lot more sophisticated.


text: I used one of our our many voices named Vespera because


text: has more formal, professional, and reassuring tone. If someone just broke their phone, obviously,


text: that's quite important. That said, we even have different voices that


text: some customers use for folks from different parts of the country and


text: can do a lot a lot of flexibility there even based on gender.


text: So it's it's just a starting point. But


text: if you have some more questions, now might be a great time.


text: Makes sense.


text: Yeah. I'm I'm mostly thinking about real world performance and measure


text: Well, yeah, you know, as I say, we


text: were some of the largest brands in the country are already using our our systems.


text: We have some case studies that I'd be happy to to share with you.


text: You know, did I talk about the fact that we did a 100,000 calls recently


text: and they all work


text: Yes. That makes sense as a data point.


text: I think the next step for us is probably to


text: define what success would look like internally before getting too far.


text: Yeah, I mean, that's generally how we think about a POC


text: So, normally, we would arrange a a call to align on the scope and success criteria.


text: And then, start to,


text: to pilot on one live call flow in in limited production.


text: Once that runs for for a couple weeks, we would reconvene to resume


text: review the results and really just measure success against


text: not just does it sound nice, but the things that really


text: matter, like


text: call completion, C SCAT, or customer call sentiment.


text: Right.


text: That sounds like a reasonable framing.


text: We need to align internally first.


text: I'm not making any commitments today, but


text: sure we can consider it.


text: Sure. No, that makes a lot of sense. You know, we do have quite a few of these


text: on the books, though. It it would be great just to to carve out time in case


text: perhaps in, a week from now just to pencil that in.


text: Can we do that? And, that'll give you some time to align in turn


text: and see if that that date works or if we need to move things around.


text: I think pencil


text: thirty minutes is reasonable.


text: But


text: Yeah. No. That that that would be great.


label: Voice 7

text: Folks there.


text: Absolutely. Who do you think are the decision makers that should be there?


text: I'll start.


text: Own CX metrics, so I'd be involved.


text: And we bring in someone from our platform architecture team.


text: And procurement if there's a real business case in Rochang.


text: Yes, that works.


text: Send a couple of times.


text: I'll I'll absolutely do that.


text: You know, this was a a real pleasure.


text: If you need any more information, everything's here on the website.


text: And


text: I


text: really appreciate you guys taking the time today.


text: Sounds good.


text: For walking through it.


text: Alright. Ency.


text: Noted.