Microsoft Teams Insider
Microsoft Teams discussions with industry experts sharing their thoughts and insights with Tom Arbuthnot of Empowering.Cloud. Podcast not affiliated, associated with, or endorsed by Microsoft.
Microsoft Teams Insider
Inside Microsoft Teams Queues App: New AI Features and Advanced Call Handling
Use Left/Right to seek, Home/End to jump to start or end. Hold shift to jump forward or backward.
Sean Gilmour, Principal Lead PM, Advanced Calling Experiences, Microsoft Teams, at Microsoft, returns to the podcast to share the latest updates to the Queues App for Microsoft Teams.
• New capabilities including auto-recording, intelligent recap and Copilot for call queue calls
• Shared call history enhancements and expanded monitor, whisper and barge features for supervisors
• Mobile-first workforce support, with the Queues App and key features now expanding to mobile devices
• The 90-day Microsoft Teams Premium trial for call queue tenants, with a 50% discount for qualifying organisations
• How Teams Phone Agent integrates with the Queues App, passing context from AI interactions to human agents
• The Unify model and Microsoft Teams Phone extensibility, including support for third-party intelligent IVRs
• ACS deprecation and what it means for the Microsoft Teams Phone ecosystem
Thanks to Shure, this episode's sponsor, for their continued support of Empowering.Cloud.
You know, we're also looking on our side, you know, we support app extensibility in calls and in, in call queue calls. So if you do have, you know, a knowledge base or a ticketing system, you can have that available. And then we're also thinking about what does that look like after a call, right? How do we, you know, support things like wrap time and wrap up and make sure that there's continuities to systems of record, uh, because those are really critical for businesses, whether it's, um, CRMs or ticketing systems or electronic health records for that matter. We also wanna look at how we create that continuity through to those systems. Welcome back to the podcast. This week, we are talking all about the Queues app, some of the new features that have come along, and some of the roadmap as well. Many thanks to Sean for jumping on the podcast again and giving us some real insight. And many thanks to Shure, who are the sponsor of this podcast. Really appreciate all their support to the community. On with the show. Hey, everybody. Welcome back to the show. Uh, a lot going on in the Microsoft Teams voice space as always. Um, as we record this, we're just coming off the back of Fireside Chat talking about Teams Phone Agent, uh, which is now GA. Um, and another area of the product that has been getting a lot of love and, uh, new features is the Queues app. Um, we've got Sean. Uh, you've been on the podcast, uh, I think multiple times before now. You're practically a regular, Sean. I know. I mean, it feels like I should just, you know, get a podcast mic and, and, uh, be all set and just join you every week- I think so. I think so … whatever the topic is. Um, so- Might be awkward for some of our competitors. Yeah. Yeah. Just, just, just, just, just whatever we're talking about, just wedge your product into the conversation- Yeah … I think is the right answer. Be perfect. Yeah. But how about with the Queues app? Yeah. So Queues app, last time you were on the podcast we were talking about some of the features that were coming. Now a lot of those capabilities have landed. Uh, the recording is particularly interesting, the recaps. Can you take us through some of the features that have dropped and kind of the use cases? Yeah, no, absolutely. Um, it's sort of interesting. There are so many that I actually wrote myself a little list. Um, I didn't wanna… I didn't wanna miss any, uh, specifically. So yeah, I mean, um, you know, last time I think we talked, we had just landed shared call history, which is a big, uh, piece of the overall story for us in the way the Queues app is expected to work, and then we followed with auto-recording, and now we've added, um, recap and copilot, uh, to shared call history to go along with that, and then started to sort of fill in other features. Uh, for example, with monitor whisper barge, we've added, um, monitor, uh, outgoing call and monitor active agent. Uh, so that was a big gap in what we provided before. Um, we've also added bulk opt-in, which was a mobile feature that we've moved over to the desktop based on customer feedback, and then we're also building out, um, features on the Queues app on mobile. So we shipped Queues app on mobile, uh, in the, you know, early summer, and now we're gonna be adding, um, shared call history to the mobile Queues app, as well as recap and copilot. So we're trying to ensure that both, uh, end points are sort of very full-featured products, and that's partly to do with the kind of mix we're starting to see with the, the users, right? When we, when we talk about, uh, the sort of, um, uh, citizen agent- You know, in frontline and, and different industries. Some of those are mobile first or mobile only. Um, as we talk a lot, uh, in healthcare, a lot of those organizations, as their digital transformation starts, are moving to mobile only workforces. Um, and that's taken us, um, a little bit by surprise on the calling side. Uh, for a very long time, Teams, the mobile device was considered a companion device. You always have a desktop, so you'd always invest in, you know, the fullest features and this, you know, setting capabilities on desktop, 'cause someone would have the ability to set forwarding targets or create call groups, uh, in that space. And now that's not true. You've got, uh, users that are only using a mobile device. Um, and so we're- Yeah, that's a, that's a very knowledge work outlook, isn't it? It is. We're lucky something that we, like I feel I suffer from when I talk about product- Mm-hmm … and, and Microsoft suffer from because th- that's a bulk of the audience. But with- Mm-hmm… 320 million users, you've got every, those that are- Yeah … you know, just, you, you see Ilya running around with the iPad a lot, like, like as a, as a device and like, you say mobile in security teams or, or healthcare- Yeah … is, is a big one as well. Yeah. And so you'll also start to see as we move and push for, um, parity in these spaces, you will start to see where we look at what has worked best in a given, um, format and, and see if it translates well. And that's where, for example, bulk opt-in is very much built around a mobile workforce where you're, you know, literally on the go as a supervisor and you're sort of like, "Oh, I need to get all of these people in." And then we got all this feedback like, "Well, why can't we do that on desktop?" I'm like,"Well, we can do that on desktop, too." Um, so it's great. And then you'll also start to see things like, um, you know, deeper, richer settings experiences coming to mobile, um, things like creation of call groups, um, which seems simple and maybe like, oh, this is a very niche feature, but we have customers who are like, "We can't deploy," right?"Because, you know, our head nurse needs to make sure that the phones ring for everyone in her group, and she doesn't have anything but a phone." Um, that makes a big difference in, in, uh, making sure that these customers can actually sort of finish their journey. Um, and then we'll als- we're also, you know, sort of surprising to us, uh, is there's a lot of supervisors on mobile devices. And so, um, y- we had prioritized many of the sort of analytics side of things. Real-time analytics is also coming to mobile, um, relatively soon, and now we're looking at, what does authorized user setting access look like on mobile? Can you manage, um, all of the call queue settings, all of the auto attendant settings, and things of that nature from mobile? So moving your entire workforce into a mobile space. So it's a, it's a fun journey. Uh, it's great. It's great to see the investments that we're able to make across all of it to sort of bring this to life. Um, and partly because- The other big thing that we just launched last month, uh, was a trial, an extended trial of Teams Premium, uh, for call queue, uh, tenants th- that want to try it out and, uh, give it a go for 90 days. Uh, so it's a 90-day trial, um, and you'd have gotten an MC post with a customized link that lets you go and redeem these licenses, um, for the number of agents you want to in your organization. And then even better, uh, if during those 90 days, 50% of those licenses that, uh, you've taken or, uh, 50% of the agents that qualify have used this Teams Premium license, it's whichever one's less. Um, so, you know, if it's, you know, fewer licenses than call queue agents, but you've used 50% of them, or 50% of the agents, uh, that you have in-house have used them, then we're gonna offer you a 50% discount on Teams Premium licenses, um, the number that we offered you for the trial. So it's a nice ability to test it out and really see if those, um, workflows and all the capabilities work for your organization, and you can sort of fit it to, to your needs. And then if it does work out for you, giving the ability to, to move into Teams Premium permanently with this discount. Yeah, I think that's really great. 90 days is a great window as well. Like, sometimes these trials are, are terribly short. Yes. And I guess by the time you thought your… thought, thought through your use cases and you wanna use it in the real world, uh- Mm-hmm and I think for Teams it's particularly interesting 'cause you can obviously relatively easily move numbers around in the sense of you might just be using regular call queues today. This is a great way- Mm-hmm … to step up and see what it is. But also, if you've got a different contact center, you might actually take some numbers and fork them over to Teams for a while and be like, "Oh, actually, maybe I don't need all the features for this particular scenario- Mm for my helpdesk team, for my internal HR- Mm … for my security team." Um- Yeah… if it doesn't fit, you can still redirect that number back, but you've got a good opportunity to really see how it works over a, a decent business period of time. Yeah, absolutely. And along with that sort of 90-day window to use it and to try the trial, we actually have a pretty large window to redeem it, to start that 90-day trial. So, um, you have until the middle of December, I think December 14th, um, which is three months after the date that we launched the trial. So you have that time also to sort of plan and understand how you might use it in your organization, and then do the deployment rather than like, "Okay, take advantage of it within this week and go." Yeah, yeah, yeah. Right? You, you… It's getting- So- It's g- it's getting to the end of the quarter. We've realized we want some more licenses. You've got seven days to test this out and make a business decision. Exa- Exactly. Yeah. We're… You know, I think there's an understanding on our side that- The, the administration of Phone isn't something you're just like click and it, and it, and it's done, right? It is something that you're gonna be thoughtful about, that you're gonna be, um, mindful and planful about because it is a big step for an organization, and it's also a complicated step. And so we also wanted to give that breathing room to, to try and adapt. And like you said, do you wanna try it for an internal help desk team that you maybe are using a contact center for and maybe it's overkill, uh, for all the capabilities you have? Um, so and, you know, along with that I think comes along with the promise of us continuing to invest in that space. So there, I'm sure I'll be back hopefully in another few months, and I'll have even more features, uh, to talk about having it released and in the pipeline for us moving forward. Some interesting stuff with AI in that space, some interesting stuff with, um, deeper integrations with Teams, um, and the ability to know when certain activities have happened, like when missed calls have come in and voicemails and things like that. So lots of stuff on the horizon as well. Oh, it's exciting. There's a lot, there's a lot there around now you've got the recording in play and you've got the data. Mm-hmm. You can see some interesting potential. Um- Yeah … maybe that's a good point to talk about the Teams Phone Agent. I know that's a different team, but like- Yeah there's a sort of better together story there with- Mm-hmm … Teams Phone Agent routing into call queues and, and, and the, um, call queues app. Yeah, absolutely. There's a couple of, of pieces we think about it. Obviously, Teams Phone Agent is a great, um, set of capabilities to sort of front, um, a set of call queues, right? And it can take, uh, a burden off that call queue team of sort of answering rote questions and, and relatively simple Q&A, um, as well as, say, booking appointments and sort of managing, uh, calendars and that aspect. Um, but then if you do need to go and escalate to a human agent, we will take all of that context, uh, that's been gathered during that, what the interactions were with Teams Phone Agent, and pass that through into the call queue, so when the agent answers the phone, they don't start dry, they don't start cold. They actually start with a knowledge of what the customer has talked through and what it's about. And that, that's so key. It's a horrible experience to- Mm-hmm … put a bunch of information or tell an IVR in case of AI. Yeah. And like, h- honestly, Mahendra was talking about 60, 70% deflection rates depending on the use case. Mm-hmm. So sometimes the AI's gonna handle it outright. But when you get to a person, at that point you very much don't want to repeat yourself. Like, it's, "This is what I need- So true … and this is why I need it." Yeah, so true, and it's so important. We think about context as really being, you know, the core of the sort of continuity of a call, right? Um, we also shipped earlier this year, um, Copilot recap on transfer in call queues, so the ability to actually leverage, um, that auto recording that you've got with Copilot during a call to then generate a recap for transfer to another agent, and that happens a lot, right? There's often transfers to individuals or other call queues, um, in, in the flow of work. And so we think about that context coming in, um, from Teams Phone Agent, uh, and introducing itself into the agent, uh, that's answering that call. Um, and then, you know, there's also a set of analytics that are coming in to, to the Queues app around, um, Teams Phone Agent. Uh, s- I'm struggling to not call it Mainline Attendant, 'cause we did for so long internally, um, and use the actual, uh, official name. Um, but, uh, we're, we're building a whole sort of rich set of, uh, analytics in there, and those will continue to grow. We see, um, Queues as a very natural home for- the capabilities, uh, that Teams Phone Agent brings. And, and also, you know, even sort of normal auto attendance. So the other thing that you get along with this is if it's off hours, it can still route to voicemail, and we've built, um, an- an- you know, the set of capabilities in the Queues app for supporting voicemails for Teams Phone Agent and normal auto attendance. So you don't have to go in, into Outlook, into the shared Outlook inbox to go and see those anymore. You actually have a place in Teams to manage those. Um, and the amount of analytics and the amount of historic data that we flow into there will continue to grow. And then, you know, we're also working through, as everyone else is, um A bit of the maker persona in this space, right? So Teams Phone agents will get more robust in the capabilities that they provide. Obviously, we are working now, and I'm sure Mahendra and Michael talked about the integration with MCS and how we wanna sort of bring more in that space. Um, but it, uh, the agent itself will get more robust in the capabilities and the way you can tune it and, and, um, shape it. And we're thinking about, how does that translate to authorized users, right? Um, how does that become an experience that an admin can offload to the expertise that, you know, works in the, the queue day to day and works with Teams Phone agent day to day, as opposed to being like, "Well, I've got all of these Teams Phone agents, and I don't know what that billing department does, and I don't know how to make this properly." So how do we build those kinds of maker experiences for… so the expertise can really come into bear. Yeah. It- So those are also additions… it's a tricky one with Teams it's so powerful and extensible. You've got kind of the, the basic capabilities in the Teams Admin Center- Mm-hmm which does give you a good start of a turn of, like, I can set up a knowledge base, and I can- Mm-hmm… set up bookings, but then you're into more technical, and then- Mm-hmm … you can get right into Unify and Foundry and Ecosystem if you wanna go down that route. So you've got- For sure uh, to help explain everything that's going on to your admin or potentially there's scenarios where partners are in play building part of the puzzle. It would be great- Mm-hmm … to give the custom- the end customer, like,"Here's what's going on with…" 'cause there's gonna be multiple agents."Here's what's going on with all the agents. Here's the-" Yeah … "here's the usage. Here's the use cases. Here's the cost model-" Yeah … all of that stuff. But even simple things, right? When we think about knowledge bases, the team that's best h- you know, in place to handle updating knowledge bases, you know, informing the question-and-answer pairs that need to be added there, helping to sort of lift the burden off of their shoulders, is the supervisors and the call queue agents themselves. Mm-hmm. So being able to think about how we create experiences for them to help keep those up to date, to also understand what is the Teams Phone agent unable to answer today? What are the kinds of escalations we're getting, right? Those are the kinds of analytics we need to work through as well. It's a entirely different world, um, for us in some ways, so you can imagine, uh, we're working through and trying to figure out what those experiences look like. But yeah, lots more coming. Awesome. Yeah, excited for, uh, for what's coming. This is… It's a, it, it's a new space to everybody working with, uh- Mm-hmm… AI and the data and the Yeah, for sure. And then, you know, I think the other thing that we think about as we, uh, work through this is that better together story with contact center, and that's, you know, for us, the best way to do that is the Unify model, right? Taking Teams Phone and the capabilities there and leveraging them in the contact center space. Um, but we're also looking at how Unify broadens out, right? Um, Teams Phone Agent is our homegrown, uh, telephony sort of fronting agent that we love and, and continue to invest in. But we also understand that our, our customers are not homogeneous. They're not always pure Microsoft shops, right? They may wanna go to third-party intelligent IVRs. And so we're working, you know, busily with those, those customers to leverage the Unify model to be able to front, um, you know, uh, call queues, um, or other rich endpoints, uh, with an intelligent IVR. And in the same way that Teams Phone Agent can pass context, we're also providing that capability for these third-party IVRs to pass that context through, and that context can go to any Teams Phone extensibility endpoint. So, whether it's a contact center or queues, uh, app Call queue. You can imagine a world where that intelligent IVR is making decisions on where these things should go, um, based on the capabilities, the skills, availability, things of that nature, and then routing that through- Yeah, that's- … and it just becomes this whole, uh, scenario. Yeah, that's really nice to hear because I think absolutely, like, there will be… There's various people in this space, including all the ecosystem partners, and there'll be- Mm-hmm… some very specialist agent that somebody And the fact that- Yeah … you're already thinking through how you can route between these systems. So it might be- Mm-hmm … Teams' own agent fronts it, and it goes off to the specialist agent. It might be the specialist agent fronts it, and actually it's just an internal basic call for IT helpdesk, and that then goes off to Teams' own agent. Um- Yeah … the, the fact that we'll be able to go in all directions is really nice. Yeah. To me, to us, it's really important, um, that we sort of embrace and extend, uh, this whole set of capabilities. Um, you know, I think at its heart, Microsoft's always been a platform company, so we love to build products, um, but we also love to build products that can help others build products and build on top of, of what we're building. And we also know that, to your point, we're not gonna be able to serve every piece of the puzzle, right? There are lots of very, um, niche spaces, and given the way, you know, Microsoft looks at its business, you know, if we don't see the volume there, then we won't necessarily do everything that, that a… that place might need, and that's where third parties come in, right? Um, where you can do these sort of very, um, customized, bespoke, rich experiences, but then plug into, you know, whether it's the Queues app, Dynamics or another third-party contact center, and be able to service those and blend those across. And, you know, we're also looking on our side, you know, we support, um, app extensibility in calls and in, in call queue calls. So if you do have, you know, a knowledge base or a ticketing system, you can have that available. And then we're also thinking about what does that look like after a call, right? How do we, you know, support things like wrap time and wrap up and make sure that there's continuities to systems of record? Uh, because those are really critical for businesses, whether it's, um, CRMs or ticketing systems or electronic health records for that matter. We also wanna look at how we create that continuity through to those systems, um, because they're critical systems, and, you know, uh, despite what maybe some people would think, um, we are not interested in the Teams side building ticketing systems or electronic health systems or things of that nature. Um, those, those aren't where, where we're gonna spend our time, but we know that they're critically important for our businesses that, that rely on us, and so we're also looking at how we sort of support that continuity and at that throughput across the board. That's great. And, and talking of Unify, we've now heard that, um, Microsoft are kind of moving away from ACS and the CPaaS side. How, how does that affect us on the Unify Teams Phone side? It doesn't really, um, other than we will obviously look for spaces where ACS was covering a set of capabilities that we wanna continue, um, and provide those capabilities and look at ways that we light that up with Teams Phone extensibility. Um, you know, a long time ago as we started the work towards Teams Phone extensibility, um, we called the effort One Phone System, and it really was sort of, hey, we're starting to build this trend towards two unique phone systems, one in ACS and one in Teams Phone. And that was at some level hard because it's not like we had the warships have spent resources to build two entirely separate phone systems, and it didn't necessarily fulfill all of the needs our customers wanted. Um, and so we sort of focused a lot of efforts in the Teams Phone extensibility. Um, and then, you know, the decision was made to deprecate ACS. And so then we're also looking at, okay, well, what are those capabilities in the ACS side that we wanna ensure there's continuity on the Teams Phone extensibility side? We're working really, really closely with the team that's driving that deprecation. It's a very thoughtful team. They're trying to approach it in a very thorough way. It's two years of runway for folks to move off of it. Um, but we're also ensuring that as we talk with our customers and we talk with our partners that have been leveraging it, that we, you know, talk with them and integrate the feedback and the needs that they may have had with ACS. Um, but the Teams Phone components themselves aren't going away. Um, we continue to offer, you know, the Teams Phone extensibility side of it in a rich way. We'll continue to build it out and provide capabilities there. And, you know, hopefully that, you know, long window around the deprecation and the continued engagement of the engineering team as we move forward on that, that will help ease this journey and make it so the transition is a smooth one for our customers, um, and their customers, right? We understand their customers are our customers, and so we don't wanna leave anyone in the lurch. So we continue to sort of work, um, to make that as smooth and as seamless as possible. Yeah. I ap-appreciate it was a, a, a very long deprecation window. And obviously- Mm-hmm … I, I speak to a lot of the ecosystem vendors, and there are some that have, you know, used various pieces of ACS, and it's generally been pretty, uh, positive around. We've got a big window. The team are working closely- Yeah … with us. Um, but it's nice to kind of say in here out loud that the, the Unify side and, and all the Teams Phone agent and extensibility side, that obviously still carries on. And of course, you're supporting all the stuff the D365 Contact Center team are doing as well. Mm-hmm. So kind of there's, there's the Teams dependency on that infrastructure and the D365 Teams dependency on that infrastructure as well. Yeah, absolutely. Uh, D365 has been a pretty invaluable partner with us as we've developed Teams Phone extensibility in the Unify model. Um, you know, we work with them and, you know, some of our leading third-party contact center solution providers to really build that system and sort of come to, to like what, what do you really need if Teams Phone is gonna be providing, um, these sort of, uh, resource numbers for you to be leveraged in, in a way that's effective. And so yeah, Dynamics has been really great and, and then those third-party partners have been really good. Um, and the team that owns the ACS deprecation, um, really strong set of engineers that are actually s- you know, contributing to Teams Phone now, but are also looking at how we light up some of those pieces that maybe are, are going away with ACS on our side to, to continue to support them. Awesome. Well, Sean, thanks so much for, uh, catching us up on everything Queues app. We'll share the link to the, the details for the, the trial. Um- Great … yeah, I think this is a great window if you're a, a customer who's already using… Certainly if you're already using regular call queues to, uh, try out some of these capabilities, and, uh, I'm excited to hear more when we can talk more about the, uh, the, the even newer things that you've got planned. So, uh, yeah, we'll definitely have you back when, when the time's right to talk more. Yeah. Thanks a, thanks a ton, Tom. I really appreciate every time I can come on, and hopefully marketing will let me come back. I haven't spilled the beans too much on some stuff. Uh, trying to be a little subtle, but they might catch on. We'll see. Yeah. Let's see if Johnny tells me off or not. We'll see, right? I'm the one that's more at risk. Yeah, that's true. He can fire me. That's true. He's in my office all the time. I'll be, I'll be running away. Awesome. Well, thanks so much, mate. Absolutely.