ACP: The Amazon Connect Podcast

28: User Adoption

Tom Morgan Season 1 Episode 28

Send us a text

In this episode, Tom and Alex return refreshed and ready to dive into everything Amazon Connect. They provide a detailed update on the latest features and improvements in Amazon Connect from the past two months, including real-time dashboards, Lex bot integration, agent performance evaluations for email contacts, and outbound dialer enhancements. They also discuss the importance of user adoption, covering strategies for successfully implementing Amazon Connect in your contact center, training for different personas, staying updated with new features, and leveraging AI tools like Amazon Q. 

Whether you're a techie, a contact center supervisor, or an agent, this episode is packed with essential insights and tips to make the most out of Amazon Connect.

Links discussed this episode:

AWS Amazon Connect Online Workshops


00:00 Introduction and Welcome
00:56 Latest Amazon Connect Updates
09:53 User Adoption: Importance and Strategies
12:03 Training and Familiarization
22:42 AI in Contact Centers
32:05 Conclusion and Wrap-Up

Find out more about CloudInteract at cloudinteract.io.

Tom Morgan:

It's time for another ACP and we are back. We are refreshed and we're looking forward to talking for another episode. Alex is with me. Hello, Alex. How are you?

Alex Baker:

Hi, Tom. Yep. Good. Thank you. Yeah, also refreshed. Just had a week off now, back at work, ready to talk more Amazon Connect stuff.

Tom Morgan:

Excellent. Excellent. Before we really get into the meat of this episode let's have a little starter. And let's start with any exciting news items that we may have missed since the last episode. So Alex, what have we, what have we got? What have we been missing out on?

Alex Baker:

Yeah, I feel like we've, for various reasons, you know, guests and what have you, we, we've not done The news section for a little while. We, we have been putting out monthly Amazon connect what's new posts on, on LinkedIn. So this kind of stuff we try and summarize in there, but just to pick out a couple of the things in the, Amazon connect release notes over the past two months, so Jan and Feb we've got some good updates around dashboards that real time dashboard capability is constantly growing, so you've got a real time dashboard for agent activity, for example, that was released in January. Going a little bit away from that, the sort of tabular format that was previously, well is still there, but you know that was previously available in Connect. You're getting more of a A visual looking dashboard, which you can tailor things like the, the widgets that you have on it the, the metrics that display on the widgets and then things like your thresholds. And you can start to have red, amber, green statuses on different metrics. There are also metrics around things like so Amazon appears to be sort of bringing Lex bot creation, making it a lot more tightly knit into Amazon connect itself. So you can configure bots from directly within the connect console, but you can also. Look at dashboards for them as well. So you can within connect, check out your bot performance, look at things like missed utterances and that kind of thing. So you can do a sort of ongoing tuning of your bots. We've, we've also got the ability to evaluate agent performance for email contacts now. So up until, up until now, it was voice and chat with the introduction of email fairly recently. It's nice to see that now you can evaluate your, your agent performance on the email channel.

Tom Morgan:

sense. Yeah, makes sense. Okay.

Alex Baker:

Around reinvent, it was, it was mentioned that there was a bit of a revamp of the outbound campaign outbound dialer type functionality. And, and one that's related to that, there's a currently in preview, but preview of persistent agent connections for faster call handling. So I think some of the. Some of the feedback that I'd heard in the past when using the outbound dialer, certainly in certain locations is that when it was doing that, the, the setup of the call, sometimes as the, the customer, the recipient, you might hear a bit, a bit of a delay as you were getting, as everything was getting connected And in theory, this should sort of try and reduce that delay as much as possible. So it might just make it a bit of a, an easier thing to, to get through compliance and to, to start using that functionality, I know it's something that with the revamp, a couple of our customers are quite keen on, on taking another look at the outbound campaign

Tom Morgan:

that's good to know. Yeah, I was gonna say, so if you've, if you've discounted or you've tried it and you haven't liked it and you, or even if you weren't really aware of that delay, if you didn't get the results that you wanted, maybe try it again, because it sounds like that experience is a little bit slicker, a little bit more natural than it, than it previously has been.

