Knowledge Base

KUDO for Microsoft Teams

User Guides

  • Integrating Teams Meeting with KUDO App

    This guide walks hosts through the steps required to configure KUDO AI inside a Teams meeting.

    Audience: Hosts and meeting organizers using KUDO AI for Microsoft Teams.

    Before You Start

    KUDO AI for Teams is an audio-first experience, so a little preparation goes a long way. Whether you're presenting or attending, use a headset and take a moment to check your computer audio settings beforehand. It's also worth lowering your headset volume before joining as translated speech can start playing at unexpected levels when the meeting begins.

    Before getting started, confirm that the Teams meeting has already been created, the KUDO app is accessible through the Teams app store, and the Host has access to the KUDO client account with permission to manage the KUDO app and Teams meeting options.

    Configuring KUDO in Teams

    1. Inside the Teams Meeting window, click Apps and add the KUDO app.
    2. Select the KUDO app from the meeting details panel and sign in with your KUDO credentials.
    3. Select AI Translation.
    4. Choose your AI meeting type based on how your use-case and workflow. 
    • AI Speech & Captions is the full experience. Best for broadcasts like keynotes and town halls.
    • AI Captions Only reduces latency. Best for multilingual discussions where response time matters.
    1. Configure your languages.
    • Speaker languages are the languages participants will speak during the meeting. 
    • Translation languages are the languages participants can select to hear or read during the meeting.
    1. Once the meeting is live, the Teams Host can return to the KUDO app at any time to configure languages, update meeting details, or manually add the KUDO Bot if troubleshooting is needed. The app also provides access to AI Customization settings, recordings and transcripts, and the KUDO Mobile Link for browser-based multilingual access.

    KUDO AI for Microsoft Teams Meetings – Host Setup and Translation Guide - Step 19.jpeg

    Troubleshooting

    Issue / Task Recommended Action Expected Result
    KUDO app becomes unresponsive or captions stop updating Click Reload Tab inside the KUDO app panel. The KUDO app refreshes and multilingual speech and captions reconnect.
    AI translation is not audible or plays through the wrong device Confirm that the same audio output device is selected in both Microsoft Teams and the operating system sound settings. Translated speech plays through the correct audio device selected by the participant.
    Translation stops or the KUDO Bot disconnects The Teams Host, KUDO Client, or Operator can click + Add Bot inside Teams, or select Restart Translation Service inside KUDO to reinitialize AI translation services. The KUDO Bot attempts to rejoin the Teams meeting and multilingual speech and captions reconnect. Translation services may temporarily pause for several seconds while reconnecting.
    Participants cannot access the KUDO app Ask participants to rejoin the Teams meeting using the Teams desktop or mobile application. If the KUDO app remains unavailable due to device or organizational limitations, provide the meeting Mobile Link. Participants can continue accessing translation through the Mobile Link even if the embedded Teams app is unavailable.
    KUDO Bot repeatedly waits in the Teams lobby Modify the Microsoft Teams meeting lobby settings to allow the KUDO Bot to bypass the lobby automatically. The KUDO Bot can join the Teams meeting automatically without requiring manual admission from the Host.

    Need Help? 

     

  • Using Teams Meeting with KUDO App

    This guide walks hosts through the steps required to join a Teams meeting, enable AI translation, select languages, and manage the KUDO Bot.

    Audience: Hosts and meeting organizers using KUDO AI Translation in Teams.

    Before You Start

    KUDO AI for Teams is an audio-first experience, so a little preparation goes a long way. Whether you're presenting or attending, use a headset and check your computer audio settings beforehand. It's also worth lowering your headset volume before joining as translated speech can start playing at unexpected levels when the meeting begins.

    Before getting started, confirm that the Teams meeting has already been created, the KUDO app is accessible through the Teams app store, and the Host has permission to manage the KUDO app and Teams meeting lobby.

    Joining Teams Meeting

    Before clicking join, select your preferred headset or audio device and confirm it's also set as your primary system sound output. Translated speech plays through your selected output device automatically once you choose a voice translation channel.

    1. Click Join now once your audio device is configured.
    2. When prompted, click Admit to allow the KUDO Bot into the meeting. The Bot automatically attempts to join through the Teams lobby 10 minutes before the scheduled start time. If it doesn't join automatically or disconnects due to inactivity, the Host can manually reset it from the KUDO app meeting dashboard inside Teams.

    1. Click the KUDO app in the Teams meeting toolbar to access AI translation. If the meeting is configured correctly but the Bot still can't join, or the app displays an "Invalid Meeting" error, the most reliable fix is to schedule a new Teams meeting with the KUDO app configured from the start.
    2. Select a captions language to view translated captions during the meeting.
    3. Choose a language from the available Voice translation channels to hear translated speech.
    4. Select Original audio to listen to participants directly while continuing to follow translated captions.

    Troubleshooting

    Issue / Task Recommended Action Expected Result
    KUDO app becomes unresponsive or captions stop updating Click Reload Tab inside the KUDO app panel. The KUDO app refreshes and multilingual speech and captions reconnect.
    AI translation is not audible or plays through the wrong device Confirm that the same audio output device is selected in both Microsoft Teams and the operating system sound settings. Translated speech plays through the correct audio device selected by the participant.
    Translation stops or the KUDO Bot disconnects The Teams Host, KUDO Client, or Operator can click + Add Bot inside Teams, or select Restart Translation Service inside KUDO to reinitialize AI translation services. The KUDO Bot attempts to rejoin the Teams meeting and multilingual speech and captions reconnect. Translation services may temporarily pause for several seconds while reconnecting.
    Participants cannot access the KUDO app Ask participants to rejoin the Teams meeting using the Teams desktop or mobile application. If the KUDO app remains unavailable due to device or organizational limitations, provide the meeting Mobile Link. Participants can continue accessing translation through the Mobile Link even if the embedded Teams app is unavailable.
    KUDO Bot repeatedly waits in the Teams lobby Modify the Microsoft Teams meeting lobby settings to allow the KUDO Bot to bypass the lobby automatically. The KUDO Bot can join the Teams meeting automatically without requiring manual admission from the Host.

    Need Help? 

  • Hosting & Operating Teams Meetings with KUDO App

    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.

    Understanding the Workflow

    When KUDO is integrated with a Microsoft Teams meeting, hosts and participants join the Teams meeting as they normally would, making it easy to chat, collaborate, and access live translation directly within Teams. However, as a Host or Operator, it's important to understand that there are actually two connected sessions running behind the scenes.

    The first session is the Microsoft Teams meeting, where participants communicate, share content, and interact with one another. The second session is a KUDO meeting, which receives the Teams audio, video, and screen-sharing feeds so interpretation services can be delivered.

    A KUDO Bot joins the Teams meeting as a participant and continuously routes the meeting content into the KUDO platform. Interpreters (or KUDO AI Translation) join the separate KUDO meeting, where they receive the source audio and provide interpretation. The translated audio is then delivered back to participants through the KUDO app in Teams.

    The Teams Host manages the meeting from within Teams and controls the KUDO app experience for participants. Meanwhile, the KUDO Operator monitors the KUDO meeting, ensures the Bot and interpreters remain connected, coordinates with Hosts and interpreters, and troubleshoots any issues that may arise during the event. Understanding this dual-meeting architecture is key to successfully operating Microsoft Teams meetings with KUDO.

    Key Concepts

    • 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 Bot

      The KUDO Bot is what connects the Teams meeting to the KUDO platform. It joins Teams as a participant, listens to the meeting audio, captures video and screen sharing, and sends all of that content into KUDO so interpreters, or AI, can work with it. If the Bot isn't connected, KUDO won't be able to hear or see the meeting, and multilingual interpretation won't function. The Bot normally joins automatically before the meeting starts, but the Host or Operator can trigger it manually if needed.

    • The KUDO Operator

      The Operator is active in both the Teams meeting and the KUDO interface throughout the session. They monitor interpretation channels, communicate with interpreters, validate audio and captions, restart services if something goes wrong, and help troubleshoot any issues participants run into. The Operator serves as the bridge between Teams, KUDO, interpreters, and meeting organizers, ensuring multilingual services remain active throughout the event.

    image.png

    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 or Translation Services

    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.

    Screenshot 2026-05-20 100559.png

    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.

    When to Escalate

    Issue First Action Escalate When
    Bot not joining Restart Bot Bot still fails after restart
    Interpreter cannot hear audio Check source feed and interpreter settings Multiple interpreters affected
    Participant cannot hear interpretation Verify language selection and audio device Multiple participants affected
    Captions not updating Restart translation service Captions fail after restart

    Need Help? 

  • Configuring Dante Audio Output for Teams App Integration

    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

    1. Add the KUDO app to the Teams meeting and configure the AI session.
    2. Enable the Audio Manager role during meeting setup. This allows translated language channels to be routed externally through Dante-compatible workflows.
    3. 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.
    4. On the Audio Manager computer, install and open Dante Virtual Soundcard.
    5. With Dante Virtual Soundcard running, log in to KUDO using the assigned Audio Manager credentials.
    6. Select the Audio Manager role to access Dante routing and venue audio configuration tools.
    7. 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.
    8. Click Edit Audio Settings.
    9. Find the Dante Virtual Soundcard device and assign each translated language channel to the desired Dante output channel.
    10. 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.

    Need Help?