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.
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.
Use the KUDO app to configure AI translation for a Microsoft Teams meeting. This guide covers the in-app experience, where attendees access KUDO from Teams.
Audience: Meeting organizers and Hosts.
Before you start
Create your Teams meeting and confirm that you can manage its apps and meeting settings.
Have your KUDO Client credentials available, or obtain the KUDO meeting link for the session you will connect.
Confirm which languages people will speak and which languages attendees need for translation.
Use a Teams Meeting and the Teams desktop or mobile application for the embedded experience. KUDO’s published compatibility guidance does not support Teams Town Hall or the Teams browser experience for this integration.
1. Add KUDO to the meeting
Open the Teams meeting, select Apps, and add KUDO. Open its panel in the meeting details.
Choose how to connect:
KUDO login: sign in with your KUDO credentials to configure the session.
Meeting link: select Use Meeting Link Instead and paste the corresponding KUDO meeting link.
If KUDO is unavailable, resolve app access with your Teams administrator before continuing.
2. Configure AI translation
When creating the session through the app, select AI Translation, then choose:
AI Speech & Captions for translated voice and captions.
AI Captions Only for text translation when faster conversational responses matter.
Set the Speaker languages for what people will say and the Translation languages for what attendees will receive. If connecting an existing session, review its configuration before the meeting.
3. Test before inviting your audience to use translation
Run a rehearsal with someone acting as an attendee. Use headsets and select the same output device in Teams and your computer’s sound settings. Begin at a comfortable, low listening volume.
Check the complete experience:
Join Teams and confirm that the KUDO Bot is present. Admit it if it is waiting in the lobby.
Open KUDO from the meeting toolbar.
Have a speaker talk and select a caption language to check the translated text.
For Speech & Captions, select a voice language and confirm translated speech is audible.
Locate the meeting’s Mobile Link so you can share an alternative access method if someone cannot open the embedded app.
Confirm that the app is accessible, languages are correct, the Bot connects, and your rehearsal attendee can receive the intended captions or speech. Agree who will manage the Bot and help attendees during the meeting.
Choose a language in the KUDO panel to follow a Teams meeting with translated captions or speech.
Audience: Participants attending a meeting configured with KUDO AI.
Before you join
Your Host must set up KUDO for the meeting. Available languages and translated speech depend on that setup; a captions-only session provides text translation.
Use a headset. Select the same output device in Teams and your computer’s sound settings, and start with a low listening volume.
Steps
Join the Teams meeting by selecting Join now.
Select KUDO in the meeting toolbar to open the side panel.
Select Captions and choose an available language for translated text.
If the session includes translated speech, select Voice and choose an available language to hear it.
To hear the speakers directly while keeping translated captions, choose Original audio from the Voice menu.
What to expect
Captions appear in the KUDO panel as people speak. When you choose a translated voice channel, translated speech plays through your selected output device.
Troubleshooting
Issue / Task
Possible Cause
Recommended Action
KUDO is unavailable
Device or organizational app restrictions
Rejoin using the Teams desktop or mobile app. If access remains unavailable, ask your Host for the meeting’s Mobile Link.
Speech is silent or uses the wrong device
Different output devices selected
Check that Teams and your computer use the same output device.
The panel freezes or captions stop
The app may need refreshing
Use Reload Tab in the KUDO panel. If translation remains unavailable, contact your Host.
Ask your Host for help with a missing language or a continuing translation problem. The Teams' meeting Host or manages the KUDO Bot and translation service.
This article explains how Teams Hosts and KUDO Operators keep a live Microsoft Teams meeting running smoothly. It covers real-time monitoring, interpreter communication, troubleshooting, and multilingual accessibility during the event.
Audience: Hosts, Operators, AV technicians, Meeting Services teams, Producers, and meeting organizers supporting live KUDO interpretation in Microsoft Teams.
Meeting Components
The Teams Host
The Teams Host is responsible for setting up the meeting environment. This includes scheduling the meeting, adding the KUDO app, configuring languages, and managing Teams lobby permissions. The Host can also launch or restart the Bot, access recordings and transcripts, and adjust meeting and language settings as needed.
The KUDO Operator
The Operator is active in both the Teams meeting and the KUDO interface throughout the session and they login through the KUDO portal. They monitor interpretation channels, communicate with interpreters, validate audio and captions, restart services if something goes wrong, and help troubleshoot. The Operator serves as the bridge between Teams, KUDO, interpreters, and meeting organizers, ensuring multilingual services remain active throughout the event.
The KUDO Bot
The KUDO Bot is the bridge between a Microsoft Teams meeting and the KUDO platform. It joins the Teams meeting as a participant, listens to the meeting audio, captures video and screen sharing, and sends that content into KUDO so interpreters or AI translation services can process it in real time. If the Bot is not connected, KUDO cannot receive the meeting's audio or visual content, and multilingual interpretation and translation will not work as expected. The Bot typically joins automatically shortly before the meeting begins, although a Host or Operator can manually trigger it if necessary. It will automatically leave when the KUDO meeting ends or when it detects that there are no active participants remaining in the Teams meeting.
Conducting a Sound Check
A sound check confirms that everything is connected and working before the meeting begins. Start by joining the Teams meeting and confirming the Bot appears in the participant list. Then join KUDO as an Operator and go through each interpretation channel. Ask each interpreter to confirm they can hear the Teams meeting, see screen sharing, and that their microphone is active. Verify that captions are updating correctly and that Teams participants can hear interpretation. It's best to complete this before any participants join.
Restarting the Bot
If interpretation stops unexpectedly, or the Bot does not join automatically, the Teams Host can manually restart the Bot from the Teams calendar app. KUDO Operators can also restart translation services from the meeting portal. Restarting the Bot or translation services may temporarily interrupt interpretation, captions, and audio routing for all languages. Wait for services to fully reconnect before continuing troubleshooting.
Common Issues
Participant Issue
Likely Cause
Recommended Action
“I can hear Teams but not the interpreter.”
The participant’s audio is routing to the wrong output device, or the interpreter microphone is muted.
Ask the participant to verify their audio output device settings in Windows or Mac. Confirm in the Operator console that the interpreter microphone is active and multilingual audio is functioning correctly.
“I don’t see the KUDO app.”
The participant joined from the Teams browser experience, which does not support the embedded KUDO app.
Ask the participant to rejoin the meeting using the Microsoft Teams desktop or mobile application.
“I selected French but I still hear English.”
The interpreter has not activated the outgoing language channel, or the interpreter microphone is muted.
Verify that the interpreter selected the correct outgoing language channel and confirm the interpreter microphone is enabled inside KUDO.
This guide walks through how to configure a Teams meeting with KUDO Audio Manager for Dante audio output. After completing this process, the Teams meeting audio will be captured, translated by KUDO AI, and routed into a Dante-enabled audio infrastructure.
Audience: Audio Managers, AV Technicians, Operators, and meeting organizers.
Before You Start
Before configuring Audio Manager and Dante output, confirm that the Teams meeting has already been created, Dante Virtual Soundcard is installed on the Audio Manager computer, Dante Controller is installed and configured on the Dante network, the Audio Manager user has been added to the KUDO meeting, and the Audio Manager computer is connected to the same Dante network as the destination devices.
For the best audio stability, use a wired Ethernet connection, avoid Wi-Fi for Dante workflows, close any unnecessary audio applications, and confirm the Dante clock is stable before the meeting begins.
Important: Venue Audio OUT is available for both AI and Human interpretation sessions. Venue Audio IN is only supported for Human interpretation workflows.
Configuring Audio Manager
Add the KUDO app to the Teams meeting and configure the AI session.
Enable the Audio Manager role during meeting setup. This allows translated language channels to be routed externally through Dante-compatible workflows.
Go to Users > Audio Managers, click + Add Audio Manager, and enter the Audio Manager's email address. If this is their first session, they'll need to complete the account setup from the invitation email before joining the meeting.
On the Audio Manager computer, install and open Dante Virtual Soundcard.
With Dante Virtual Soundcard running, log in to KUDO using the assigned Audio Manager credentials.
Select the Audio Manager role to access Dante routing and venue audio configuration tools.
Locate the meeting, go to Settings, and select Venue Audio OUT.
Venue Audio IN sends onsite interpreter booth audio into KUDO. Available for Human interpretation sessions only.
Venue Audio OUT sends translated KUDO audio to external devices, Dante-enabled systems, or broadcast infrastructure. Available for both AI and Human interpretation sessions.
Click Edit Audio Settings.
Find the Dante Virtual Soundcard device and assign each translated language channel to the desired Dante output channel.
Subscribe each translated language output to complete the routing.
Troubleshooting
Task
Action
Expected Result
Verify Dante Clock Synchronization
If the KUDO Audio Manager is not available in Dante Controller, confirm that all Dante devices are synchronized to the same Dante clock source before the meeting begins.
Dante devices appear correctly inside Dante Controller and Audio Manager becomes available for routing.
Verify Dante Network Connectivity
Confirm that Dante Virtual Soundcard is running, the Audio Manager computer is connected to the Dante network, destination Dante devices are visible inside Dante Controller, and firewall or network policies are not blocking Dante traffic.
Dante devices communicate correctly across the network and translated audio channels become available for routing.
Restart Audio Manager Routing
If translated channels stop updating or audio routing becomes unstable, restart Dante Virtual Soundcard, reopen Audio Manager, and verify Dante subscriptions inside Dante Controller.
Audio routing reconnects and translated audio channels resume normally. Translated audio may temporarily pause during reconnection.
Depending on your Microsoft Teams environment and organizational policies, the KUDO app may require approval or validation by your IT administrator before it can be used inside Teams meetings.
