# Plan what happens when nobody can answer

A working phone line does not guarantee a useful response. Plan the moments when everyone is busy, the office is closed or a customer needs something your first point of contact cannot resolve.

19 November 2026

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

## Start with the caller’s next step

Write down the main reasons people call: a new enquiry, a question about an existing job, a change to arrangements or an urgent problem. For each reason, decide what the caller needs before the conversation ends. Sometimes that is an answer; sometimes it is a clear explanation of what happens next.

Separate calls that need a person immediately from those that can wait for a callback. Do not put an urgent support line into a general enquiry workflow without an agreed escalation route. An answering service should not promise that someone will respond within a particular time unless your team can meet it.

Look at three situations separately: nobody answers, the line is busy and the business is closed. A single all-day rule may be simple, but it may send calls away when a colleague could have helped.

## Match the response to the work

| Approach | Useful when | Check before choosing |
| --- | --- | --- |
| Team or reception | A person needs to make a judgement or resolve the issue immediately | Cover during breaks and competing calls |
| Voicemail | The caller only needs to leave a message | Who checks messages and when callbacks happen |
| AI call answering | Routine questions and enquiry capture can follow approved business information | Accuracy of answers and the boundaries of what it can promise |

## Make the handover actionable

Decide what a useful enquiry contains. A name, callback number, reason for calling and relevant location may be enough. Ask for details that help someone act, rather than collecting information simply because a form has a field for it. Consider whether sensitive details are necessary before asking callers to provide them.

Assign responsibility for the inbox. Agree who checks new messages, how the team records follow-up and what happens during absence. An unanswered call becomes a service problem again if a captured message has no owner.

Review a small sample of real enquiries after launch. Were the details sufficient? Did callers ask something the answering service could not explain? Use those findings to improve the instructions and staffing arrangements, without inventing answers to fill gaps.

## Where Ellis can help

[Ellis](https://netavo.com/services/ellis-ai-receptionist), by [Netavo Intelligence](https://intelligence.netavo.com/), uses your business information to answer questions and capture enquiries, with calls available to review. It suits the parts of the workflow where you need a useful first conversation while your team is occupied.

See the [Ellis product tour](https://ellisanswers.com/tour) to judge the handover for yourself. For a closer look at the choice of answering method, Ellis also has a [guide comparing AI answering with voicemail](https://ellisanswers.com/comparisons/ai-answering-vs-voicemail).

Before routing customers, work through our [call diversion test plan](https://netavo.com/insights/testing-ai-call-diversion). If the wider phone system needs changing, Netavo can discuss [cloud voice and numbering](https://netavo.com/services/voice).

## Put the call experience to the test

Explore Ellis’s answers, call inbox and current UK trial details before deciding which calls it should handle.

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

Source: https://netavo.com/insights/planning-unanswered-business-calls
