The question nobody has asked out loud yet Every Monday the supervisor exports the Queues data to Excel. Every Friday a new workaround gets added. The team keeps making it work. But something has shifted over the last six months: taking calls used to be part of the job, and now it is the job. The Queues app is the obvious default when you turn on Teams calling. For a while it is enough. Then one day it stops being enough, and the honest question has to be answered: are we running a contact center now? We deploy Microsoft Teams calling for customers in more than 90 countries, that is most of our work, so we've watched this transition play out enough times to recognise the pattern. Below are five signs that you've outgrown Queues. No single one is decisive. If two or more describe your normal, it's time to evaluate what comes next. Sign 1: you can't see what's happening right now The supervisor can tell you what happened yesterday, last week, last month. Live is harder. Who is on break right now? Which agent is three minutes into a call that should have ended two minutes ago? How many callers are waiting in the priority queue this minute? The Queues app gives you yesterday's story. A contact center gives you the current one. Supervisor blindness is the earliest and most commonly dismissed sign. Teams work around it for months by messaging each other on Teams: "are you on a call?" That is not supervision, that is coordination-by-chat. Sign 2: your routing logic keeps hitting the ceiling Calls route by queue membership. That is the toolbox. Then one day the business asks: can we send VIP accounts to a different queue? Can overflow roll to the sales team after six rings? Can Dutch callers be routed to Dutch-speaking agents? Can the after-hours path go to a voicemail that auto-transcribes and files a ticket? Can we close one specific queue for a local holiday without closing the others? Each of these is solvable in Queues with a workaround. Stack five workarounds on top of each other and the system is no longer understandable. When someone new joins the team they cannot be onboarded on the routing rules, because the routing rules are tribal knowledge. That is the sign. Sign 3: your agents live in another system all day If the agents spend eighty percent of their day in Salesforce, ServiceNow, TopDesk, Dynamics, or any CRM or ticketing system, Teams is the wrong primary surface. They alt-tab on every call. They copy caller ID into the search bar. They paste notes back from the call. A proper contact-center layer puts the customer record next to the call surface, so the incoming call shows the account, the open ticket, the last conversation. We covered the outbound version of this in the outbound article; the inbound version is the same pattern. Sign 4: what isn't working is invisible Queues data retention is forty-five days. That is enough for week-to-week operations. It is not enough for quarter-to-quarter patterns, seasonal missed-call spikes, IVR drop-offs, agent performance drifts, the Black Friday post-mortem. Once your questions go past a month, you are either exporting to Power BI yourself or you are answering with "we don't know." We went deeper on this in the reporting article. Short version: if you need historical reporting that outlasts forty-five days, you need a platform with real retention or a BI pipeline of your own. Sign 5: the team's job IS answering calls This is the softest sign to articulate and the hardest to deny once you see it. A service desk has twenty people. Eighteen of them spend their day on the phone. The other two supervise, coach, and handle escalations. In that shape, calling is not a feature of the job, it is the job. At that point Queues, which is built to be a useful feature layered on top of Teams for teams that happen to take calls, starts costing real money in attrition, customer complaints, and missed opportunities. Not because Queues is bad; because it is built for a different use case. A proper contact center is built for this one. How to decide None of these signs alone means you need to change tools. Every team has some of sign 1 or sign 4 on a bad day. The question is whether two or more describe your normal. If two or more apply, it's time to evaluate. If only one does, watch it. If zero do, Queues is fine. Stop worrying about it and go solve something else. Most of what we do is help customers run Teams calling well: SBCs, Operator Connect, routing, the full Teams Phone deployment. For the teams that have outgrown Queues and need a layer on top, we also build Purple+, one of the contact-center options at Level 4. Other platforms cover other shapes. Get in touch if you want to talk through where your team sits today.