Alex Baker:

Yeah, definitely, definitely worth looking at again. We've got one around performance evaluation. So this arguably fairly small release, but you can automatically send. Email notifications to agents when their contacts have been evaluated, and that's now native. That's something that you could, you could set up yourself. Previously, you're using Lambda functions SES that kind of thing. But it is something that, that is now native, so you can put in a, an automatic notification for, well, any any evaluation that's been carried out, or maybe evaluations with a particularly low score. You could send a notification to the agent to say this needs some attention. Please arrange a coaching session with your supervisor, that kind of thing.

Tom Morgan:

I can imagine that's quite important, actually it's it's important to keep. Like, it's no, it's no good as an agent saying, like, it's time for your review and you've done rubbish, you know, over the past six months. So, well, you never told me I was doing rubbish, you know, like, automating that process of, in the moment, you know, day by day keeping on top of it. That feels, that feels quite important.

Alex Baker:

Definitely. Yep. That's a really nice little addition. We've got the, this one's around forecasting capacity planning and scheduling, and I know this was something that when I mentioned it to, to one of our colleagues he was really excited about for one of our customers in particular, cause this was. It had been a bit of a a sticking point for them, but you can, now configure which states an agent can be in when adhering to their schedule. So for example, you can map a schedule activity like work, whatever you want to call it, to multiple different agent statuses. So if you're in. As the agent, if you're in available or if you're in back office work, or if you're in an outbound code, all of those can map to that schedule activity work rather than there being this sort of one to one mapping, like you're, you have to be in available or you have to be in a certain code. So yes, another, small, but important, nice functionality improvement there.

Tom Morgan:

Yeah, definitely. That's good. Yeah. It's, it's, I don't know. It's all those things. They come out like it's, it's the V2, V3, V4 iteration of a feature, isn't it? Where, you know, you sort of find these things and fill the gap. So yeah, that's good.

Alex Baker:

Yeah, great. What else we got? So there's targeting multiple agent proficiencies in a single routing step. So this is around that sort of more granular skills based routing. Haven't haven't played with this at all, but just reading off the notes so you can target up to four different combinations of agent proficiencies per routing step. So by using up to Three or conditions, the routing tries to match a contact with four different types of agent, which increases the possibility of finding a suitable match. So yeah, you can really start to put in some granular skills based routing around maybe the, the particular level of training that an agent has on a certain language or their account management skills, their ability to deal with something like tax questions that kind of thing.

Tom Morgan:

That's cool. Nice.

Alex Baker:

And the final one just to take a look at and actually, it's only now that I've noticed this one. There are some new evaluation metrics available. I'm just taking a quick look through those. We've now got. Average evaluation score. So this is, let me just step back a sec. The following contact evaluation driven metrics are available on historical metrics reports. So you've got, yeah, average evaluation score, average weighted evaluation score. Automatic fails percent. That one, that's certainly one that we've developed custom reporting for people in the past. Cause there wasn't anything sort of available out of the box. It was quite nice to see that in the natively and connect. And then another one for evaluations performed. So, yeah, I think on my point of, we've developed. Quite a bit of custom reporting around evaluation metrics just because there wasn't really that much for it out of the box. But obviously Amazon have seen that that is a bit of a gap as well and started to bring those in, which is great.

Tom Morgan:

Right. Yeah, definitely. So over time, those things get put into the box. That's fine. You know, then that's, that's the that's our job is to fill the gaps whilst they're there and then to sort of step away and step aside as the gaps get filled and go and fill other gaps. So yeah, definitely. That's good.

Alex Baker:

I'm sorry. The other one to mention around that actually is and we mentioned dashboards at the start of this section and agent performance evaluations dashboard as well. So just to. Just to tie that up there again, improving that out of the box experience and being able to go into your dashboards and check out how people are performing and their evaluations.

