Plan for the calls that are not customers

Every business phone line gets junk. Robocalls about a car warranty nobody has. Someone selling search ads. A recorded voice saying the business listing is about to be removed. A silent call that hangs up after ten seconds. When a person answers the phone, they learn to spot these in a few words and hang up. When an AI receptionist answers, it does whatever its instructions say, and most instructions say nothing at all about junk calls.

That gap matters more than it looks. The agent treats a sales pitch like a new customer. It asks for a name and address, tries to book a visit, and then sends the owner a tidy summary of a "lead" that was never a lead. Do that a few times a day and the team stops trusting the summaries. Once they stop trusting the summaries, they stop reading them, and the real calls get missed along with the junk.

So when we build voice reception for a service business, we plan for junk calls on purpose. It is part of the job, the same as booking and handoffs.

What junk calls actually cost

The obvious cost is minutes. Most voice platforms bill by the minute, and an agent that politely chats with a recorded message until it ends is paying to listen to an ad. That part is real but usually small.

The bigger costs are quieter.

Noise in the summaries. If every call produces a summary, and a share of them are vendors and robocalls, the office has to read each one to find the jobs. People are busy. They skim. Skimming is how a real emergency call gets lost between two warranty pitches.

Bad data in the system. An agent that books a visit for a sales rep, or creates a customer record for a recorded voice, puts junk into the calendar and the customer list. Someone has to clean it up later, and until they do, it throws off anything that counts customers or open jobs.

Wrong alerts. If the agent is set to text the owner for urgent calls, a pushy sales call that uses words like "urgent" or "final notice" can set off the same alert as a burst pipe. A few false alarms and the owner starts ignoring the texts.

Tied up lines. A long junk call can keep a line busy while a real customer gets a busy signal or goes to voicemail. This depends on how the phone system handles more than one call at a time, which is worth checking with your carrier.

None of this shows up as an error. The agent did exactly what it was told. It was just told to treat every caller as a customer.

Teach the agent to sort the call early

The fix starts with a short sorting step in the first part of the call. The agent's goal in those first few turns is to figure out what kind of call this is before it starts collecting details.

We usually give it four categories:

• Customer or likely customer. Someone asking about service, pricing, an existing job, or a problem at their home or business. This is the normal path.
• Known contact. A supplier, a sub, a property manager, or a staff member calling the main line. These get routed or messaged, not booked.
• Vendor or sales pitch. Someone selling something to the business. The agent takes a short message if the owner wants that, or politely ends the call.
• Automated or empty call. A recording, a long silence, or a call that does not respond to questions. The agent ends it quickly.

The agent does not need to be perfect at this. It needs to be careful in one direction. If it is not sure, it treats the caller as a customer. Losing two minutes to a pitch is cheap. Hanging up on a real customer with a leaking water heater is not.

A few rules we write into the instructions:

• The agent never hangs up on a person in the first few seconds. It asks one plain question, like "Are you calling about service at your home or business?", and listens to the answer.
• If a recording is clearly playing, the agent does not try to talk over it. It ends the call.
• If the caller says they are with a marketing company, a listing service, or a lender, the agent offers to take a name, company, and number for the owner, and says the owner will reach out if interested. It does not book anything.
• The agent is never rude. A real customer sometimes opens with a sales voice because they are nervous or in a hurry. Being polite costs nothing if the guess was wrong.
• Junk calls never trigger urgent alerts, no matter what words they use.

Keep a short list the office controls

Some numbers call over and over. The same sales company, the same recorded message, sometimes from slightly different numbers. A simple block list helps here, and it should live somewhere the office can edit without calling a developer.

In our builds that is usually a small table with the number, a label, and what to do: end the call, send to voicemail, or answer normally. The office adds a number when they see a repeat in the call log. The agent checks the list before it says anything.

The other side of that list is just as useful. Known contacts like the parts supplier, the property manager who sends half the work, or a staff member's cell can be marked so the agent greets them correctly and routes them where they need to go, instead of asking for their address like a stranger.

Carriers also offer their own spam labeling and call blocking, and many businesses have it turned on already. It catches some of the obvious robocalls before they ever reach the agent. We treat it as a first filter, not the whole answer, because it will not catch a live sales rep and it can occasionally flag a real caller.

Log it, then look at it once a week

Junk calls should still show up in the call log. They just should not show up as leads. We tag each call with the category the agent chose, and junk calls go into their own section of the daily summary, collapsed, with one line each.

That does two things. The office can scan real calls first without wading through pitches. And once a week, someone can open the junk section and check that nothing real ended up there by mistake. If a real customer got sorted as a vendor, that is a sign the sorting question or the rules need a change, and it is easy to fix once you can see the example.

This review is also where the block list grows. A number that showed up three times this week as a sales call goes on the list. A supplier who kept getting asked for their address goes on the known contact list.

Start with last week's calls

If you already have an AI receptionist, pull last week's call summaries and count how many were not customers. Look at what the agent did on those calls. Did it try to book them? Did it send an alert? Did it create a customer record?

If the answer to any of those is yes, add a sorting step, write the few rules above into the agent's instructions, and give the office a list they can edit. It is a small change. It makes every summary the team reads a little more trustworthy, and a phone system only helps if people trust what it tells them.