Purpose

This pilot is designed to evaluate KUDO AI Translation in a competency assessment environment where an English-speaking assessor conducts a one-on-one evaluation with a Spanish-speaking employee in real time.

For the purposes of this evaluation, the sample use case is based on a construction company conducting workforce assessments. The assessment may include safety procedures, equipment operation, onboarding requirements, job-site protocols, and other operational topics commonly encountered in the construction industry.

Unlike classroom training, this pilot focuses on validating whether an assessor can accurately evaluate knowledge, comprehension, and job-related competencies through translated communication.

The goal is to determine whether KUDO can effectively support multilingual assessments, certifications, competency evaluations, and workforce qualification programs without requiring bilingual assessors or human interpreters.

Upon completion of the pilot, participants should have a clear understanding of translation accuracy, terminology handling, assessment reliability, and the overall suitability of KUDO AI Translation for competency validation scenarios.

Pilot Objectives

This pilot is intended to validate the following:

• Real-time AI translation accuracy during assessments
• Question-and-answer interactions
• Knowledge verification through translated communication
• Competency validation workflows
• Technical and safety terminology translation
• Assessor confidence in evaluating responses
• Overall readiness for workforce assessment applications

Test Scenario

Participants

Recommended Duration

15–20 Minutes

Languages

Pilot Preparation Checklist

Prior to the pilot, please ensure the following items have been completed:

✓ KUDO meeting created

✓ Participant meeting link distributed

✓ KUDO Mobile App installed

✓ Mobile login credentials provided

✓ Terminology list submitted to KUDO

✓ AI Customization configured

✓ Test devices prepared

✓ Headphones available

✓ Internet connectivity verified

Test Environment

For this pilot, the assessor joins the KUDO meeting using the Participant meeting link provided by KUDO.

The employee or student also joins using the KUDO Participant meeting link and selects their preferred language. 

All spoken responses, questions, and assessment interactions will be translated in real time between English and Spanish. To ensure the best possible experience, participants should use a stable internet connection, headphones or earbuds, and fully charged devices, and should participate from a quiet environment whenever possible.

AI Customization Preparation

To fully evaluate KUDO AI Translation in a competency assessment environment, the client should provide a list of terminology they would like to evaluate during the pilot.

Terminology may include:

• Equipment names
• Safety procedures
• Construction terminology

Depending on the desired outcome, terminology can be configured using one or more of the following tools:

• Glossary - Ensures specific terms are translated consistently into the desired target language.
• Do Not Translate - Preserves terms exactly as written. This is commonly used for company names, product names, equipment models, acronyms, and proprietary terminology.
• Word Priority - Guides the AI toward a preferred interpretation when a word or phrase may have multiple possible meanings.

Participants should intentionally incorporate submitted terminology throughout the assessment to validate AI Customization performance.

Pilot Workflow

Phase 1 – Setup and Connectivity

Goal

Confirm all participants can access the meeting and communicate through translated audio.

Activities

Assessor

• Joins the KUDO meeting.
• Confirms microphone audio is working.

Employee / Student

• Opens the KUDO Mobile App.
• Selects Spanish as their preferred language.
• Verifies translated audio and captions are available.
• Confirms microphone access is enabled.

Success Criteria

✓ Both participants successfully join.

✓ Two-way communication is established.

✓ Translated audio and captions are available.

✓ No technical assistance is required.

Phase 2 – Knowledge Verification

Goal

Evaluate whether the assessor can verify understanding through translated communication.

Activities

The assessor asks a series of knowledge-based questions related to construction operations. Examples may include:

• Safety procedures
• PPE requirements
• Emergency response procedures

The employee responds in Spanish using the KUDO Mobile App.

Success Criteria

✓ Questions are translated accurately.

✓ Responses are translated accurately.

✓ Assessor can determine whether answers are correct.

✓ Communication remains clear and natural.

Phase 3 – Competency Validation

Goal

Evaluate whether KUDO supports true competency assessment rather than simple conversation.

Activities

The assessor presents practical scenarios requiring explanation, reasoning, or procedural knowledge. 

Examples:

• Describe the proper lockout/tagout process.
• Explain fall protection requirements.
• Walk through an equipment inspection procedure.

The employee answers in Spanish while the assessor evaluates the response in English.

Success Criteria

✓ Assessor can accurately evaluate competency.

✓ Employee demonstrates understanding through translated communication.

✓ No significant meaning is lost during translation.

✓ Responses remain understandable and complete.

Phase 4 – AI Customization Validation

Goal

Evaluate how effectively KUDO AI Translation handles client-specific terminology using Glossary, Do Not Translate, and Word Priority customization.

Activities

The assessor intentionally incorporates client-provided terminology into assessment questions and follow-up discussions. Examples may include:

• Construction equipment names
• Safety terminology
• Operational procedures

Optional Advanced Validation

For the most realistic evaluation, participants may use existing certification materials, assessment forms, onboarding evaluations, or safety qualification documents currently used by the organization.

Success Criteria

✓ Technical terminology is translated accurately.

✓ Terminology remains consistent throughout the assessment.

✓ Specialized vocabulary does not negatively impact comprehension.

✓ AI Customization behaves as expected.

Pilot Success Criteria

The pilot should be considered successful if:

• The assessor can accurately evaluate knowledge and competency through translated communication.
• Translation quality remains acceptable throughout the assessment.
• Technical and safety terminology is understandable.
• Two-way communication remains natural and efficient.
• No significant meaning is lost during question-and-answer exchanges.
• Participants can complete the assessment without requiring bilingual facilitation or human interpretation.
• The organization would feel comfortable using the solution during live competency evaluations.