Tom Morgan:

Yeah. Oh, good. It feels like this whole evaluation thing is just growing and growing and becoming more and more important and more and more sort of central and completely makes sense because yeah, it's such an important part of. Obviously keeping a quality bar high.

Alex Baker:

Yeah. We've spoken about it. We've done whole episodes around quality. It is still one of the areas that I'm really excited about because of the introduction of the capability to automate and to be able to. Do much more than what was traditionally, maybe two evaluations per agent per month or whatever your metrics were being able to move that much closer to 100 percent to evaluate in some way. I think that's great.

Tom Morgan:

Definitely. Oh, well, thank you for the for the news roundup. This episode, we're going to be talking all about user adoption, which is a kind of underrated, but really important subject. We did talk about it a little bit at the back end of last year. But it's, it's definitely worth spending a whole episode talking about. We thought because. It's quite easy sometimes, I think, as technical people, Alex and I are both techies, and it's easy to get caught up in the technical delivery of something like Amazon Connect, and to really just focus in on that and get that bit done, and then to be really surprised and a bit annoyed and upset if. The whole project is not deemed as success afterwards because even though it was technically perfect, actually nobody used it because you didn't bring people along for the journey. So that user adoption part is really important. It's really important in the outcome of a successful project. And so it's definitely something you should be thinking about.

Alex Baker:

Yeah. And don't underestimate the fact that people like your agents are going to be interacting with it much more frequently than we do, or, you know, that the agent interface part of it. So it's got to, it's got to make their lives easier. It's got to be understood, easy to use. They've got to get the best out of it.

Tom Morgan:

Definitely. And that's what we're going to be talking about this episode. Really the kind of how to have user adoption for Amazon connect. So let's start at the very beginning. I think probably before you'd even. Show agents at what an Amazon connect looks like, you know, right at the very beginning of that journey, you've decided to move your contact center from whatever it's doing to Amazon connect or you, maybe you don't have a contact center. You just have people answering phones. Cause that's quite common as well. Like that's how people, you know, it's your company's grown. It started small. You didn't need a contact center. So they're currently just answering phones as much smaller organization. And, they're kind of, Decided that they've grown and now's the time for a contact center. And, and so you've decided on Amazon connect as the technical person but you now have to sort of sell that to your agents, what's, what's the process there and, and what, what's involved in doing that and how much of it, I guess, how much of it needs to be technical or is it, is it more about just keeping them involved and letting them know? And, and how, how early on do you tell them essentially?

Alex Baker:

I guess from, from your own perspective, if you're, especially if you're going in sort of fairly, fairly new to it go and make the most of all of the resources that are out there. The first of all. On connect so that, you know, the ins and outs of it yourself as much as possible. And, you know, about the, why, why are you doing it? Why have you chosen connect? What are the benefits? Why is it good for your business? So that you, when you go and talk to. The business users about it you can put across a good case for that and make it compelling. You know, I think people are sometimes resistant to change, especially if you've had, and we've seen it with some of our customers, they've had legacy systems in place for 5, 10 years or even longer.

Tom Morgan:

Silence.

Alex Baker:

change to your daily your daily work, isn't it? If you, you're, that system that you're interacting with constantly for your eight hours at work, if it's going to change, understandably, people are sometimes resistant to that. So. Yeah, I think my point is, if you're going in as the product owner or project lead make sure you're fully sort of comfortable in, in talking the benefits of the change.

Tom Morgan:

