What should I do if the Notta Bot fails to auto-join a calendar event?

If Notta Bot fails to join a Web meeting automatically, an announcement email will be sent to your account's email address.

Email Example:

The failure to join automatically is most likely related to the meeting settings, joining permissions, or the Bot's availability status. Please check the causes and solutions below.

Causes of Automatic Join Failure

The following are potential reasons why the Notta Bot failed to join automatically:

  1. Inadequate or Restricted Joining Information
    • Incorrect meeting password
    • Invalid meeting link
    • Unsupported meeting link
  2. Bot Participation Denied
    • Host (meeting organizer) denied or ignored the Bot's join request
  3. Bot Availability Limitations
    • No available Bot when dispatch was attempted
  4. Meeting Configuration Restrictions
    Due to meeting settings:
    • Guests are not permitted, or login is required
    • Participation from specific regions/IPs is restricted.
  5. Bot Exited Mid-Meeting
    • The Bot was forcibly removed from the meeting during recording
  6. Bot Service Anomaly
    • Temporary error on the Bot service side

Solutions

As the meeting owner or invitee, please check and correct the following points to ensure the Bot joins automatically:

  1. Meeting Information and Authentication
    Confirm that the meeting URL and password listed in the calendar event are correct.
  2. Participation Approval
    Ask the meeting host to approve the Bot's join request and accept the recording permission request (especially for Zoom meetings).
    What should I do if Notta Bot fails to join my Zoom meeting?
    What should I do if Notta Bot fails to join my Teams meeting?
  3. Waiting Room
    Check if the Bot is stuck in the Waiting Room for a long time, and ask the host to approve the Bot's entry or turn off the Waiting Room setting.
  4. Account/Region Restrictions
    Check if the meeting settings require specific authentication (account verification) or if any region restrictions that might block the Bot's connecting IP address are set.
  5. Bot Availability
    Especially for accounts with only one Bot, confirm that the Bot has fully exited the previous meeting before the next meeting starts, and adjust the meeting times accordingly.
    How many online meetings can be transcribed concurrently?

Articles in this section

Was this article helpful?
0 out of 0 found this helpful
Share