AVinBrief

The commercial AV industry, in briefs you can read in under a minute.

← All briefs

Corporate · July 14, 2026

Google Meet Hardware Gets Structured In-Room Problem Reporting and New Admin Console Monitoring Tools

Context-aware user feedback and two new admin dashboard columns replace generic telemetry for enrolled Meet hardware devices.

By AVinBrief Editorial Desk · · Updated August 12, 2026

What changed for users reporting a problem from a Google Meet hardware device?
The feedback menu on Meet hardware touchscreens now surfaces context-aware options based on the device's current state rather than a single generic form. In a call, users see options such as "Can't see others" and "Poor audio or video quality." From the touchscreen landing page outside a call, the menu shifts to join-related problems, including "Can't join Meet call" and "Can't join Teams call." During a large-scale livestream, a separate set of dedicated report options appears. The prior experience sent unstructured feedback regardless of context.
What did Google change on the admin console side?
Feedback is no longer routed as a background telemetry event; it now appears as a primary, sortable column in the device list. Google added two columns. "Last feedback submitted" is a sortable timestamp filterable by 1, 3, 7, or 30 days, with a click-through side panel that shows the specific details of that report. "Feedback in the last 28 days" is a rolling cumulative count of reports per device. A new "With feedback in last 7 days" filter surfaces problem devices immediately and repositions the feedback columns adjacent to the device name in the list view.
What does an IT admin need to do before any of this works?
The "Let users send feedback to Google" checkbox must be enabled in Google Meet hardware Settings under Data Sharing, set to on at the domain or organizational unit level where the device is enrolled. If that setting is off, no user-submitted feedback reaches the admin console regardless of which reporting options appear on the device touchscreen.
Which devices are covered, and when does the rollout complete?
The update applies to all enrolled Google Meet hardware devices across all Google Workspace customers. Google is rolling it out gradually across both Rapid Release and Scheduled Release domains starting July 14, 2026, with full feature visibility expected within 15 days of that date.
The out-of-call feedback menu includes a "Can't join Teams call" option. What does that indicate about the hardware's interoperability posture?
The presence of a dedicated Teams join-failure option in the out-of-call feedback menu confirms that Microsoft Teams interoperability remains a supported use case on Google Meet hardware: a configuration where the same room device can be used to join either a Google Meet or a Teams call. Building Teams-specific failure reporting into the structured feedback menu signals that Google treats the interoperability path as a production-grade scenario, not a fringe configuration.

The Take

What does this update tell IT admins managing large Google Meet hardware fleets about where Google is taking room-device operations?

The shift from background telemetry to a primary, sortable admin column is a small schema change with a meaningful operational consequence. Until now, an admin who wanted to know which room devices had been generating complaints had to correlate unstructured telemetry events against support tickets: work that typically didn’t get done until a user escalated a problem. The 28-day rolling count and the 7-day filter together create something closer to a recurring-fault dashboard. A device that shows eight reports over 28 days is a different problem than one with a single report yesterday, and the console now makes that distinction visible at a glance.

IT admins face a choice about whether to send feedback from a Google Meet hardware device directly to Google to enable these features. Confirm the current terms and conditions with the vendor first, because the feedback can include diagnostic data, device logs, and a screenshot of whatever is on the display. That content could be sensitive, including shared documents, participant names, calendar details, image and likeness, and other material the organization considers confidential. Users may also struggle to tell a hardware issue (which a ticket with Google could legitimately help) from a software issue (which in some cases should go to Microsoft), which lowers the payoff on the privacy exposure.

For IT admins managing fleets across multiple buildings or campuses, the question worth bringing to the next device review is whether the 28-day window is the right detection interval for their environment. A room that’s lightly used, for instance a small huddle space booked twice a week, might accumulate the same raw count as a heavily used executive boardroom, while representing a much higher problem rate per session. Google does not appear to surface a per-session rate, only a raw count. Admins who need that granularity will still need to cross-reference the feedback data with room utilization data from their booking system and run their own analysis.

Sources