Teams Queues Shared Call History Goes GA: Setup, 45-Day Reports, Mobile Support and Premium Trial

To be clear about what this is: it isn't a new contact-center product. It's an upgrade for the call queues many organizations already run in Teams. Microsoft aims it at teams that take customer calls on top of their other work, like bank branches serving outside customers or IT help desks serving staff.

What actually changed​

Shared call history is generally available​

Microsoft calls this the biggest change. Shared call history is now generally available. Instead of each representative seeing only their own calls, the queue gets a unified view of missed, incoming, and outgoing calls along with voicemails. Admins decide who sees it: access to shared history can be configured for all queue members or restricted to authorized users.

The feature has been on its way for a while. A Message Center notice from November 2025 (MC1188999) said it would roll out January–February 2026, disabled by default, and requiring a Teams Premium license and admin enablement. Roadmap trackers show item 530579 moved from Rolling out to Launched on 2026-02-18. So the September post confirms general availability rather than introducing the feature from scratch.

Microsoft Learn's planning documentation lists what shared history shows:

• Missed calls, including callers who hang up and callers sent to shared voicemail after a timeout, overflow or the no-agents treatment
• Shared voicemails
• The status of each call log
• Call times and duration
• Call participants

There's also a size limit. Microsoft's documentation says the feature keeps up to 3,000 entries or six months of calls per call queue, whichever comes first.

Status labels for follow-ups​

Representatives and supervisors can now mark a missed call or voicemail as Unresolved, In progress or Resolved. Think of it as a shared "I've got this" flag. Someone starting a shift can filter for Unresolved calls, and nobody phones a customer who's already being helped.

Keep expectations realistic. These are status tags on call-log entries inside the Queues app. They aren't a CRM case system. A call marked Resolved means someone clicked Resolved, not that the customer is happy.

Reporting goes from 30 to 45 days​

Supervisors and approved viewers can now look back over 45 days of call-history reporting, up from 30. One catch, noted by 4sysops: reports still open to the most recent 7 days by default, so you have to widen the date range yourself to see all 45 days.

It's easy to confuse this with shared call history, but they're separate tools. The reporting shows aggregate data such as call volume and wait times for staffing decisions, not individual customers to follow up. Microsoft Learn adds one detail that matters for anyone building staffing charts: historical metrics are reported in UTC, while real-time metrics use the signed-in user's local time zone. A branch in Chicago or Sydney may find that a "Monday" in the report doesn't line up with its local Monday.

Team leads get more control​

Authorized users, such as supervisors and team leads, can change key call queue settings directly in Teams. That means fewer tickets to IT for routine tweaks. Microsoft Learn says authorized users don't need access to the Teams admin center or a Teams Administrator role. Depending on what they're allowed to do, they can:

• Configure call routing for business hours, after hours and holidays
• Manage queue membership, routing method, presence-based routing and exception handling
• Use real-time and historical reporting
• Monitor, whisper, barge in on or take over agent calls, if their policy allows it

This works through permissions, not a master key. Admins create voice applications policies and assign them to users. You might give a "team supervisor" policy both real-time and historical reporting, and give a "shift lead" policy real-time reporting plus the ability to opt agents in and out of queues.

Teams mobile support​

Representatives can stay opted into their queue, check recent calls and call back missed customers from a phone. That helps staff on a shop floor, in a branch or traveling between sites. Microsoft Learn currently lists the Queues app as supported on Teams desktop, Mac, VDI, touch-screen Teams phones, and iOS and Android. It does not list web clients.

The older Message Center text described affected organizations as those using the app on desktop, web, and Mac. That conflicts with Microsoft Learn. Treat the current Learn page, which says web isn't supported, as the authority.

Section summary: Shared history and status tags help your team follow up together. Reports covering 45 days support staffing decisions. Authorized users take routine changes off IT's plate, and mobile support covers staff who aren't at a desk.

How to turn on shared call history​

Microsoft's setup documentation says the call queue must have Conference mode enabled first. After that, there are two steps.