Yes, you're right. Absolutely. The people don't, yeah, people worry sometimes about change because also it's, it's changed because it's, yeah, someone's moved my cheese and I don't know what I'm doing anymore. I think there's a, there's a worry as well. And I think we justified as well, but the process gets built up over time. You know, we do things the way. We do them and part of that is because that's how we've always done them. But part of it also is. Because there's a really good reason for doing it that way. And if we take that away, you know, we might remember the hard way why we did it the way we did. So there's all these little business processes that need to be sort of captured and thought about. And I think, you know, that comes across sometimes as resistance to change. So it's kind of well intentioned resistance to change. What I think one of the nice things about Amazon Connect is that and we've talked about this before because of its consumptive model and how easy it is to spin up. I guess whilst you're building out what will become the production contact center, I guess there's no reason why you can't just sort of spin up a test instance just to get people a bit familiar with it. And so they, I'm thinking maybe. people who are coming from not from a, an existing contact center, maybe. And they're just used to answering the phones just so they can see how that flow is slightly different and get used to it and just sort of start to look around a little bit. Yeah.

Alex Baker:

mentioned that as a, a big benefit of connect quite a bit in the past. I know from working on, on previous systems. Sometimes you'd have the concept of a, whatever you want to call it, a model office, I remember calling it or a, you know, a test area. But yeah, the, the sooner you're able to get hands on with the products and get people working with it and figuring out what the differences are and what the workarounds are, the better and it's. As we know, it's, it is pretty easy to, to go in and set up a, an Amazon connect contact center.

Tom Morgan:

And I think that really helps with the familiarity of, of how the product works as well, but probably doesn't be interested to see what you think about this. Does, does that completely replace the need for like more formalized training or do you think the training as part of this process is still needed and important?

Alex Baker:

The scale of, you know, we talk to smaller customers, we talk to larger customers when you get to certainly into the enterprise space, it's, it's not practical to kind of. You've really, you've got to put some structure around things like training processes. You can't just kind of get your agents to go and have a play in the, in the, in the test setup and figure it out for themselves. And that's where because we, we have dedicated people that deal with that sort of training and comms part of things. Yeah, it's, it's quite a, quite a big piece of work to undertake.

Tom Morgan:

Yeah, makes sense. And you kind of want everyone working in the same way as well. I suppose it's as much, it's, it's partly training on Amazon connect, but it's also partly on training the, in the process, right? The way to use the thing rather than just how the thing works. It's yeah, I'm thinking,

Alex Baker:

that can be,

Tom Morgan:

clothes.

Alex Baker:

it can be quite different. Businesses can have very different processes. So we've, we've sort of created fairly generic training decks or training programs in the past, which then we've gone into. Each of our, our customers and we've had to tailor it because they, they work in different ways because we're enabling different features for them. Things like, you know, custom agent desktops that we've, we've put in for people, that kind of thing, whilst it's still Amazon connect, which is the fundamental core platform, actually, there are quite a few complexities to the way that every single customer works, which means you probably need to really look in depth at, at how the. How the training is tailored to that.

Tom Morgan:

Mm, I think the o the other thing, so you've got. Thinking about user adoption, you've got telling people it's coming. So you've got that communication, you've got training, kind of think about, you know, training and making sure everyone knows how to use the system. And I think it's worth thinking through as well, all the different. The different types of people that are going to use the system, because it's not just the agents, right? And I think that, I don't know that that can easily get forgotten. It's easy to focus in on just the agents and and not think about some of the other sort of personas that are going to be using the system such as supervisors, service owners, execs, they all, they will have requirements for the data normally but an information out of the system and And that's, that can be a really obvious jarring gap if you don't consider it, especially if you're moving from a, from an existing contact center that does provide those things. And, and, you know, the execs used to get in their monthly Tuesday report about how the contact center is doing. If that suddenly dries up because nobody thought about it and captured it as a requirement, then that's not good.

Alex Baker:

It's a great point. Yeah. So early on, do that, that persona mapping who, which personas kind of. Touch the contact center. Obviously, your agents and supervisors are the first ones that come to mind. But yeah, you know, you've potentially got whole teams, like, maybe quality, analysts that they access the system day to day still, but they do it in quite a different way to how, how your agents do. You're going to need to do some totally different training for them. Probably. how do they go in and access calls? How do they use the new quality scoring tools and processes that are available to them and possibly none of that you will, you will train certainly to the agents, maybe not to the supervisors either. Maybe again, it's the slight difference between some of our smaller customers. And some of the larger customers, you might find that in a smaller customer, they wear more hats as it were. So you might have the supervisors that are taking on a lot of the, quality management part of, of the role as well. But then in some of the bigger enterprises, generally, you might find that you have. A QA team, a workforce management team, and they're a little bit more, maybe siloed is the wrong word, but that they're more knowledgeable and experienced and they give laser focus, to what they do. And not so much of the other stuff.

