Find the cause
Voice AI not working? Find where it stops
Start by identifying the first point of failure: can the page open, can it receive your input, and can you hear the result? Each symptom calls for a different check. Voice Ai links you to a voice product, but this guide cannot diagnose an individual account or service outage.
decide which case you are (decision table)
Locate the earliest step that fails before changing settings. A silent result and a missing microphone signal may sound alike, but they point to different parts of the process.
path A
Take this path when the page opens but cannot receive the text or audio you intend to use. Test one input at a time so you can tell which change made a difference.
-
1
Confirm the intended input
Decide whether you are entering text or supplying microphone audio. Text-to-speech does not need microphone permission; a live voice-changing workflow does. If a text field is available, try a short, ordinary sentence rather than a long script. If a microphone is required, select the device you are actually speaking into and watch for an input-level indicator, if the interface provides one.
-
2
Check device permission and signal
For microphone input, inspect the browser’s site permission and your operating system’s microphone access. Make sure another application has not taken exclusive control of the device, then test it in your system’s sound settings. A headset can appear as both an input and an output device; choosing it for playback does not automatically choose its microphone for recording.
-
3
Repeat with a smaller test
Reload the page after changing a permission, then submit a brief sample or record a few seconds in a quiet room. Remove unsupported characters from a text test and avoid uploading a file merely to check whether text entry works. If the short attempt succeeds, add your original content back in smaller parts to isolate the input that causes the failure.
path B
Take this path when the input is accepted but processing stalls, playback is silent, or the result is unusable. These checks can narrow the cause; they cannot repair a remote service.
-
A stalled result is not a microphone diagnosis
If the interface accepts your input and then waits indefinitely, the fault may be a temporary network or service issue. Repeated submissions can make it harder to identify which attempt completed.
WorkaroundSubmit one short test, wait for its status to settle, then reload and retry once. Check any service-status notice shown by the product before changing local audio settings.
-
This page cannot restore missing sound
A completed result can still be inaudible when a browser tab is muted, the wrong speaker is selected, or system volume is low. A silent preview does not by itself prove that generation failed.
WorkaroundPlay another known audio source in the same browser, inspect the tab and system volume, and choose the intended output device. Then replay the result if that option is available.
-
A poor result may not be a technical failure
Unclear source audio, background noise, awkward punctuation, or a script outside a voice’s comfortable style can make an output sound wrong even when processing completes.
WorkaroundUse a clean, short source sample or a plainly punctuated sentence. Compare that controlled test with your original input before treating the difference as a broken feature.
final check
Compare the first failed action with the symptom you can observe. Change one variable, run the same short test again, and note whether the result changes.
What you observe
Next action
Page never opens
What you observe
The browser shows a loading or connection error before any voice controls appear.
Next action
Check your connection, reload once, and try another browser or network. Microphone settings cannot fix a page that has not loaded.
Text cannot be submitted
What you observe
The input is visible, but a short sentence cannot be sent or an error appears immediately.
Next action
Try plain text without unusual symbols. Note the exact error rather than assuming the voice or speaker is at fault.
Microphone shows no signal
What you observe
The page opens, but recording has no visible level or captured sound.
Next action
Check site permission, operating-system permission, and selected input device. Test the microphone outside the voice tool.
Processing does not finish
What you observe
The input was accepted, but no completed result appears.
Next action
Try one shorter submission and check for a status notice. If it stalls again, save the error wording and avoid repeatedly changing unrelated settings.
Result completes without sound
What you observe
A result or playback control appears, yet nothing is audible.
Next action
Test browser audio, tab mute, system volume, and output-device selection before resubmitting the input.
Sound plays but is distorted
What you observe
Audio is audible, but speech is unclear or does not resemble the expected delivery.
Next action
Compare a clean short input with the original. Check source noise and punctuation before investigating playback.
Only one browser fails
What you observe
The same short test works elsewhere on the same device.
Next action
Review the failing browser’s permissions, extensions, and stored site data. Change one setting at a time so the cause remains identifiable.
tutorial FAQ
An active connection does not confirm that microphone permission, input submission, processing, and playback all work. Find the first step that fails, then run a short test focused on that step. If multiple attempts stall after submission, check for a service-status notice rather than repeatedly changing device settings.
The result may have completed while your browser tab is muted or audio is going to a different output device. Play another known audio source in the same browser and check tab mute, system volume, and speaker selection. If other audio works, replay the result before submitting new input.
The browser may lack site permission, the operating system may block microphone access, or the wrong input device may be selected. Test the microphone in your system’s sound settings first. If it works there, review the browser permission and reload the voice page.
Not as a first step: clearing site data can remove useful settings without identifying the cause. Try a reload, a short input, and a second browser to see whether the issue is local to one browser. If it is, review permissions and extensions before removing stored site data.
Submit a brief, ordinary test using the same input type as your failed attempt. If that works but your original material does not, inspect the original for length, noise, or unusual characters. If even the short test stalls after submission, look for a product status message and record any error shown.