Laura Meschi

So, yeah, it's really, really fun to be working on this project where the technology is so new and it feels new for everyone. So you don't feel left out in a way. You're not alone. Yeah.

Probably AI is the new internet smartphone technology revolution. So it's like being in the midst of something that is probably life changing. So it's exciting and scary at the same time.

Probably AI is the new internet smartphone technology revolution. So it's like being in the midst of something that is probably life changing. So it's exciting and scary at the same time.

Probably AI is the new internet smartphone technology revolution. So it's like being in the midst of something that is probably life changing. So it's exciting and scary at the same time.

So as I said, we started with setting up use cases for the usage of agent force based on the highest reason for contact, which in hindsight, it was the only way we could do this being so unknown and, you know, unknown territory for everyone. But in hindsight, I think we probably chose use cases that were a little too complex for So it took a little longer to build the functionality.

So as I said, we started with setting up use cases for the usage of agent force based on the highest reason for contact, which in hindsight, it was the only way we could do this being so unknown and, you know, unknown territory for everyone. But in hindsight, I think we probably chose use cases that were a little too complex for So it took a little longer to build the functionality.

So as I said, we started with setting up use cases for the usage of agent force based on the highest reason for contact, which in hindsight, it was the only way we could do this being so unknown and, you know, unknown territory for everyone. But in hindsight, I think we probably chose use cases that were a little too complex for So it took a little longer to build the functionality.

As it wasn't just answering FAQs questions, we started off by asking the virtual agent to actually perform some actions. So it took longer than expected. And one other challenge was reporting on return on investment, which felt a bit more complicated than what I expected. within the functionality itself.

As it wasn't just answering FAQs questions, we started off by asking the virtual agent to actually perform some actions. So it took longer than expected. And one other challenge was reporting on return on investment, which felt a bit more complicated than what I expected. within the functionality itself.

As it wasn't just answering FAQs questions, we started off by asking the virtual agent to actually perform some actions. So it took longer than expected. And one other challenge was reporting on return on investment, which felt a bit more complicated than what I expected. within the functionality itself.

So it took a little bit of a DIY solution to try to get an understanding of how successful the deflection rate was for the agent and how successful in general was the handling of the conversations with our customers. Yeah, I would say those two. And probably the setup process, it's fairly easy, especially if you're looking into setting up a use case that is an FAQ-based type of use case.

So it took a little bit of a DIY solution to try to get an understanding of how successful the deflection rate was for the agent and how successful in general was the handling of the conversations with our customers. Yeah, I would say those two. And probably the setup process, it's fairly easy, especially if you're looking into setting up a use case that is an FAQ-based type of use case.

So it took a little bit of a DIY solution to try to get an understanding of how successful the deflection rate was for the agent and how successful in general was the handling of the conversations with our customers. Yeah, I would say those two. And probably the setup process, it's fairly easy, especially if you're looking into setting up a use case that is an FAQ-based type of use case.

But the time that it takes for testing and quality assessment of the interaction, it's quite extensive. And that's something I completely, not completely overlooked, but I kind of did not take into account that much when we started off this journey.

But the time that it takes for testing and quality assessment of the interaction, it's quite extensive. And that's something I completely, not completely overlooked, but I kind of did not take into account that much when we started off this journey.

But the time that it takes for testing and quality assessment of the interaction, it's quite extensive. And that's something I completely, not completely overlooked, but I kind of did not take into account that much when we started off this journey.

It was mainly the fact that the deflection rate we were expecting to achieve has not been as high as we expected. Partially, it could have been an unreasonable expectation to have, because, as you said earlier, you know, we thought it would be much more immediate, whereas this is something completely brand new and you kind of have to learn by doing.

It was mainly the fact that the deflection rate we were expecting to achieve has not been as high as we expected. Partially, it could have been an unreasonable expectation to have, because, as you said earlier, you know, we thought it would be much more immediate, whereas this is something completely brand new and you kind of have to learn by doing.

It was mainly the fact that the deflection rate we were expecting to achieve has not been as high as we expected. Partially, it could have been an unreasonable expectation to have, because, as you said earlier, you know, we thought it would be much more immediate, whereas this is something completely brand new and you kind of have to learn by doing.

So it's part of the challenge and part of the beauty of this is that you just learn as you go. So that was the challenge. And yeah, because the, um, deflection rate is not what we expected. We kind of have to try different ways of achieving and maximize the power of the technology that we have. Um,