Google Meet proximity detection uses an ultrasonic signal and your device’s microphone to recognize a supported meeting room nearby. It can simplify Companion check-in, but detection has specific hardware, permission, and meeting conditions. Verify those conditions before promising automatic room selection for a hybrid meeting.
Confirm the room and device requirements
You must be in a physical room with supported Google Meet hardware. Your administrator can control automatic check-in for individual rooms. Google’s guidance supports Android, iOS, and laptops using Chrome for automatic room check-in. The separate Connect room feature has its own desktop and administrator requirements, so do not treat every detected-room option as the same function.
Use the normal meeting pre-join screen
Open the current meeting and allow the microphone permission needed for detection. Wait briefly for the room indication on the pre-meeting screen and inspect the detected room name. Google says automatic check-in does not work through g.co/present or g.co/companion, or when the meeting has more than fifty participants. A working short link therefore does not establish that proximity detection should appear.
Check the selected microphone and fallback
A headset or audio processing can prevent the microphone from receiving the ultrasonic signal. Ask your administrator to help review the supported device arrangement if needed. If detection fails, Google’s documented fallback is manual room check-in after joining Companion mode. Verify the room label rather than repeatedly joining in search of a detection prompt. Do not select a nearby room you do not occupy. Automatic detection is a convenience for this joining workflow, not a substitute for checking your actual room and meeting identity.
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.