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

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:

Bot does not join the meeting
Bot stuck in “waiting room”
Bot automatically denied without host action
No recording or transcript generated- Use the options menu (three dots) next to the warning message in Google Meet to manually admit flagged bots.

When starting your meeting:

Without this step, Claap will NOT join the call.

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- Inform meeting participants in advance to avoid confusion when admitting the bot.

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.

To prevent the Claap bot from joining meetings automatically:

Open the Claap settings and navigate to Meeting Preferences.
Locate the option labeled "Auto-record the following meetings in my calendar."
Set this option to "None." This will disable automation, ensuring the bot does not join meetings without manual action.