Tom Morgan:

Yeah, yeah, no, definitely. So yes, definitely consider all of the different people in the process. And I think this, it can be, I think, a good time if you're looking at user adoption, and if the input and integration of a new contact center is a really good time to do that, but it shouldn't be the only time necessarily. And what I mean by that is, yeah. You might be listening to this and thinking, well, we've got no plans. You know, we've already got connect already. We've got no plans to, you know, add another connect or anything. We don't need to worry about user adoption, but I think actually it's very much an ongoing thing. And, and especially, I think, especially at the moment with AI and everything, I think user adoption comes back into the focus quite a lot because in a way, so user adoption, as much as anything else is. Is it's ongoing for 1 thing, because obviously people come and go and say, there's always training of new agents. So that user adoption part never really sort of dies. And so it's important to have the tools there for those people, whatever that looks like an organization. And in some places, I think it's, it can be quite informal, right? It can just be. You know, you sit with an experienced member of staff until you figure it out, or you, you know, hopefully there's a playbook or a user guide or something. So you can kind of get your hands on, something to sort of help you, help you learn. But a lot of it is in that kind of handover process. The, the reason for thinking about, I think now as well with AI is. I think if you want to really take advantage of some of the stuff that AI can do, I think in order to do that, you need to have a really solid understanding of how the business works, like the business of running your contact center, if that makes sense. I don't know if you do, I'm not sure if you agree with that sort of slightly unhinged thought.

Alex Baker:

I think I see where you're going. It's, it's something that probably is fresh in our minds because of some of the work. We're doing at the moment where we're uncovering insights into what does happen in people's call centers that maybe that they're not necessarily aware of. So. Yeah, it's a fast evolving space, isn't it? The thing I was going to point out is that whether it's an Amazon Connect or whether it's one of the other contact center as a service providers, I think the pace of innovation is massively increased compared to maybe where it was 10 years ago, where you might be on a more of a legacy platform and it didn't really evolve much, maybe you do a. Like a yearly update or something to the platform, but there wasn't this sort of trickle feed of, of updates and new capabilities, whereas, because that's happening in something like Amazon connect, it's of benefit to you as the user, whatever your persona to keep up to, up to date with those things. You look at some of the things that have been released recently. Things like the the real time dashboarding that's improved massively over the last few months. So if you were a Connect user, adopted Connect a year ago, you might have looked at the real time reports back then and thought, yeah, they're not great. They're quite, tabular. They don't give me the flexibility I need. Whereas now, if you're aware of those changes, you might go back in and it might sort of fit your needs a bit, a bit closer.

Tom Morgan:

Yes, yeah, yeah, I think what I was thinking is as well, like, if you go and look at a, you know, a well run contact center, there's key people in there, like experienced agents They have all like they've seen it all before right so they know instinctively what to do and you kind of want to somehow bottle that institutional knowledge you want to kind of get it and write it down into something like a playbook or a guide or something and capture it for the future because it helps really helps with training but I think it will also help some of this AI stuff and we actually this is maybe a good time to come on to some of that AI stuff because You know, we talk a lot about I in the contact center. And I think it's tempting to think like the easy reductionist view, I think, is that I is going to take all the jobs, but I don't think that's true. And I think it's true in the contact center either, particularly, but I think it, it helps agents do better at their jobs. But I think that's where some of this capturing of this institutional knowledge, I think, can really help. Because I think I can help in taking away some of the easily repeatable things that you don't need necessarily human where, you know, you could have humans be reserved for those much more complicated things or those things that really require. Really require a human. So things that are highly, you know, require empathy, require emotion, require intelligence and all those things. But you can't even start to think about that if you don't know what you've got and you don't have that playbook in place. There's something as well. I think for agents around not fearing the AI, I think, and being an embracing it instead to make yourself a better agent. I'm thinking about things like Amazon Q and the guides, you know, if, if you were starting as an agent today, you've got. Assuming your organization has this, like if you could lean into the Amazon queue, if you could lean into being able to use guides and things like that, I think you'd become, you know, a really good agent really quickly by focusing on the things that, you know, where you add value and then using the AI to help you. I don't know. What do you think?