Post-Pilot Feedback Questions

1. How easy was it to join and access the translated experience?
2. How accurately was the training content translated?
3. Did the AI Customization behave as expected?
4. Would you feel comfortable using this solution during live training?
5. What improvements would you recommend?

Next Steps

Following completion of the pilot, review participant feedback with the KUDO team. The findings from this pilot will help determine the most effective approach for implementing KUDO AI Translation within workforce assessments, competency validation programs, safety certifications, onboarding evaluations, and operational qualification processes.

Need Help?

Purpose

This pilot is designed to evaluate KUDO AI Translation in a classroom-style training environment where an English-speaking instructor delivers training content to Spanish-speaking learners in real time.

For the purposes of this evaluation, the sample use case is based on a construction company conducting workforce training. The training content may include safety procedures, equipment operation, onboarding materials, job-site instructions, and other operational topics commonly encountered in the construction industry.

The goal is to determine whether KUDO can effectively support workforce training, employee onboarding, safety programs, and operational instruction by providing multilingual communication without the need for bilingual trainers or human interpreters.

Upon completion of the pilot, participants should have a clear understanding of the learner experience, translation accuracy, handling of construction and safety terminology, and the overall suitability of KUDO AI Translation for classroom-based and field training scenarios.

Pilot Objectives

This pilot is intended to validate the following:

• Real-time AI translation accuracy
• Learner comprehension and engagement
• Ease of deployment using personal devices
• Classroom interaction and discussion flow
• Technical and safety terminology translation
• Instructor experience and teaching effectiveness
• Overall readiness for workforce training applications

Test Scenario

Participants

Recommended Duration

15–20 Minutes

Languages

Pilot Preparation Checklist

Prior to the pilot, please ensure the following items have been completed:

✓ KUDO meeting created

✓ Participant meeting link distributed

✓ Mobile Link or QR code distributed

✓ Terminology list submitted to KUDO

✓ AI Customization configured

✓ Test devices prepared

✓ Headphones available

✓ Internet connectivity verified

Test Environment

For this pilot, the instructor, speaker, or presenter will join the KUDO meeting using the Participant meeting link provided by KUDO and deliver the training content in English. Learners will access the translated audio and captions on their own devices using the KUDO Mobile Link or QR code.

To ensure the best possible experience, all participants should use a stable internet connection, headphones or earbuds, and fully charged devices, and should participate from a quiet environment whenever possible to minimize background noise and distractions.

AI Customization Preparation

To fully evaluate KUDO AI Translation in a real-world training environment, the client should provide a list of terminology they would like to evaluate during the pilot. This allows the KUDO team to configure AI Customization settings and validate how specialized vocabulary is handled during translation.

Terminology may include equipment names, internal acronyms, safety procedures, product names, project names, operational processes, employee job titles, and other industry-specific language commonly used during training.

Depending on the desired outcome, terminology can be configured using one or more of the following tools:

• Glossary - Ensures specific terms are translated consistently into the desired target language.
• Do Not Translate - Preserves terms exactly as written. This is commonly used for company names, product names, equipment models, acronyms, and proprietary terminology.
• Word Priority - Guides the AI toward a preferred interpretation when a word or phrase may have multiple possible meanings.

To validate these customizations during the pilot, participants should intentionally use the submitted terminology throughout the training session and verify that the expected translations or language behavior are applied consistently. For best results, terminology should be submitted to the KUDO team prior to the pilot so that configuration and testing can be completed before the session begins.

Pilot Workflow

Phase 1 – Setup and Connectivity

Goal

Confirm all participants can access the meeting and translation experience.

Activities

Instructor

• Joins the KUDO meeting as a Participant.
• Confirms microphone audio is working.

Learners

• Scan the QR code or open the Mobile Link.
• Select Spanish as their preferred language.
• Verify translated audio and captions are available.

Success Criteria

✓ All participants successfully join.

✓ Learners receive translated audio.

✓ Learners receive translated captions.

✓ No technical assistance is required.

Phase 2 – Training Delivery

Goal

Evaluate how effectively learners understand instructional content.

Activities

The instructor delivers approximately five minutes of training content in English using material representative of a typical construction training session.

Examples may include:

• Safety procedures
• Equipment operation
• New employee onboarding

Success Criteria

✓ Learners understand instructional content.

✓ Instructor maintains a natural speaking pace.

✓ Translation remains understandable throughout the presentation.

✓ Participants can complete the training exercise without requiring repeated interpretation, bilingual facilitation, or significant modification to the instructor's normal delivery pace.

Phase 3 – Real-World Classroom Conditions

Goal

Evaluate performance during typical classroom interactions and discussion.

Activities

Participants intentionally simulate:

• Multiple speakers
• Speaker interruptions
• Clarification requests

Success Criteria

✓ Translation remains understandable.

✓ Participants maintain conversation flow.

✓ Learners remain engaged.

✓ Discussions occur naturally without significantly slowing the session.

Phase 4 – AI Customization Validation

Goal

Evaluate how effectively KUDO AI Translation handles client-specific terminology using Glossary, Do Not Translate, and Word Priority customization.

Activities

The instructor intentionally incorporates client-provided terminology into the training content. Examples include:

• Construction equipment names
• Safety terminology
• Operational procedures

Optional Advanced Validation

For the most realistic evaluation, instructors may use actual training materials currently deployed within the organization, including:

