Scam With Your Friends AI Not Working

Find the failing stage

A call has four stages: microphone input → recognized text → online AI response → caller voice. Run this quick check before changing service settings:

1. Say a short sentence and inspect the captured text. Missing or incorrect words belong in the microphone guide.
2. Send a short typed phone message. If it gets a reply, the AI connection works for that test and speech input needs attention.
3. If typed text also gets no reply, read the service warning and check the selected backend.
4. If a reply appears as text but has no sound, skip to voice output.

Match the warning to the next action

Hotfix 2 separates service failures and temporary usage restrictions from fictional caller dialogue. Keep the exact wording so you do not troubleshoot a restriction as a microphone failure.

Connection or sign-in failure

Check internet access and the current official announcements. Retry after a temporary outage; persistent failures need a report.

Temporary usage restriction

Follow the notice and support or appeal route. Do not assume a reset time or that buying a key is required.

Missing or rejected personal OpenRouter key

The host should replace the key or switch to Official Backend.

Clock-related warning

Check the Windows date and time, then retry. Early official fixes specifically addressed clock-related AI access failures.

Deepgram key error

This is speech recognition, not the AI conversation backend. Fix that key or choose a built-in recognition mode.

Check official announcements for service notices. This website does not have a live server-status feed, so the absence of a notice here is not evidence that services are healthy.

Official Backend or a personal key?

Update 0.1.78 documents a persistent warning when the host’s personal OpenRouter key is missing or rejected. The stated choices are to replace the key or switch to Official Backend.

Ask the host which backend is selected. If a personal key is selected, check that account’s key status and available usage in the provider dashboard. An OpenRouter key powers conversation requests; a Deepgram key powers optional speech recognition. Replacing one does not configure the other.

See included AI and optional services if the warning is unclear. The reviewed official material does not establish a universal recurring allowance or reset schedule.

Caller text appears, but no voice plays

First check whether other game audio works and whether output is going to the intended device. If only caller speech is missing, inspect voice-loading or Qwen3 warnings rather than changing microphone recognition.

The newer official notes give Qwen3 up to 20 seconds to start speech before using another voice system for that session. Older updates used shorter limits, so old timeout advice may no longer match your build. Update 0.1.82 also prevents unsupported or failed Qwen setup from blocking host/join behind its warning.

If optional Qwen3 is selected and fails, try the alternative voice system offered by the game and repeat the same test. Record whether reply text is visible and whether the fallback produces sound.

Send a useful problem report

Include the game version, exact warning, time the failure began, selected backend, speech provider and whether typed dialogue works. For a silent caller, add whether response text and other game sounds work. Use in-game Feedback or the main-menu community link described by the EULA.

If you attach logs or a recording, review what they contain first; they can include conversation text and player audio. See recordings and privacy.