Use this guide to check the KUDO Bot connection and restore translation when the Bot is missing from a Teams meeting.
Audience: Meeting organizers, Hosts, and KUDO Operators.
Before you start
Confirm that KUDO is configured for the Teams meeting. The Host manages Teams lobby access; the Operator monitors the KUDO session. The Bot carries meeting audio into KUDO, so its connection is essential to translation.
Steps to check and reconnect the Bot
- Check the Teams participant list for the Bot. If it is waiting in the lobby, have the organizer admit it.
- Join the KUDO session as an Operator to inspect Bot connectivity. The status indicates whether it is connected, waiting to join, disconnected, or reconnecting.
- If the Bot is absent and the service is still running, open the KUDO for Teams app and click + Add Bot.
- Allow reconnection to finish, then confirm meeting audio reaches KUDO and captions or translated audio work. Restarting services can briefly interrupt all languages.
What to expect
The Bot normally attempts to join about 10 minutes before the scheduled start. A lobby can delay admission.
After everyone leaves Teams, inactivity causes the Bot to leave while KUDO remains active. When participants return, use + Add Bot; it does not rejoin automatically.
Troubleshooting
| Issue / Task | Possible Cause | Recommended Action |
|---|---|---|
| Bot stays in the lobby | Admission is required | Have the organizer admit it. |
| Bot still fails to join after recovery | The connection problem remains unresolved | Escalate to KUDO Support using the help link below. |
| Captions remain unavailable | Translation services may need restarting | Have the Operator restart translation services through the meeting portal. Wait for reconnection; escalate if captions still fail. |
Manage schedule changes and end the session
In the KUDO for Teams app, select the meeting and use Sync Meeting after changing its Teams schedule. If Teams is cancelled, also select Cancel Meeting in KUDO.
When translation is finished, select End Meeting. This immediately stops the KUDO session and disconnects the Bot.
Further help
See the Host and Operator guide for service recovery and escalation guidance, or contact KUDO Support if recovery fails.