Alex Baker:

Definitely, the caveat of if it's set up well, and if it, if it backs off to a good source of data, but it's always, whether it's sort of going into a new job or even in existing jobs, everyone's got so much data. And you might not necessarily know where to go and look for a particular answer. If you can have something that is. There in the background, that's just quietly sort of feeding you some of the information that, that is relevant and context sensitive then yeah, surely that should help you do your job a bit easier.

Tom Morgan:

Yeah, definitely. And we talked before, I think about this transition from being an agent to being an advisor. so you're, you're not just in the middle between two computer systems, you're, you're much more plugged into the data and you're doing those kinds of complex tasks that, would be best served by humans. I think that's, there's a really big part of that for

Alex Baker:

Yeah. And you'd like to think that and again, thinking about some of the work that we're doing at the moment, you'd like to think that you'd be able to take some of the more boring repetitive elements. Away from the agents, you know, I'm thinking stuff like the identification and verification, if you can abstract some of that into the, into the IVR, rather than have the agent do it every time, taking away the, the repetitive questions, you know, the. The classic sort of, where is my order? Can I have a status on my order? That kind of stuff. maybe sometimes agents might like that, that the contrast arguably

Tom Morgan:

Yeah, you're right

Alex Baker:

easier, some more difficult work.

Tom Morgan:

yeah, there's a big part here about agent care and, you know, looking after agents and trying to reduce that churn because yes, I think that is true. Agents sometimes just want to take an easy call and that's, that's totally fair and there's no reason why that can't still happen. But I think also we can protect agents from some of those, you know, those calls that are just draining because you know, you've got to give out this bad news and. There's nothing they can say. The news isn't changing. So yes, depending on what it is, that might be something that could be delivered in a more automated way with a sort of, yeah, we can, you know, we're going to tell you all this stuff and you can go and talk to a person, but they're going to tell you exactly the same thing is maybe a better fronting rather than having these agents be shouted out all day because they're trying to deliver this bad news that nobody wants to hear. You know, that may, maybe that's a, we're protecting our agents better in that way, for sure. That's interesting. So the, the reason I got into this at all was trying to capture like the processes that happen inside the contact center because it really helps you use your adoption, but it also, it puts you in a really strong place for taking advantage of some of the things in Amazon connect, such as Amazon queue, user guides for agents and things like that. It helps you sort of really take advantage of all of that stuff.

Alex Baker:

Yeah, and it's, it's always good when, when we take on a project and we get to talk To somebody who's really knowledgeable about all that kind of stuff and, and possibly even that they, they have some of it documented, heaven forbid it. Sometimes you don't get that, but sometimes you do, and yet it may be, you know, a great business analyst or great sort of business lead who really knows the business processes in and out inside and out.

Tom Morgan:

yeah, definitely. Just coming back to training for a minute because just the nuts and bolts of how to use Amazon Connect. I think AWS do workshops for like supervisor roles as well. Is that true?

Alex Baker:

Yeah, so I'm a real big fan of some of the AWS online workshops and we should put a link in the post when we put this out. But yeah, there's, there's some great workshops that you can just go and access yourself about connect in general. There are. I suppose maybe a minority that are sort of aimed more at the, the agent population, but there are some around sort of using the agent workspace and contact control panel probably more at a slightly more technical audience, but, thinking about the, quality team that we mentioned, for example I know there's at least one workshop around that covers that kind of area. Definitely encourage people to, yeah. To go and check them out. They, they've clearly had some, thought and effort put into them. And I think they're designed such that they can either be delivered just as a purely online course or AWS themselves, or a partner can deliver the workshops as a face to face interactive kind of thing. But yeah, I really rate those. And I I'm always trying to use a bit of spare time to keep up to date with any of the new ones that are released.

