Configure Connect with 8x8 Work
Select the Connect virtual microphone and speaker in 8x8 Work for translated calls.
Prepare 8x8 Work
Prepare the physical and virtual audio paths before changing 8x8 Work. Connect the wired headset, open Connect, and confirm that the real microphone and speaker work in How I Sound?. Keep a record of the original 8x8 Work devices so the configuration can be reversed if the test is unsuccessful.
- Connect: select the physical headset and the correct source and destination languages.
- Operating system: confirm that Connect Mic and Connect Speaker are present.
- 8x8 Work: sign in with an account allowed to change audio settings.
- Test participant: use a colleague or second device that can confirm both directions.
Choose the device pair
The correct speaker depends on which side of the conversation must be translated. Always use Connect Mic for translated outgoing speech, then route incoming speech through Connect Speaker only when Connect needs to process that direction. Keep alerts and ringtones on the physical headset whenever 8x8 Work provides a separate selector.
| Translation direction | 8x8 Work microphone | 8x8 Work speaker |
|---|---|---|
| Bidirectional | Connect Mic | Connect Speaker |
| Outgoing only | Connect Mic | Physical headset |
| Incoming only | Physical headset | Connect Speaker |
Configure 8x8 Work
Follow the application-specific path below after Connect is ready. Save the device selection, then reopen the relevant settings to confirm that 8x8 Work did not revert to a system default or a previously connected headset. Complete the sequence before enabling Connect on a live conversation.
- Open Connect and confirm the physical headset before starting 8x8 Work.
- Launch 8x8 Work and sign in to the assigned account.
- Select the Call using control from the left navigation.
Open Call using from the left navigation. - Open the audio-device controls and choose Connect Mic as the microphone.
Choose Connect Mic and the speaker required by the current translation direction. - Choose Connect Speaker for bidirectional translation, or keep the physical headset as speaker for outgoing-only translation.
- Save the selection if prompted and place an internal call to verify the route.
Control extra processing
A calling platform can apply automatic gain, echo control, noise suppression, or voice enhancement before Connect receives the signal. Begin with the simplest stable path and disable overlapping processing during the baseline test. Re-enable one control only when the real call environment requires it and the recipient confirms a measurable improvement.
- Confirm 8x8 Work did not revert to a system-default device after an update or reconnect.
- Keep the physical headset selected inside Connect, not the Connect virtual devices.
- Test the active call surface because preview and ringtone devices can be separate.
Validate the complete call
A saved setting is not proof that the integration works during an active call. Test the physical headset, Connect processing, the 8x8 Work virtual route, and remote playback as one complete chain. Use the same account, network, VPN, and headset that will be used in production so the result represents the real workflow.
- Use How I Sound? to confirm a clean physical microphone signal.
- Join an internal call and verify the active 8x8 Work devices inside the call surface.
- Press CONNECT-ON and confirm that the timer starts and live transcription responds.
- Speak a complete sentence and ask the remote participant what they hear.
- Test the reverse direction when using bidirectional or incoming-only translation.
- Reconnect the headset once and confirm that 8x8 Work keeps or correctly restores the saved route.
Resolve common issues
Use the symptom to identify the layer that needs attention instead of reinstalling every component. Confirm the current device names before changing them, then make one correction and repeat the same test. If the issue continues, record the application version, operating system, selected devices, translation direction, and the exact point where audio stops.
| Symptom | Likely cause | Next check |
|---|---|---|
| Connect devices are missing | 8x8 Work cached its device list | Open Connect first, then restart 8x8 Work. |
| The recipient hears natural speech | The physical microphone is active | Select Connect Mic in the active call settings. |
| Incoming translation is silent | The call speaker bypasses Connect | Select Connect Speaker for the incoming path. |
| Speech is clipped or metallic | Competing audio processing | Disable one gain, suppression, or enhancement control and retest. |
Frequently asked questions
These answers cover the decisions most likely to change the 8x8 Work result. Confirm the translation direction before applying a recommendation because outgoing-only and bidirectional calls do not use the same speaker route. Keep the last working configuration available so a failed adjustment can be reversed without disrupting the next call.
Why did 8x8 Work return to the system microphone?
A device reconnect, application update, or profile change can replace the saved choice. Reopen Call using, restore Connect Mic, verify the speaker, and make a new test call.
Which devices should I select in 8x8 Work?
Select Connect Mic whenever outgoing speech must be translated. Select Connect Speaker when incoming speech must also pass through Connect; otherwise keep the physical headset as the call speaker.
Why are Connect devices missing from 8x8 Work?
Close 8x8 Work, confirm that Connect Mic and Connect Speaker appear in the operating system, keep Connect open, and relaunch the desktop application. Applications and browser tabs often keep the device list that existed when they started.
How do I know the 8x8 Work integration is ready?
Run How I Sound?, place a real test call, press CONNECT-ON, confirm that the timer and transcription respond, and verify what both participants hear. A saved device name alone does not prove the complete route.
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.
Was this article helpful?