This article explains how the KUDO Bot behaves throughout the lifecycle of a Microsoft Teams meeting and what actions Hosts or Operators can take to manage the Bot.
Quick Reference
| Scenario | Required Action |
|---|---|
| Teams meeting cancelled | Click Cancel Meeting in the KUDO for Teams app. |
| Teams meeting rescheduled | Click Sync Meeting. |
| Bot waiting in Teams lobby | Admit the Bot from the Teams lobby. |
| Bot disconnected during a live meeting | Click + Add Bot. |
| Teams meeting became inactive | Click + Add Bot after participants return. |
| Translation no longer needed | Click End Meeting. |
| Verify Bot status | Join the meeting as a KUDO Operator. |
Before the Meeting Starts
Bot Reservation
When a Teams meeting is scheduled with KUDO enabled, KUDO reserves a Bot based on the meeting start time configured in Microsoft Teams.
If the Teams Meeting Is Cancelled
Cancelling the meeting in Microsoft Teams does not automatically cancel the associated KUDO session. To release the reserved Bot and prevent unnecessary resource allocation:
- Open the KUDO for Teams app.
- Select the meeting.
- Click Cancel Meeting.
If the Teams Meeting Is Rescheduled
If the meeting date or time changes in Microsoft Teams, KUDO must receive the updated information. To synchronize the changes:
- Open the KUDO for Teams app.
- Select the meeting.
- Click Sync Meeting.
This updates the KUDO service with the latest Teams meeting details.
During the Meeting
Automatic Bot Join
Approximately 10 minutes before the scheduled meeting start time, KUDO automatically starts the translation service and instructs the Bot to join the Microsoft Teams meeting.
If the Teams meeting uses a lobby, the Bot will wait there until a meeting organizer admits it.
No user action is required under normal circumstances.
Manually Recall the Bot
If the Bot is not present in the Teams meeting while the KUDO service is still running, you can manually recall it.
To do so:
- Open the KUDO for Teams app.
- Click + Add Bot.
KUDO will attempt to reconnect the Bot to the Teams meeting.
Common reasons for manually recalling the Bot include:
- The Bot was removed from the meeting.
- The Bot disconnected because the Teams meeting became inactive.
- The Bot did not successfully join the meeting on the first attempt.
End the KUDO Session
When multilingual services are no longer needed, you should end the KUDO session. To stop both the KUDO service and disconnect the Bot:
- Open the KUDO for Teams app.
- Click End Meeting.
This immediately ends the KUDO session and disconnects the Bot from Microsoft Teams.
Bot Behavior During Inactive Meetings
If all participants leave the Microsoft Teams meeting, the Bot automatically leaves the Teams call after detecting inactivity.
The KUDO meeting itself remains active and continues running.
When participants return to the Teams meeting, the Bot does not automatically rejoin.
To reconnect the Bot:
- Open the KUDO for Teams app.
- Click + Add Bot.
This recalls the Bot back into the Teams meeting while keeping the existing KUDO session active.
Check the Current Bot Status
To verify whether the Bot is connected and functioning correctly during a live meeting, join the KUDO session as a KUDO Operator.
The Operator interface displays the current Bot status, allowing you to confirm whether it is:
- Connected to the Teams meeting
- Waiting to join
- Disconnected
- Reconnecting
This is the recommended method for monitoring Bot connectivity during live multilingual meetings.