• Safety manuals
• Toolbox talks
• Equipment training documentation

Success Criteria

✓ Technical terminology is translated accurately.

✓ Learners understand operational concepts.

✓ Terminology remains consistent throughout the session.

✓ Specialized vocabulary does not negatively impact the learner experience.

✓ AI Customization behaves as expected.

Pilot Success Criteria

The pilot should be considered successful if:

• Learners understand instructional content without repeated clarification.
• Participants communicate naturally.
• Translation quality remains acceptable throughout the session.
• Technical and safety terminology is understandable.
• Learners can independently access translated audio and captions.
• The instructor can maintain a normal training pace.
• Participants can complete the training exercise without requiring repeated interpretation or bilingual facilitation.
• Participants would be comfortable using the solution during live workforce training.

Post-Pilot Feedback Questions

1. How easy was it to join and access the translated experience?
2. How accurately was the training content translated?
3. Did the AI Customization behave as expected?
4. Would you feel comfortable using this solution during live training?
5. What improvements would you recommend?

Next Steps

Following completion of the pilot, review participant feedback with the KUDO team. The findings from this pilot will help determine the most effective approach for implementing KUDO AI Translation within workforce training, onboarding, safety programs, and operational communications.

Need Help?

Connecting to KUDO Meeting

Each room that requires translation needs one dedicated computer connected to KUDO Meeting. This machine upstreams the room's source-language audio and video feed and should not be used for anything else during the event. Before the event:

• Connect the computer to the internet using a wired Ethernet connection.
• Disable notifications, sleep mode, and automatic updates.
• Connect a USB audio interface or capture device capable of receiving the room's audio feed from the onsite AV team.
• If video is available, connect a USB video capture device to receive the room's video feed.

From KUDO, you'll need:

• The Participant Link for the onsite computer that will upstream the event.
• The Mobile Link (QR Code) that attendees will use to access translated audio and captions.

Sharing the QR Code with Attendees

Display the KUDO Mobile Link QR code on presentation screens, signage, or printed materials. Attendees scan it with their phones, choose their preferred language, and immediately start hearing translated audio or reading live captions. No app download needed.

Running multiple rooms or a multi-day event? Create a static QR code for each room, label them clearly, and rotate the Mobile Links throughout the day based on the agenda. Sound check the audio and test each QR code before attendees arrive.

Attendee Wi-Fi Requirements

Reliable Wi-Fi coverage throughout the venue is essential. For larger events, a dedicated attendee network is recommended. A 5 GHz network helps reduce interference from nearby Bluetooth devices and other wireless equipment in congested areas.

Minimum Requirements

• Wi-Fi 5 (802.11ac) or Wi-Fi 6 (802.11ax)
• Dedicated or isolated 5 GHz wireless network
• Access points with 3x3 MU-MIMO antennas or better
• Minimum bandwidth of 48 kbps per attendee
• UDP traffic allowed through the network firewall
• Unicast communication supported

Recommended Best Practices

• Provide strong Wi-Fi coverage throughout all attendee areas
• Avoid congested public or guest networks when possible
• Test QR code access and audio streaming before attendees arrive
• Encourage attendees to bring headphones or earbuds for the best listening experience
• Ensure attendee devices can remain charged throughout the event

Technical Specifications

Ingest Computer

• Windows 7+ or macOS 10.11+
• Intel Core i7, AMD Ryzen 7, or Apple M1 processor (or better)
• 8 GB RAM minimum

Browser

• Chrome (preferred)
• Firefox
• Microsoft Edge
• Safari is not supported

Internet Connection

• Dedicated 20 Mbps download
• Dedicated 10 Mbps upload
• Open TCP Port 443
• Open UDP Port 3478

Audio Input

• One audio feed from the room source
• One USB audio interface or USB audio adapter

Video Input (Optional)

• One video feed from the room source
• One USB video capture device

Recommended: While AI Translation only requires audio, providing a video feed whenever possible improves interpretation quality by giving interpreters visual context such as presenters, slides, demonstrations, and audience interactions.

Need Help?

When scheduling a session, you have the option to configure advanced settings. All these settings have been pre-configured with the optimal defaults suitable for the vast majority of meetings. Therefore, in most cases, you do not need to modify them. However, to enhance the experience for specific needs, you may need to customize them. Below is a list of settings you can configure when creating a new session.

Mobile Link and Integrations

This option enables the automatic creation of a link for accessing KUDO AI on any mobile device through a dedicated URL or a QR code. The QR code will open a page in the browser. Additionally, this option provides an embed code to integrate KUDO AI into third-party platforms. This option is enabled by default.

This option includes the following two settings:

