Getting started with Connect
Go from download to your first translated call. This guide follows the same order you see in the Connect app.
Before you start
Confirm the following requirements before opening Connect so the rest of the setup can proceed without interruption. This makes the outcome easier to evaluate, explain, and reproduce across future calls. Use the guidance here to make one deliberate change at a time and preserve a clear baseline.
For detailed hardware and operating-system information, see System requirements.
Download and install Connect
Install the desktop app and its virtual audio components before configuring your calling application. Complete each prerequisite in order and confirm that the operating system recognizes every required Connect component. Restart only when requested, then reopen the app and verify permissions before changing audio routing.
- Install the required components.
- Open the Connect download page and choose the installer for your operating system.
- Run the installer and approve the virtual audio driver when prompted.
- Approve system permissions.
- Allow microphone access.
- On macOS, also approve any requested audio or accessibility permission.
- Confirm the installation. Open Connect and keep it running while you configure the calling app.
Sign in
Sign in with Google or with the email and password attached to your Connect account. If your organization has enterprise SSO enabled, choose Log in with SSO and use your work email. Confirm the result in a controlled test before moving to the next decision or configuration step.
The first time you sign in, Connect may show a short onboarding checklist for microphone access, audio-driver status, and output playback. Complete every check before moving on.
Choose how the conversation should translate
Set the source language, destination language, and translation direction to match the participants in the call. Keep the original setting noted so an unsuccessful adjustment can be reversed quickly. This makes the outcome easier to evaluate, explain, and reproduce across future calls. Use the guidance here to make one deliberate change at a time and preserve a clear baseline.
- Under Translate: From, select the language you will speak.
- Under To, select the language the other participant should hear.
- Add Language Hints when you expect more than one language from the other side.
- Select Unidirectional for one-way delivery or Bidirectional when both sides need translation.
- Choose a voice, then enable only the options needed for the call, such as Instant Mode, Speaker Labeling, or Noise Suppression.
Select audio devices and route your call app
In Connect, select the headset microphone you speak into and the speakers or headset you listen through. Then open the audio settings inside your calling app: Record the working device names and settings so the same result can be reproduced on the next call. A clean baseline makes every later quality decision more reliable.
| Setting in the calling app | Select | Why |
|---|---|---|
| Microphone / Input | Connect Mic | Sends the translated version of your voice to the call. |
| Speaker / Output | Connect Speaker | Lets Connect receive and process the other participant's audio when needed. |
| Inside Connect | Your physical headset | Keeps your real microphone and playback device under Connect's control. |
Start your first translated call
Use a short test call to confirm the selected devices and translation direction before beginning a real conversation. This makes the outcome easier to evaluate, explain, and reproduce across future calls. Use the guidance here to make one deliberate change at a time and preserve a clear baseline.
- Start or join the call in your normal calling app.
- Check that the call is using Connect Mic and Connect Speaker.
- Return to Connect and press How I Sound? for a quick translated voice preview.
- Press CONNECT-ON. The timer starts when Connect is actively processing audio.
- Speak at a normal pace, keep the microphone close, and leave a brief pause between turns.
Finish cleanly
Press CONNECT-OFF before leaving the call, then close the call normally. If you changed app-specific audio devices for a one-time session, switch them back to your normal headset afterwards. Keep the original setting noted so an unsuccessful adjustment can be reversed quickly. This makes the outcome easier to evaluate, explain, and reproduce across future calls.
Frequently asked questions
These answers address the setup choices that most often block a first translated call. Confirm each layer in order: physical headset, Connect configuration, virtual devices, calling application, and translation direction. A successful local preview is useful, but the setup is complete only after both sides of a real test call hear the expected audio.
Does the other participant need Connect?
No. The other participant joins through the normal calling application and hears the translated audio delivered through that call. They do not need a Connect account, browser extension, or separate installation.
Why do I select my headset in Connect but Connect Mic in the calling app?
Connect needs the physical headset to capture and play audio locally. The calling application uses Connect Mic and Connect Speaker so the audio can pass through Connect for processing before it reaches either participant.
Why is my headset missing from the device list?
Connect the headset before opening Connect, confirm operating-system microphone permission, and try a direct USB port. If the device appears in the operating system but not in Connect, close and reopen Connect before changing routing or reinstalling components.
When is a first setup ready for a live call?
The physical devices must appear in Connect, How I Sound? must produce a clear preview, the calling app must use both Connect virtual devices, and a short test call must confirm the correct language direction for both participants.
Support
Need help? Get in touch with our Support Team for assistance. Include the calling application, operating system, selected microphone and speaker, translation direction, and the exact step that failed. A short description of the expected result and what happened instead helps the team respond more quickly.