# Test call diversion before AI answers customers

An answering service is only one part of the calling path. Test how your existing number reaches it, what happens when conditions change and how you restore the previous arrangement.

19 November 2026

[Voice & PSTN](https://netavo.com/insights)

## Record the current arrangement first

Identify who provides the number and who controls the phone system. Confirm which diversion options are available: all calls, busy, unanswered or a schedule. These are provider-specific settings; do not assume a mobile dial code also works on a hosted business number.

Ask the provider about diverted-call charges, caller-number presentation and any restrictions on the destination. Record the current settings and the steps needed to remove the diversion. Keep that record somewhere accessible if the person configuring the service is away.

Changing the destination of calls is different from porting the telephone number. If you are also moving providers, treat that as a separate project with its own cutover plan. Our [UK business number porting guide](https://netavo.com/insights/porting-uk-numbers) covers the preparation.

## Rehearse the paths customers will take

| Test | What to observe | What to resolve |
| --- | --- | --- |
| No answer | Let the normal phone ring without picking up | Ring duration and whether existing voicemail answers first |
| Busy | Call while the business line is occupied | Whether the call queues or reaches the answering service |
| Outside opening hours | Test the actual scheduled rule | Time zone and any holiday exceptions |
| Return to normal | Remove the test diversion and call again | Confirm the original destination rings |
| Message handover | Leave a realistic enquiry | Check that the team can find the details and follow up |

## Check the conversation as well as the connection

Use an external phone to ask questions a customer would ask. Include a routine enquiry, an unclear request and a question outside your published business information. Listen for claims about prices, availability or response times that your team has not authorised.

Check the captured callback details rather than assuming the displayed caller number is enough. Withheld numbers and provider behaviour can affect what arrives. Give a callback number during a test and confirm that the resulting message is usable.

Be explicit about the service’s limits. If the business needs emergency support, clinical advice or another time-critical response, agree a suitable human process; a general enquiry inbox is not an escalation procedure. Do not leave callers with a promise your team cannot deliver.

## Start with a defined set of calls

Begin with a routing rule that your team understands and can reverse. Keep someone available to check the first enquiries, and decide what evidence would make you pause the trial. Test changes again when you alter opening hours, routing rules or phone providers.

[Ellis](https://ellisanswers.com/) is an AI call answering service for small businesses by [Netavo Intelligence](https://intelligence.netavo.com/). Use its [product tour](https://ellisanswers.com/tour) to inspect how the inbox and business information work, and confirm the setup instructions for your own provider before enabling a diversion.

Read [about Ellis by Netavo Intelligence](https://netavo.com/services/ellis-ai-receptionist), or use our [unanswered-call planning guide](https://netavo.com/insights/planning-unanswered-business-calls) to decide which conversations should reach it. For changes to the underlying phone system, see [Netavo cloud voice and numbering](https://netavo.com/services/voice).

## Explore Ellis before routing your calls

Review the service, hear a sample and check current trial details on Ellis.

[Meet Ellis](https://ellisanswers.com/)

Source: https://netavo.com/insights/testing-ai-call-diversion
