Calls Not Reaching Voice AI After Forwarding

Last updated: September 28, 2026

Overview

Eve's Voice AI answers on its own phone number. Your phone system reaches it the same way it reaches any outside line: a forwarding rule sends the call to that number, and the Voice AI picks up.

When a forwarded call goes unanswered, the break is in the forwarding rule, the number that rule points to, or your provider's permission to forward outside your organization. Nothing on the Eve side needs changing to fix it.

Your agent's phone number is in Settings → Intake, in the [Firm] Intake Agent section. It is read-only.

Start here

The first question to ask yourself: did the call reach your phone system at all? To check this:

  1. Open your phone provider's call logs.

  2. Find your call by the time you placed it and the number you called from.

  3. Check whether the log shows the call arriving, and whether it shows an outbound leg to the Voice AI number.

What the log shows

What it means

Go to

No record of the call

The call never reached your phone system, so no forwarding rule could have fired

Contact your provider about the intake line itself. Nothing in this article applies.

Call arrived, no outbound leg

The rule did not fire

Causes 1 through 4

Call arrived, outbound leg failed or was rejected

The rule fired and the call was refused

Causes 1 and 5

Call arrived, outbound leg connected

The call reached the Voice AI

The Voice AI answers but no lead appears

Cause 1: The forwarding rule points to the wrong number

The most common cause by a wide margin. Usually the number was retyped by hand, or pasted with formatting the provider rejects.

  1. Go to Settings → Intake and find the Phone number field in the [Firm] Intake Agent section.

  2. Copy the number exactly as shown.

  3. Open your phone system's admin panel.

  4. Open the forwarding rule for your intake line.

  5. Compare the destination number against the number from Eve, digit by digit.

  6. Retype the number rather than pasting it, so no hidden characters carry over.

  7. Enter it in the format your provider expects. Most require the country code, for example +16505550100, and reject parentheses, spaces and dashes.

  8. Save the rule, then wait two to three minutes for the change to take effect.

Cause 2: The rule was not active when you tested

  1. Open the forwarding rule in your phone system's admin panel.

  2. Confirm the rule status is set to enabled or active.

  3. Check the rule for time-based conditions, for example forwarding only after 5 PM or only on weekends.

  4. Compare those conditions against the time and day of your test call.

  5. Check the time zone set on the rule. A rule left in the wrong time zone fires hours off schedule and looks broken at random.

  6. Check the holiday or exception calendar, if your provider has one.

  7. Adjust the conditions to match the hours you want calls routed to the Voice AI, or test again inside the hours already set.

Cause 3: The rule is on the wrong line

Most firms have a main number, a ring group, and individual direct dials. A rule set on one of them does nothing for calls arriving on another.

  1. Confirm which number your clients actually call. Check what is published on your website, your advertising, and your Google Business profile.

  2. In your phone system, trace that number to whatever answers it first, which may be an auto attendant, a ring group, or a queue.

  3. Confirm the forwarding rule sits on that destination rather than on an individual extension.

  4. If calls pass through an auto attendant, confirm the menu option your callers use also forwards to the Voice AI.

  5. Save, then place a test call to the published number rather than to an internal extension.

Cause 4: The forward times out before the Voice AI answers

Rules that forward after a set number of rings can expire before the outbound call connects, which sends the caller to voicemail instead.

  1. Open the forwarding rule and find its ring count or timeout setting.

  2. Note how long the rule waits before forwarding.

  3. Add at least 20 seconds of headroom, or lower the ring count, so the forward has time to connect.

  4. Confirm voicemail is not set to answer before the forward fires.

  5. Save, then place a test call and let it ring without hanging up.

Cause 5: Your provider does not allow forwarding to external numbers

Some phone systems forward only to internal extensions. Others allow external forwarding but require it to be switched on per line.

Eve Intake integrates with Zoom, RingCentral, Dialpad, CallHarbor and SpectrumVoIP, and your phone system must be able to record calls. On RingCentral, confirm the account is RingCentral EX rather than CX, RingCX or Ring Contact Center.

  1. Contact your provider's support team, or search their documentation for "external call forwarding" or "forwarding to outside numbers."

  2. Ask whether your plan allows forwarding to numbers outside your organization.

  3. If it is available but switched off, ask for it to be enabled on your intake line.

  4. If it is not available at all, ask whether the provider supports SIP forwarding or another route to an external number.

  5. Once external forwarding is confirmed, update the rule with the number from Eve.

  6. Place a test call to confirm the Voice AI answers.

Confirm the fix

Place a test call to the number your clients call, from a phone the agent has not seen before. A working setup does all three of these:

  1. The Voice AI answers, and the caller can hold a conversation with the agent.

  2. Your provider's call log shows a connected outbound leg to the Voice AI number.

  3. A new lead appears under Intake → Leads within a few minutes, carrying a transcript and a score.

Close out test leads with an accurate reason when you are finished, so your reporting stays clean.

The Voice AI answers but no lead appears

Forwarding is working. The lead is created after the call ends rather than during it, so wait a few minutes and refresh Intake → Leads.

New lead email notifications fire only for voice agent calls, and only when recipients are set under Settings → Intake. A missing email is not by itself evidence of a missing lead, so check the Leads page before treating it as one.

If no lead arrives after a few minutes, contact support with the time of the call and the number you called from.

What this article does not cover

  • Calls that reach the Voice AI but score or transfer incorrectly. Those are scoring and call transfer rule settings rather than forwarding.

  • Leads created through email lead capture or the Lead Creation API, neither of which involves call forwarding.

  • Configuration inside your phone system, which only your provider's support team can change on your account.

If none of this resolves it

Contact support with the following, which is everything needed to trace a single call end to end:

  • The exact date, time and time zone of your test call

  • The number you called from and the number you called

  • Your phone system provider and plan

  • A screenshot of the forwarding rule, including its conditions

  • The matching entry from your provider's call log

Related articles