Almost all the setup effort goes into the jobs you want. The list that saves you more time is the other one, the jobs you do not want, and what the phone should say when one of them rings. Write that list badly and your calendar quietly fills with work you would rather not have taken.

The short answer

Your AI front desk should turn down four kinds of job: work your licence or ticket does not cover, work outside the area you are willing to drive, job types you have decided you no longer do, and jobs where the customer needs something you cannot deliver. Everything else should either be booked straight into your calendar or passed to you as a message. Write the list in plain language before the front desk goes live, and for every no, write the sentence it says instead.

Why the no list matters more than the yes list

A front desk that books everything is not doing you a favour. It is filling Tuesday with a job three communities away that pays less than the drive, and it is putting your name on work you are not the right person to do.

The yes list mostly writes itself. You already know your bread and butter. The no list is the one you have never written down, because until now the decision lived in your head and you made it on the phone, in about two seconds, based on things you never had to explain to anyone.

That is the real work here. An AI front desk only knows what you tell it, and "I would just know" is not something you can tell it. So you have to say it out loud once.

The four kinds of job worth turning down

1. Work your licence or ticket does not cover. This one is not a judgement call. If the work sits outside what you are licensed, certified or permitted to do, your front desk should never book it, no matter how good the job sounds or how busy the week is. Give it the plainest possible line and a pointer somewhere else.

2. Work outside the area you will actually drive. You cover HRM, but you probably do not cover all of it equally. A small repair out past Musquodoboit Harbour and a small repair in Dartmouth are not the same job, because one of them is well over an hour of unpaid driving round trip. Set the boundary by job value, not just by postal code: you might drive an hour for a full install and twenty minutes for a service call.

3. Job types you have quietly stopped doing. Every trade has these. The drain you no longer snake, the oil equipment you stopped touching, the one-off warranty work for a brand you gave up on. You stopped saying yes to these a year ago, but your website, your Google listing and your old customers have not caught up. Your front desk needs to know they are off the menu.

4. Jobs where you cannot give the customer what they need. Someone wants a technician this afternoon and you are booked into next month. Someone needs a stamped drawing you do not produce. Someone has a rental dispute they want a report for. Nothing is wrong with any of these callers. They are just not your job today, and holding them in your calendar for three weeks helps nobody.

How do I tell my AI receptionist which jobs to refuse?

You give it three outcomes rather than two. Most owners set this up as book or do not book, and that is where it goes wrong, because a lot of calls sit in the middle. Here is the shape that works.

Outcome Use it when What the caller hears
Book it The job is on your yes list, in your area, and the timing works Confirmation with a date, a time window and what to expect
Take a message You would probably say yes, but there is something only you can decide That you will call back, and roughly when
Turn it down The job is on your no list for one of the four reasons above A plain no, a reason, and where else to try

The middle row is the one that saves you. If a call is unusual, borderline, or a repeat customer asking for something odd, you do not want the front desk guessing. You want it to be honest, take the details and hand the decision to you. Every no you are not sure about should start life as a message.

Once you have the three outcomes, write the actual rules the way you would explain them to a new apprentice on their first day answering the phone. Not "screen out low-value work." Instead: "Do not book anything past Porters Lake unless it is a full replacement." Specific enough that a stranger could apply it without asking you.

The one rule that sits above the no list

Before any of the four rules run, your front desk needs a safety override. If a caller says they smell gas, suspects carbon monoxide, has water near live electrical, or describes anything else that sounds dangerous, the answer is never a refusal and never a message. It is to tell them to get out and call 911 or the utility's emergency line right now, and to say it first, before anything about your service area or your calendar.

Write that override at the top of the list, not the bottom. It is the one case where the wrong script does real harm, and it takes two sentences to get right.

Saying no without losing the customer

A turned-down call is still a person who has now heard your business name. The difference between a good no and a bad one is about one sentence.

A bad no is vague and leaves them nowhere. A good no does three things: it says no clearly, it gives one honest reason, and it points somewhere else. "We do not do that kind of work anymore, but a gas-certified shop will. Try searching for one in Bedford" costs you nothing and takes the sting out.

Two things worth avoiding. Do not let the front desk apologize at length, because it reads as a machine stalling. And do not let it hedge into a maybe. A soft no turns into a voicemail, then a follow-up, then a phone call from you three days later to say the thing it should have said at the start.

If your no is really about price rather than fit, that is a different problem and there is a different answer for it. We wrote about what a front desk should and should not say about pricing separately.

What getting this wrong actually costs

It costs you in both directions, and the two are not symmetrical. Turn down too much and you lose jobs you wanted. Turn down too little and you lose whole days.

Run rough numbers on your own business and you will see which side you are on. Here is an illustration using round made-up figures, not our data or anyone's. Say you take on four out-of-area service calls a month you would have refused in person, and each adds ninety minutes of driving. That is six hours a month, most of a working day, spent on the highway rather than on a job. Put your own hourly rate against those six hours and compare it to the margin on those four calls.

To check the other direction you need the refused calls written down, so have the front desk log every one of them with the caller's name, number and what they wanted. Read that list once a week. The number to watch is how many of last month's refusals are jobs you would have taken: if it is more than one or two, your rules are too tight. This is the same arithmetic as working out what your missed calls cost you, just pointed at the jobs you said no to on purpose.

Then check the no list again every few months. Trades change what they do faster than they update their website, and a stale no list turns away work you would now happily take.

Questions, answered

Should my AI front desk ever turn down an emergency call?

Only if it truly is not your trade or not your area, and never before the safety override above has run. An emergency caller is someone with an urgent problem and nobody already booked, so the bar for refusing one should sit higher than for a routine job. If you are simply full, take the message rather than refusing, and let the caller know honestly that tonight is unlikely.

What if I want to say yes to a job the front desk already refused?

You catch it in the weekly log. Have the front desk record every turned-down call with the caller's name, number and what they wanted, then read the list on a set day each week and ring back anyone you would have taken. It is also the cheapest feedback you will get on whether your rules are set right.

How specific do the rules need to be?

Specific enough that someone who has never met you could apply them. Name the communities, name the job types, name the dollar threshold if you have one. Vague rules like "only good jobs" give you unpredictable results, because the front desk has to guess what you meant.

Can I set different rules for different times of day?

Yes, and most trades should. What you want handled at 2am is not what you want handled at 2pm, and the same call can be a booking during the day and a message overnight. Set the daytime rules first, get them right for a few weeks, then add the after-hours version.

Does turning down work hurt my Google ranking or reviews?

Reviews are the part you can actually affect, and a clear no rarely costs you one. What people write reviews about is how they were treated: no answer at all, a vague brush-off, or a booking you cancel on them later. On ranking, Google's own guidance talks about relevance, distance and prominence, and says nothing about which jobs you accept. If reviews are the real worry, our guide to asking for them is the better place to start.

Hear it handle a real one

The fastest way to know whether your rules are right is to listen to them being used. Book a 15 minute call and we will ring the front desk right there so you can hear it take a customer, screen the job and put it on the calendar. The Front Desk plan is $297 a month CAD, no contract, and the rest is on the pricing page.