Create the template:

1. In the Microsoft Teams admin center, go to Voice > Templates and resources.
2. Select Templates, then choose Shared call history as the template type.
3. Select Add, then enter a name and description.
4. Set the permission level for Incoming missed calls.
5. Set the permission level for Answered and outbound calls.
6. Select Save.

Assign it to a queue:

1. In the Teams admin center, go to Voice > Call queues.
2. Select the queue.
3. On the General info tab, find the Shared call history template section.
4. Pick the template from the dropdown and select Submit.

Microsoft's setup page also notes that assigning templates to a call queue moved to a new Templates step in August 2026. If your admin center looks a little different from the steps above, check there.

If you'd rather use PowerShell, Microsoft documents cmdlets such as New-CsSharedCallQueueHistoryTemplate -Name "Everyone – Missed call history" -Description "Everyone sees missed call history" -IncomingMissedCalls AuthorizedUsersAndAgents. Use AuthorizedUsersOnly to limit missed-call history to supervisors.

What success looks like: a representative opens the Queues app, joins the queue and sees new queue calls in History, with an option to set a status on each one. Independent walkthroughs report the same thing: new calls will now be visible in the History.

If it doesn't work, check these:

• The app isn't showing up. Microsoft Learn says Queues app users need Teams Phone and Teams Premium licenses. After you license a user for Teams Premium, the app can take up to 48 hours to appear.
• A user can't see the queue. They must be a member of at least one call queue. The limit is 200 agents per queue, and Microsoft recommends no more than 100 queues per user, with a hard limit of 200.
• A call is logged in the wrong queue. If queue A's overflow, timeout or no-agents handling sends a call to queue B, Microsoft Learn says the history belongs to queue B.
• A team lead can't edit a nested queue. Authorized users can't edit nested auto attendants or call queues that don't have a resource account.
• History disappeared after a region move. The original notice warned that if your organization moves to a new region, existing history will not transfer; a new history will begin.
• You use automatic call recording. As of August 2026, Clerk.chat reported that assigning a template or managing authorized users on a queue that uses one requires the Teams administrator to also be a SharePoint site administrator for that site.

The trial and discount: read the fine print​

This part of the announcement is a sales offer, and the conditions are strict.

Three practical points:

1. Trial licenses start expiring when you redeem them, not when you assign them. Redeeming before your agents are ready wastes trial days.
2. The discount depends on usage. Assign the trial licenses to people who actually work the queue, or you may miss the threshold.
3. No Message Center post means no offer. Searching harder won't change that. Microsoft also says licensing, pricing and service limits may change.

Microsoft also mentions an adoption view in the Teams Premium usage dashboard in the Teams admin center. It's still rolling out, so confirm it's in your tenant before you plan to measure the trial with it.

Analysis: who should care?​

The upside is clear. Many small help desks and branch teams don't need, and can't justify, a full contact-center platform. A shared list of missed calls plus Unresolved, In progress and Resolved tags fixes one of the most common queue problems: customers who never get a call back.

There are a few counterpoints. All of this sits behind Teams Premium, on top of Teams Phone. That's why Microsoft is pairing the announcement with a trial and a discount. Shared history also raises privacy questions in settings like healthcare clinics, where colleagues could see call participants and voicemails. The template's split permissions for missed calls and for answered and outbound calls let you share less, so use them. And status tags only help if everyone uses them. If half the team skips them, the shared list soon becomes as unreliable as the sticky note.

Here's a sensible plan for an eligible organization. Check the Message Center terms and your license count. Confirm Teams Phone entitlements and Conference mode. Turn on shared history only for queues that need it. Set up authorized-user policies on purpose, not as a free-for-all. Then use the trial to answer three questions: do status tags cut down on repeat callbacks, does the 45-day UTC reporting change how you staff, and do mobile callbacks suit your frontline staff?

Bottom line: For teams already on Teams Phone, this is a useful, practical update. The trial is a fair way to test it, as long as you track license expiry and usage carefully.