Tom Morgan:

Yeah, no, they're really good. And the other thing we talk about user adoption, and I know we primarily talked about the user adoption of agents and supervisors, but if you're a techie person, don't completely zone out because actually user adoption for techies is also a thing. Because, as you know, Amazon Connect is this evergreen service. It is evolving all the time. And so there's a whole thing about how you stay up to date with developments and then how you keep your user base up to date as well. It's all very well. You knowing that this new capability is out. But how do you make sure that your agents and your supervisors know? And in a way that You know, it's trickled down and disseminated in a way that stays in line within your business processes and the way you want your agents to work or your supervisors when your agents to works as a whole, there's a whole process in that, isn't there? There's a whole sort of thing around, not just knowing that the technology is there, but then deciding whether or not you want to use it. And then if you do decide you want to use it, how you're going to use it and then moving operationally to actually using it.

Alex Baker:

Yeah. And probably also some considerations around compliance, for example. So I know that some of the AI tools that are being introduced are great and should improve productivity equally, some, people, maybe legal teams, maybe those in certain countries that have tighter regulations around this kind of thing they're a little bit more nervous about putting them in and you get into maybe talking about what the, the guardrails are behind it or, or what the data usage policy is from the, vendor themselves. So yes, it's, it's good to be informed for that kind of reason. So you can talk to the, whole spectrum of business users, whether it's your, your supervisors, your managers, or, or your, your legal team.

Tom Morgan:

Yeah, yeah, definitely. And it's an ongoing thing. Not to plug it too hard, but we. That's why we have a managed service, right? Because we know it's an ongoing thing and we know it's not a one and done. And so we want that opportunity to come back to service owners and say, Hey, did you know this thing is here? Let's have another review. Like you could do this. You could do that. Here's what's new. And, and so like lean into that with training or evaluations or, you know, other things like that. So but that's why, that's why we have what we have, I think. So, yeah.

Alex Baker:

It's one of the quite fun things that I enjoy about the provision of the managed service to our customers, being able to go in and have those regular sort of touchpoint roadmap type calls and show them, you know, this is something new. I think you'd really benefit from this. It's nice to have that constant trickle of, of new exciting stuff to maybe it's just me being the sort of techie geek that wants to play with all the new stuff. But I think, yeah, that's definitely a, a good interesting part of the role.

Tom Morgan:

Yeah, definitely. Definitely. So user adoption. It's not just for users. It's for everyone. It's ongoing. It's, it's about keeping people involved all the way along. It's about making sure you've got the right people involved to start with. And then figuring out, you know, the right time to tell them. And, and how to do that. And as much as anything else, I think it's, yeah, it's also about fully understanding. the business processes that happen and how you want that to be achieved through whatever the technology is. The technology here almost doesn't matter. You know, it's not, it's, this isn't particularly Amazon connect specific. Although, you know, some of the tools and stuff we've been talking about are things like I'm thinking about Amazon queue. but actually a lot of this is repeatable across different contact centers. But yeah. Trying to bottle that institutional knowledge, I think is really important for user adoption, but also it will stand you in really good stead going, going forward. I think. All right.

Alex Baker:

Silence.

Tom Morgan:

whilst you're there. We'd love it if you would rate and review us. And if you have colleagues that you think would benefit from this content, please let them know to find out more about how cloud interacts can help you on your contact center journey, visit cloud interact. io. We're wrapping this call up now and we'll connect with you next time.

Podcasts we love

Check out these other fine podcasts recommended by us, not an algorithm.

AWS Podcast Artwork

AWS Podcast

Amazon Web Services