Google introduced a new guest admission flow that impacts how external participants including Claap are allowed into meetings.
Google safeguarded guest admit flow
When someone requests to join a meeting (also called “knocking”), hosts will now see two separate queues:
Standard queue
Trusted participants
Typically admitted quickly
Additional review queue (critical for bots)
Automated participants
Default action = automatically deny
Most bots fall into this second category. Hosts and co-hosts can still manually approve anyone, the default is just a suggestion.
This update directly affects tools like:
AI meeting assistants
Call recording bots
Note-taking tools
Automation agents (e.g. joining calls via API or link)
Common issues you may see
Bot does not join the meeting
Bot stuck in “waiting room”
Bot automatically denied without host action
No recording or transcript generated
How to fix it
You must manually admit Claap
When starting your meeting:
Open the People panel in Google Meet
Look for Claap in the waiting requests
Check the second queue (additional review)
Click Admit
Without this step, Claap will NOT join the call.
Best practices for smooth recordings
To avoid issues:
Start the meeting before Claap joins
Stay on the call until Claap is admitted
Inform your team that Claap needs approval
If recording is critical, double-check the waiting room
If you don’t see Claap, it may already have been auto-denied by Google
In that case, restart the recording or ask Claap to rejoin the meeting.