Google Meet’s Report a problem feature sends feedback about the product experience. Choose the description and optional screenshot deliberately, because meeting screens can contain private names, chat, and presented material. Google’s guidance also says additional details such as browser logs are automatically included, subject to Workspace administrator controls.
Open the appropriate feedback route
During a computer meeting, open More and choose Report a problem. Before a meeting, the Meet website provides a support route to report a problem, and the pre-join screen can offer the same action under More. After a meeting ends, use Submit feedback if offered. Choose the route available in the context where the issue occurred.
Describe the event clearly
State the action you attempted, the expected result, the actual result, and the approximate time. Include exact error text and whether the issue repeated. Distinguish a browser crash from a meeting disconnection or a participant-admission refusal. Useful detail is more valuable than a lengthy complaint that never identifies which control failed. Do not include passwords, verification codes, or unrelated personal information.
Review screenshot and diagnostic expectations
Google documents an Include screenshot or capture option, depending on the route. Inspect what the screenshot would reveal and omit it when it is unnecessary or unsuitable. Do not assume omitting a screenshot removes all diagnostics: browser logs can be included automatically, and administrators can control client-log uploads. Follow your organization’s reporting requirements if sensitive information is involved. Send once the selected material is appropriate, and retain a brief record for your support team. Feedback submission itself does not prove that the underlying meeting problem has been resolved.
References
Reviewed against the linked official product guidance on November 4, 2026. Features, limits, screen labels, and access can vary by account, platform, region, and organization policy.