• Enable Autofloor: When activated, this setting allows participants to hear the original (speaker's) audio within the translation channel if the speaker is speaking the same language as that particular channel. Autofloor can be disabled to implement the autofloor API, or to stop the floor audio from passing thru.
• Enable Horizontal Screen Projection: When activated, this setting adjusts the appearance of the Mobile Link, allowing it to be fully resizable. This feature is especially useful for projecting captions on large screens during in-person events, where space is limited due to other visuals being projected on the screen.

Uploading Your Logo

This option allows you to upload your company logo to a meeting, replacing the default KUDO logo on the Mobile Link. It's ideal for organizations that want to deliver a branded experience when using translation services.

The logo can be uploaded in Advanced Settings during meeting creation. For best results, use an image that is 96x96 pixels or smaller, in landscape orientation.

Speaking Modes

This option applies to sessions held via KUDO Meeting. The default setting is Open Mic, but you can customize this based on your needs. The available modes are:

• Open Mic: Participants can independently turn their microphones on and off. You can also limit the maximum number of microphones that can be active simultaneously by adjusting the "Number of Active Mics" setting.
• Request to Speak: In this mode, participants must request permission to speak by clicking a dedicated icon within the KUDO Web Conferencing application. The session host will then enable their microphone. We recommend using Request to Speak modes for meetings expecting 20 or more participants.

Recordings

This option allows you to record the audio and video of your meeting. Recordings will be available for 30 days. By default, this option is set to OFF, ensuring that no recording of your meeting will occur without your explicit consent.

Audio Manager

Allow the Audio Manager role in order to ingest and route audio for hybrid or in-person meeting.

Preparation time

Allow the meeting to start before the scheduled time. This is useful for technical setup, such as checking if connections are established and ensuring that audio is properly captured by the device.

Grant consent for the KUDO team to access your meeting

Allow members of the KUDO team to join your meeting when necessary, for example, for debugging purposes.

Need Help?

How KUDO Counts Viewers

KUDO identifies and reports unique attendees (called Viewers) based on how participants access and interact with interpretation channels during a meeting. These statistics appear in the Viewer Language Statistics section of the Post-Meeting Report.

What Makes a Unique Viewer

A viewer is counted when someone clicks Join on a Floor or language channel through the KUDO Meeting, Mobile Link, or KUDO Widget. KUDO identifies each viewer by the combination of their device, browser, and session environment.

When Someone Is Counted Once

If a viewer refreshes the page, clicks Leave and rejoins, or reconnects using the same browser and device, they are counted only once. This prevents duplicate counts during normal reconnects or page refreshes.

When Someone Is Counted Again

A viewer is counted as a new unique attendee if they join from a different device, switch to a different browser on the same device, or access the meeting from a separate environment. For example, opening the KUDO Viewer Link in another browser while already connected on their phone.

How Language Counts Work

Viewer statistics are tracked per language channel accessed during the session. If a participant joins the Floor channel, switches to Spanish, then English, then back to Spanish, the report will show one count for each language: Floor, Spanish, and English. Switching back to a channel already visited in the same session does not add another count.

Need Help?

Before You Start

Confirm that the meeting has ended, recording was enabled during the session, and you have access to the KUDO Client account that scheduled the meeting. Allow a few minutes after larger meetings for assets to finish processing before downloading.

Important: Recordings and transcripts are only available for meetings that were recorded. Enable recording before the meeting begins and verify it's active during the session. Assign a Host or Operator to monitor recording on high-visibility events, and download critical assets shortly after the meeting concludes.

Accessing Content

1. Log in to your KUDO Client account and go to Previous Meetings. 
2. Select the meeting and open the Content section. 
3. Select Recordings to view and download available meeting recordings. 
4. Select Transcripts to view and download multilingual transcription files.
5. If polls were used during the meeting, go to Polls within the Content section to access poll questions, participant responses, and voting statistics. Availability depends on poll configuration and meeting permissions.

KUDO supports Single Sign-On (SSO) through SAML 2.0, allowing users to sign in to KUDO after authenticating through your organization's Identity Provider (IdP). KUDO acts as the Service Provider, and your organization acts as the IdP. If a user doesn't already have a KUDO account, one can be created automatically upon their first successful sign-in.

By default, new users are provisioned with the Meeting Participant role unless a different role is specified in the SAML response. If a user is later invited to a session with a different role, that role can be associated with their account, and they may be able to select it at login.

Supported roles: Meeting Participant, Interpreter, Viewer, and Operator.

Step 1 — Request SSO Setup from KUDO

To begin, email the following information to support@kudo.ai:

• Your KUDO account email address
• Your organization name
• Your Identity Provider (Okta, OneLogin, or Microsoft Entra ID)

Once KUDO creates your organization in the system, the support team will provide the SAML configuration details you'll need, including the ACS URL, Login URL, Single Logout URL, and Entity ID.

Step 2 — Configure Your Identity Provider

Your IT administrator will need to log in to the Identity Provider with administrator permissions and create a SAML connector for KUDO using the details provided. Map the following custom fields in the IdP configuration:

If no role is assigned in the IdP, KUDO will default to the Meeting Participant role.

Once configuration is complete, download the SAML metadata file and send it to support@kudo.ai.

Step 3 — Submit Your User List

Provide a list of users who will be accessing KUDO through SSO. KUDO will use this to ensure each user is associated with the correct organization in the system.

Step 4 — Confirmation

Once setup is complete, KUDO will confirm that SSO is active. Users can then sign in to KUDO using your organization's SSO provider.

Need Help? 

KUDO uses secure web technologies and real-time communication services to deliver multilingual meetings, AI translation, captions, audio, and video streams.

If users are connecting from a corporate, government, educational, or restricted network environment, firewall or proxy settings may block access to parts of the KUDO platform.

This guide outlines the recommended network requirements and domains that should be allowed to ensure proper connectivity.

Common Symptoms of Firewall or Network Restrictions

Users affected by firewall or proxy restrictions may experience:

• Unable to join meetings
• Infinite loading screens
• Missing audio or video
• Interpretation channels not loading
• KUDO panel not appearing in Microsoft Teams
• Frequent disconnects or reconnects
• Captions or AI translation failing to initialize
• Webcam or microphone connection failures
• KUDO Widget or Mobile Link not loading properly

Domains

Depending on your company's firewall or endpoint security settings, you might have to whitelist the following domains: 

• *.kudoway.com (if your account is in the USA region)
• *.kudoway.eu  (if your account is in the Europe region)
• *.kudoway.ca (if your account is in the Canadian region)
• *.tokbox.com 
• *.opentok.com

If your firewall doesn’t allow wildcard whitelisting or your company’s policy prevents you from doing wildcard whitelisting, you can narrow it down using specific sub-domains:

USA region

• https://live.kudoway.com
• https://api.kudoway.com
• https://session-console.kudoway.com

Europe region

• https://live.kudoway.eu
• https://api.kudoway.eu
• https://session-console.kudoway.eu

Canada region

• https://live.kudoway.ca
• https://api.kudoway.ca
• https://session-console.kudoway.ca

Ports

All media (audio and video) traffic will go through STUN servers, and the recommended protocol is UDP (3478). However, if your company’s security policy is blocking UDP, our system will fallback the media traffic to TCP on SSL (443). All traffic is bi-directional.

Required TCP port: 443

Recommended UDP port: 3478 (UDP traffic is recommended because of its low overhead, leading to better video quality in most cases).

Using KUDO with a proxy

If the only way to access the Internet from your network is through a proxy then it must be a transparent proxy or it must be configured in the browser for HTTPS connections.

We do not support proxies requiring authentication.

Firewall behaviors

In some cases, we have seen users experiencing issues with media (audio and video) after a short period of usage. This might be related to their firewall or endpoint security settings where stateful packet inspection or flood control will deprioritize or throttle media streams, hence reducing the quality or, in some cases, blocking the stream. In these extreme cases, we recommend you contact your company’s IT security.

Microsoft Teams

If you are using KUDO with Microsoft Teams, while all the above security considerations apply, you will need to allow or whitelist the following sub-domains and ports:

• https://teams-bot.kudoway.com
• https://teams-web.kudoway.com
• TCP port: 8445
• TCP port: 9444

IP ranges

KUDO is using dynamic IP and elastic load balancing; hence we cannot guarantee the exact IPs used for your meetings. However, we can provide you with a range. For technical and security reasons, we do change these ranges periodically. If your company is whitelisting these ranges, you can explicitly ask KUDO to add you to our mailing list to get an updated range. We do notify customers three weeks ahead of the changes.

IP version support

KUDO platforms support IPv4. The support for IPv6 will be available in Q2 2022. 

IP Range

You might have to whitelist two sections, depending on your firewall security settings and policies:

1. Account region related
2. KUDO Media Services

Updated IP range as of March 2022

USA Server (Mandatory if the account is in the US region)
44.194.123.245 
54.183.2.235

Europe Server (Mandatory if the account is in the European region)
3.125.64.235 
34.247.171.240

Canada Server (Mandatory if the account is in the Canadian region)
3.97.146.187

CHINA Server (Mandatory if the account is in the China region)
47.52.44.158
47.52.109.58

KUDO Media Services (Mandatory)
{
 "ipv4": [

  "3.123.12.128/28",
  "3.127.48.224/28",
  "3.214.145.96/27",
  "3.234.232.160/27",
  "3.234.248.80/28",
  "3.235.255.176/28",
  "3.248.234.48/28",
  "3.248.243.144/28",
  "3.248.244.96/27",
  "3.25.48.192/28",
  "3.38.113.0/24",
  "3.38.114.0/24",
  "3.38.91.128/25",
  "3.7.161.0/26",
  "3.7.161.48/28",
  "13.251.158.0/28",
  "15.228.1.16/28",
  "18.139.118.176/28",
  "18.141.165.128/27",
  "18.156.18.0/27",
  "18.157.71.112/28",
  "18.179.48.208/28",
  "18.180.159.224/27",
  "18.202.216.0/28",
  "34.218.216.144/28",
  "34.222.66.96/28",
  "34.223.51.192/27",
  "34.223.51.224/27",
  "35.158.127.224/28",
  "44.232.236.96/27",
  "44.234.90.64/28",
  "52.200.60.16/28",
  "52.213.63.176/28",
  "52.41.63.240/28",
  "52.51.63.16/28",
  "52.65.127.192/27",
  "52.66.255.192/27",
  "54.233.127.224/29",
  "54.250.250.208/28",
  "54.69.125.241/32",
  "54.89.253.64/28",
  "99.79.160.16/28",
  "99.80.88.240/28",
  "168.100.64.0/18"
 ]
}

Need Help? 

Access & Restrictions

KUDO meetings can be joined from any location with a stable internet connection. If you're connecting through a corporate, government-managed, or heavily restricted network, your IT team may need to adjust firewall or security settings to allow access to KUDO services. See the KUDO Firewall & Network Requirements guide for recommended configurations.

Regions with Known Access Limitations

Some countries restrict cross-border data traffic or apply internet routing policies that can affect access to cloud-based services like KUDO. In these locations, you may experience service disruptions, degraded audio or video quality, or difficulty connecting at all. KUDO is aware that access may be unreliable or unavailable in the following countries: 

• China
• Belarus
• Crimea
• Cuba
• Iran
• Jordan
• Kuwait
• North Korea
• Oman
• Russia
• Sudan
• Syria
• United Arab Emirates (UAE)
• Donetsk People's Republic of Ukraine
• Luhansk People's Republic of Ukraine
• Zaporizhzhia Oblast
• Kherson Oblast

This list is not exhaustive and may change without notice as regional regulations and internet policies evolve.

Using a VPN

Participants connecting from restricted regions may be able to access KUDO through a VPN. Keep in mind that VPN connections can introduce additional latency or affect audio and video quality depending on your provider and network conditions.

Need Help? 

Displaying the multilingual closed captions from the KUDO Mobile Link on a large display can be achieved using basic AV skills and hardware devices. We highly recommend seeking professional AV support, especially during large-scale conferences or meetings where successful interpretation is critical.

Requirements:

- Large display or comfort monitor.

- Dedicated computer with HDMI output, or a USB adapter with an SDI output.

- Video scaler hardware (Brands such as Blackmagic, AJA, AVPro, Decimator)

- Stable wired internet connection.

- Appropriate power and display cabling (HDMI, SDI).

- Professional AV technician.

1. Open The KUDO Mobile Link in Your Web Browser 

Use a dedicated laptop or PC with a wired internet connection to open the KUDO Mobile Link in a supported browser (Google Chrome, Mozilla Firefox, or Microsoft Edge).

The meeting organiser of the KUDO meeting must share this mobile link ahead of time.

Once the meeting is live and "presenter" audio is correctly being published, you can select the language you'd like to display by using the dropdown list.

You can select between coloured backgrounds by clicking the "Aa" symbol at the top right. Here you have the choice between light and dark mode.

Tips:

Double check that you do not have any + or - "accessibility zoom"  function taking place within your browser for consistent text scaling.

Also check to mute the audio from your device or directly from the KUDO mobile link. (It's best to avoid having the audio of the translation leak out of a loud speaker when within close proximity to your microphone system in the same room).

2. Connect the Hardware and Cabling

Connect your laptop or PC to the video scaler’s input using an HDMI cable.

On your computer (Windows or Mac OS), go to the display settings and select “Extend Display” instead of mirroring. This keeps the main screen private while sending captions to the external display.

Next, connect the video scaler’s output to your main display using HDMI or SDI, depending on cable length and the video scaler hardware you’re using.

Tip: Avoid using HDMI for long cable runs—SDI is more reliable over distance.

3.  Scale the Image on the Video Scaler

Once your system is connected and you've double checked that audio is still being passed through to the KUDO meeting, use the video scaler controls to adjust the image size and aspect ratio. 

Most video scalers have buttons and a small screen for making adjustments. You can zoom in or crop the image so that only the captions are visible, hiding the rest of the interface for a clean look.

Tip: Many clients prefer scaling the image so the KUDO interface (icons, buttons, etc.) is hidden, leaving just the captions visible on screen.

How the Workflow Fits Together

The workflow runs across four stages. First, a dedicated ingest computer joins the KUDO meeting as a Participant and routes NDI programme audio into KUDO AI for caption generation. KUDO processes that audio and delivers real-time captions through the KUDO Mobile Link. OBS Studio then composites those captions over the programme video feed. Finally, an Epiphan Pearl encoder takes the OBS output and streams the captioned programme to Vimeo via RTMP.

Before You Start

Confirm that the KUDO meeting has been created with AI Captions enabled and the Mobile Link is available for the desired caption language. Vimeo streaming credentials should be on hand, the TriCaster programme output should be accessible via NDI, and the following software should be installed before beginning: NDI Tools, VB-Audio Virtual Cable, OBS Studio, the DistroAV OBS plugin, and Google Chrome or Microsoft Edge. The Epiphan Pearl encoder should also be accessible on the local network.

For the best production stability, use wired Ethernet connections on all systems, separate the ingest and overlay workflows across different machines when possible, and test NDI routing and caption latency before the live event. Validate the Vimeo ingest before going live.

Important: Audio quality, network stability, and source platform performance directly affect AI caption quality and synchronization.

Equipment

You'll need a TriCaster as the programme video and audio source, an Epiphan Pearl as the RTMP encoder for Vimeo delivery, a dedicated Ingest PC to route programme audio into KUDO, and an Overlay/Production PC running OBS Studio. The Ingest PC and Overlay PC can be combined into a single machine if CPU resources allow. Always test under production load conditions before going live.

Phase 1 — Configure the Ingest PC

The goal here is to capture programme audio from the TriCaster NDI output and send it into KUDO as the microphone source. KUDO AI then generates live captions from that incoming audio.

1. Install NDI Tools and VB-Audio Virtual Cable, then restart the computer.

2. Open NDI Virtual Input and select the TriCaster programme NDI source. Confirm the NewTek NDI Audio device appears in Windows audio settings and that audio signal activity is visible. For additional browser compatibility, optionally route the signal through VB-Cable as the browser microphone input.

3. On the Ingest PC, open Chrome or Edge and join the KUDO Participant/Speaker link as a Participant. Inside KUDO, select the NDI audio device or VB-Cable output as the microphone source, confirm microphone activity is visible, and mute local speakers to avoid feedback.

Phase 2 — Retrieve KUDO Captions

4. Open the KUDO Mobile Link for the desired caption language in a browser. This caption feed will be embedded into OBS Studio as a Browser Source in the next phase.

Phase 3 — Configure the Caption Overlay in OBS

The goal here is to composite the KUDO caption feed over the programme video, creating a single captioned output for Vimeo delivery.

5. Inside OBS, add a new NDI Source and select the TriCaster programme feed. Set the output resolution to match your production format. The programme feed should appear in the OBS canvas.

6. Add a new Browser Source and paste the KUDO Mobile Link URL. Set the resolution to match the production output — 1920x1080 is recommended.

7. Move the caption layer above the programme video source and position captions in the lower third of the canvas. Resize or crop the Browser Source as needed. Adding a semi-transparent black background behind the captions can improve readability. Preview the scene and confirm captions appear correctly over the programme feed.

Phase 4 — Configure OBS Output to Epiphan Pearl

8. Choose one of the following methods to deliver the OBS output to the Epiphan Pearl:

Phase 5 — Stream to Vimeo

9. Inside Vimeo, open the live event and locate the RTMP URL and Stream Key. Keep these available for the next step.

10. Inside the Epiphan Pearl web interface, select the correct input source and add a new RTMP destination. Paste the Vimeo RTMP URL and Stream Key, then configure encoding settings. Recommended output: H.264 video, AAC audio, 1080p, 25 or 30 fps. Click Apply, then Start Streaming.

Troubleshooting

Known Limitations

AI caption quality depends heavily on source audio quality. Network instability may affect NDI routing and caption synchronization. OBS Browser Sources may need to be refreshed during extended productions, and combined ingest and overlay workflows on a single machine may require additional CPU resources. Caption timing may vary slightly depending on AI processing latency, and Vimeo synchronization behavior can vary by network conditions.

Requirements

• Dedicated computer with a wired internet connection to open the KUDO Mobile Link in a supported browser (Google Chrome, Mozilla Firefox, or Microsoft Edge).
• The latest version of OBS Studio installed.
• An active KUDO session with audio ingestion of the source language.
• An active KUDO Mobile Link (URL).

Step-by-Step Setup in OBS

Step 1: Open OBS and Add a Browser Source

1. Open OBS Studio.
2. In the Sources panel, click + and select Browser.
3. Name the source (e.g., KUDO Captions) and click OK.
4. Paste the KUDO Mobile Link URL into the “URL” field.
5. Set the dimensions:
   • Width: 1280
   • Height: 100 (adjust as needed)
6. Click OK to save.

Step 3: Position and Style Your Captions

• Drag and position the browser source at the bottom of your video frame.
• Resize it to fit your stream layout cleanly.
• Optional: Add a background strip for visibility:
  • Add a Color Source underneath the caption layer.
  • Use a dark or semi-transparent color (e.g., black with 50% opacity).

Step 4: Start Virtual Camera/Go Live

1. Set up your additional sources (camera, slides, screen share).
2. Confirm that captions appear in your OBS preview.
3. Start streaming to your OBS Virtual Camera output or desired RTMP string.

Optional: Add Translated Audio

To stream audio interpretation alongside captions:

1. Capture the language audio feed from the KUDO Mobile Link.
2. Add the audio in OBS using either:
   • Audio Input Capture (if using a virtual audio cable), or
   • Browser Source
3. Match the caption overlay with the corresponding audio.

Before You Start

Before configuring YouTube streaming, confirm that the KUDO meeting has already been created and translation languages are configured. You'll also need a separate YouTube Live stream created for each language, with its own unique stream key, and a Host with permission to manage broadcast settings in both KUDO and YouTube Studio.

Important: Each language must be broadcast independently to its own YouTube Live destination. Reusing the same stream key across multiple languages will interrupt or overwrite active broadcasts.

Troubleshooting

Need Help? 

Polls can be configured by going to Content > Polls before the meeting, or added during the live session. KUDO supports multiple choice, parliamentary voting, and anonymous ballot formats. Both Operators and Hosts can start, stop, and publish results, and monitor voting activity in real time.

Modifying a poll after it's already live may require participants to refresh their browser, so pre-configuring polls before the meeting begins is strongly recommended. Poll access can also be restricted to specific delegates, and anonymous voting or vote weighting can be configured in advance.

Before you start

Before participating in a poll, confirm that you've already joined the KUDO meeting, the Host or Operator has launched a poll, and the Polls panel is visible inside the meeting interface. Stay connected to a stable internet connection and submit your vote before the Host closes the poll.

Note: Poll availability and result visibility depend on Host or Operator permissions during the meeting.

Voting in a Live Poll

1. When a Host launches a poll, the Polls icon on the right-hand side of the meeting interface becomes highlighted. Click it to open the voting panel.
2. Read the poll question and review the available answer options before selecting one.
3. Click your preferred answer, then click Submit to cast your vote. Once submitted, the poll status updates to Voted while you wait for the Host to close the poll and optionally publish the results.

Viewing Poll Results

1. After the poll ends, the Host may choose to publish results to participants depending on the meeting's configuration.
2. When results are published, the Results tab becomes highlighted inside the Polls panel.
3. Click the Results tab to view the outcome.
4. Poll results display a visual summary using bar or pie charts, and may include a breakdown of eligible voters, actual voters, and non-voters.

Troubleshooting

Need Help?

---

Configuring Audio Manager

1. On a dedicated Audio Manager computer, install and open Dante Virtual Soundcard. Set the Audio Interface to WDM and Channels to 16 x 16, then click Start to enable it.
2. Log in to KUDO using the assigned Audio Manager credentials.
3. Select the Audio Manager role to access Dante routing and venue audio configuration tools.
4. 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 systems, or broadcast infrastructure. Available for both AI and Human interpretation sessions.
5. Click Edit Audio Settings.
6. Find the Dante Virtual Soundcard device and assign each translated language channel to the desired Dante output channel. Click Save when finished.
7. Inside Dante Controller, subscribe each translated language output to the appropriate Dante destination channel. Once subscribed, translated language channels are available for routing and monitoring across the Dante network.

Troubleshooting

Need Help? 

Troubleshooting

Need Help? 

KUDO offers two primary methods for routing interpretation audio to external sound systems like FM transmitters or infrared (IR) audio distribution systems:

• Option 1: KUDO Audio Manager — Use a single PC to route multiple language channels directly to Dante-enabled systems. Click here to learn more →

• Option 2: KUDO Mobile Link Method (this article) — Use individual laptops per language to route audio via headphone out or audio interfaces.

   

When to Use This Setup

The KUDO Mobile Link allows attendees to listen to live interpretation via their smartphones. However, routing audio to external receivers can be beneficial when:

• Smartphones run low on battery or overheat
• Internet connectivity is unreliable
• You need a backup/compliance solution using traditional receivers (FM or IR)

Equipment Needed

• 1 laptop per language (Windows/macOS)
• Wired internet connection for each laptop
• Google Chrome browser (recommended)
• Optional: USB audio interface for better quality
• 3.5mm to RCA/XLR adapters or cables
• FM transmitter or IR audio distribution system
• Optional: Ground loop isolators to reduce hum/noise, and adapters.

Step-by-Step Setup Guide

1. Laptop & Mobile Link Setup

• Plug in each laptop and connect to reliable internet (Wi-Fi or Ethernet).
• Open Chrome and navigate to the KUDO Mobile Link for your event.
• Join the session as a listener on each laptop, selecting one language per device.
  Example:
  • Laptop 1: Spanish
  • Laptop 2: English
• Confirm that audio is playing through each laptop using headphones or built-in speakers.

2. Route Audio to the External System

Option A: Using Headphone Out (Simple)

• Connect a 3.5mm cable from the laptop headphone jack to your FM or IR transmitter input.
• Adjust laptop volume to around 70% to avoid distortion.
• Use a ground loop isolator if you hear hum or interference.

Option B: Using USB Audio Interface (Recommended)

• Connect a USB audio interface to the laptop.
• Set your system/browser audio to output via the interface.
• Use the interface’s RCA, 1/4", or XLR outputs to feed your transmitter.
• This method offers cleaner, more stable audio quality with less chance of interference.

3. Transmit to Attendee Receivers

• FM Setup: Connect each audio feed to a dedicated FM transmitter.
• IR Setup: Connect each audio feed to an IR emitter panel.
• Ensure attendees are tuned into the correct channels/frequencies.

Tips for Best Results

• Clearly label each laptop by language.
• Use wired internet when available for maximum stability.
• Disable sleep mode, screen savers, and system notifications on all laptops.
• Conduct full audio testing before the event.
• Monitor output during the session.
• Provide extra FM or IR receivers as backups for attendees.

If you need further support with this configuration, contact the KUDO support team.

Join the meeting as an Onsite or Online Participant

Participants can join a Hybrid Meeting as an On-site or Online Participant from a customized onboarding page. On-site Participants will rely on the meeting venue's microphone, camera, and interpretation distribution systems, and will not have access to the microphone/camera buttons or Language Selector on their Kudo Meeting Console.  Online Participants will experience Hybrid meetings just like any normal Kudo meeting, and will have full access to the microphone/camera buttons and interpretation Language Selector. 

To join a Hybrid meeting:

• Click the meeting link and enter your Name & Email address on the meeting's landing page.  
  • Select I’m an on-site Participant to join as On-site 
  • Select I’m an online Participant to join as Online

Request-to-Speak as an Onsite Participant

While On-site Participants do not have a Mic On button to use their device's built-in microphone, they can still utilize Kudo's Request-to-Speak function in conjunction with the venue's microphone system. 

• Click on Request to Speak. The Operator and Host will see the request in the Request-to-Speak List
• The Operator or Host will accept the request. The On-site Participant's Request-to-Speak button will change to Done Speaking and the On-site Participant is listed in the Request-to-Speak List list as accepted. 
• The On-Site Participant can now speak into the venue's microphone system.

Access meeting documents

Just like Online Participants, On-site Participants are able to access all meeting documents. 

• Click on Documents tab to access all documents available for Participants in the Hybrid meeting 

Switching Participants from Online to On-site, and vice versa as an Operator or Host

An Operator or Host can switch a Participant from Online to On-site or vice versa from the Meeting Console.

• Go to the Users List → Click on the "…" menu next to the Participant's name
  • Click on (On-Site) Change to Online to switch a Participant from On-site to Online. The Participant will receive a pop-up informing them of the switch.
  • Click on (Online) Change to On-site to switch a Participant from Online to On-Site. The Participant will receive a pop-up informing them of the switch.

Join the meeting as Online and Onsite Participants

Participants can join the Hybrid Meeting as an “Online” or “On-site” participant from a customized onboarding page.

• Enter Name & Email Id or Email Id and Password to join the meeting  
  • Select “I’m an on-site Participant” to join as Onsite 
  • Select “I’m an online participant” to join as Online  

Switching participant from onsite to online and vice-versa 

An Operator can switch a participant from online to onsite or vice versa from the Meeting console.

• Go to the Users List → Click on the “…” menu next to the participant's name
  • Click on (On-Site) Change to Online to switch a participant from On-site to Online → Participant receives a modal informing them of the switch
  • Click on (Online) Change to On-site to switch a participant from Online to On-Site → Participant receives a modal informing them of the switch

Request to speak (Onsite – similar to online) 

• Click on “Request to Speak” --> The Operator sees the Request in the RTS Tab 
• Operator accepts the request --> the button changes to “Done Speaking” and the onsite participant is listed in the RTS list as accepted 

Access meeting documents 

• Click on Documents tab to access all documents available for participants in the hybrid meeting 

Access Polls 

To read about KUDO's access polls features, click here