Troubleshooting

Voice calls are not working

Diagnose problems with Rezi's AI voice agent, calls not answering, audio issues, or Retell connection errors.

Updated June 10, 2026 3 min read

Voice calling is built into Rezi: each building's number answers calls with an AI voice agent, all managed by the platform. When voice stops working, the issue is usually at the building level (the number or the voice agent is not configured for go-live) or a temporary network/quality issue. Work through these steps to identify where the break is.

Step 1: Confirm voice is enabled for the building

Open Settings > Building > Voice and confirm the AI voice agent is turned on and the building has completed go-live. A building that has not finished setup, or has voice toggled off, will not answer calls with the AI. Re-save the voice settings if you recently changed the greeting or agent instructions.

Step 2: Confirm the building's number is active

Open Settings > Building and check that the building has an active phone number. If the number shows pending or failed provisioning, calls have nowhere to land. Provisioning normally completes within a few minutes of creating the building; if it stays failed, contact Rezi support to investigate.

Step 3: Test with a direct call

Call the Rezi phone number from a different phone. If the call connects and you hear the AI voice agent greeting, the system is working. If you hear ringing with no answer, a 'number not in service' message, or silence, there is a routing or number issue, contact support. If the AI answers but audio quality is poor (choppy, echo, silent periods), this is a network-level quality issue rather than a connectivity problem.

AI voice agent not responding

If calls connect but the AI agent does not speak (silence after connection), re-save the building's voice settings to re-push the configuration, then test again. If the silence persists across multiple calls, contact Rezi support with the time of a recent test call so the issue can be traced.

Voice quality issues (echo, latency, choppy audio) are almost always network-related rather than a Rezi configuration issue. The AI voice agent uses real-time audio that is sensitive to packet loss and jitter. Test from a stable, high-bandwidth connection before concluding there is a Rezi-side issue.

Calls go to voicemail instead of the AI agent. Why?
If calls ring and then go to voicemail rather than the AI agent, the building's voice agent is either turned off or the building has not completed go-live. Enable voice in Settings > Building > Voice, finish setup, and test again.
The AI agent answers but says it cannot help with anything. What is wrong?
This is typically a knowledge base configuration issue. The voice agent is functioning but the building context (knowledge base, agent instructions) is incomplete. Add or review the building's knowledge base, then re-save the voice agent settings for the building.
How do I test voice without calling from my own phone?
Use the pre-activation test in the building's go-live flow, which places a test call to the manager's phone. This lets you confirm the voice setup works before guests or guests start calling.

Was this article helpful?

Related articles