Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 271/272 feeds/APIs · 469/469 docs · 8/9 advisories · checked 16:49 UTC Customize Public modeDiscuss ChangeIntel on Discord

Rate my call feedback experience update in Microsoft Teams

From Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.

Rollout

Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".

Schedule dates changed in the text

Date phrases in schedule sentences differ between the versions this installation saw
  • Seen 28 Jan 2026 late January 2026 → mid-February 2026, late February 2026
  • Seen 4 Dec 2025 early December 2025, mid-December 2025 → late January 2026
  • Seen 19 Nov 2025 mid-November 2025, late November 2025 → early December 2025, mid-December 2025

Read from date phrases in Microsoft's text, not from notice metadata. A changed phrase can be a moved rollout, a new milestone or just rewording; "What changed" below shows which.

What the notice says

Microsoft’s text, safely structured

Updated January 28, 2026: We have updated the timeline. Thank you for your patience.

Introduction

The Rate My Call survey is a feedback screen that the Teams client will occasionally present to users after their Teams call or meeting has completed. Currently, the rating presents 1-5 stars on the first page and a list of potential issues (called problem tokens) on the second page.

We will be rolling out a new streamlined feedback experience for Teams on Windows, Mac, and Web that presents the feedback on a single screen with a thumbs up / thumbs down rating system and problem tokens for the user to select, plus an area to provide details. In testing, we found higher feedback returns with this new design, and clearer insights into call quality issues.

Screenshot 1: New Rate My Call User Interface

When this will happen

  • General Availability/Targeted Release: Rollout begins mid-February 2026 (previously late January), completes by late February 2026 (previously late January).

How this affects your organization

Who is affected: Users of Microsoft Teams on Windows desktop, Mac, and Web clients

What will happen

  • Users will see a new Rate My Call screen after calls and meetings
  • The new screen includes:
    • Thumbs up / thumbs down rating
    • Optional problem tokens
    • Optional free-text field for additional details
  • Feedback Rating values in Call Quality Dashboard (CQD) will change:
    • 5: Thumbs up / Good
    • 1: Thumbs down / Had issues
    • 0: Survey shown but not submitted
    • Null: Survey not shown
  • Problem tokens will still be recorded even if a rating (thumbs up or down) is not submitted
  • Admins may notice an increase in poor feedback metrics due to the new rating method; this does not reflect a decline in service quality

What you can do to prepare

  • Communicate this change to helpdesk and support staff
  • Update internal documentation to reflect the new feedback format
  • Monitor PCR (Poor Call Rate) telemetry until it stabilizes, then set your own threshold

Compliance considerations

No compliance considerations identified, review as appropriate for your organization.

FAQ

Q: Will a higher PCR mean calls are worse? A: No. The new design captures more dissatisfied users by reporting a higher willingness to report poor calls. The increase is a measurement effect, not a quality regression.

Q: What is the new PCR target or threshold for your workstreams? A: We cannot provide a fixed PCR threshold. Your action is to monitor your own PCR telemetry until it stabilizes (both volume and value relatively flat), then set your threshold. Stabilization may take weeks and once the data converges, you can then set your own.

What changed

Between archive captures, newest first
  1. Updated December 11, 2025:January 28, 2026: We have updated the timeline. Thank you for your patience.  Introduction The … Call User Interface When this will happen: General Availability/Targeted Release: Rollout begins late January mid-February 2026 (previously early December 2025), late January), completes by late JanuaryFebruary 2026 (previously mid-December 2025).late January). How this affects your organization: Who is affected: Users of Microsoft Teams …

  2. Updated December 4,11, 2025: We have updated the timeline. Thank you for your patience.  Introduction … Screenshot 1: New Rate My Call User Interface When this will happen: TargetedGeneral Availability/Targeted Release: Rollout begins late January 2026 (previously early December 2025), completes by …

  3. Updated November 19,December 4, 2025: We have updated the timeline. Thank you for your patience.  Introduction … My Call User Interface When this will happen: Targeted Release: Rollout begins early December 2025late January 2026 (previously mid-November),early December 2025), completes by mid-December 2025late January 2026 (previously late November).mid-December 2025). How this affects your organization: Who is affected: Users of Microsoft Teams …

    • Tags Feature update, User impact → Updated message, Feature update, User impact

    Updated November 19, 2025: We have updated the timeline. Thank you for your patience.  Introduction The Rate My Call survey is a feedback screen that the … My Call User Interface When this will happen: Targeted Release: Rollout begins mid-November 2025,early December 2025 (previously mid-November), completes by mid-December 2025 (previously late November 2025November). How this affects your organization: Who is affected: Users of Microsoft Teams …

  4. · first version seen

Learn more

Links from the notice and their documentation checks

No related evidence found in this installation's recent collection. This does not establish that no announcement exists.

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 27 Oct 16:49 UTC · 271 of 272 readable · 269 fully read · documentation 469/469 current