You blocked out a Thursday afternoon, drove forty minutes to a job two towns over, and the whole thing fell apart in the first five minutes. The budget was half what the work costs. Or they wanted three quotes and you were number one of many, mostly there to make the other guy's price look reasonable.
The frustrating part isn't the occasional dud. It's that you usually can't tell the duds from the real jobs until you're standing in the driveway, so you say yes to everything, or you play twenty questions over text for two days trying to decide if it's worth the drive.
There's a middle path. A few good questions, asked early and asked lightly, sort most of the tire-kickers and out-of-area jobs out before you ever start the truck. AI can help you write those questions and even ask them for you. The trick is keeping it a light filter, not an interrogation, because if you ask too much too fast you scare off the good customers right along with the bad.
The four questions that earn their keep
Four short questions cover almost every service business, and each one catches a different kind of mismatch before it costs you a drive. You don't need a long form to do it.
- Location. Just the town or ZIP. This is the big one for anyone who works a service radius. A job out in Worcester when you cover the South Shore isn't worth the miles, and you'd rather know that in ten seconds than after the drive.
- Job type. A quick "what are you looking to have done," in the customer's own words. A kitchen remodel and a leaky faucet are both plumbing, but they're not the same afternoon.
- Timeline. Something like "looking to book soon, or planning ahead for the spring?" Somebody pricing a deck for next summer is a real lead, just not a this-week one, and you'll follow up with them differently.
- Budget range. The touchy one. Handle it gently (more on that below), but a rough range keeps you from driving out to quote a full bath gut on a coat-of-paint budget.
None of these needs an exact answer. A ballpark on each is usually enough to tell a serious inquiry from a someday-maybe.
Put the questions where the lead already is
Ask right where people reach out, so nobody has to do extra work to answer. For most owners that's two spots: the contact form on the website, and the automatic text that goes back when someone calls or messages and you can't pick up.
On the form, turn your single "message" box into three or four short fields. Town, type of job, rough timeline, and if you like, a budget dropdown with ranges instead of a blank line. People fill in what's in front of them, so the questions quietly do the sorting while you're on a job.
Your reply-back text is the other half. When a call comes in and you can't grab it, or a lead lands at 9 PM, an automatic text can fire off in seconds: "Thanks for reaching out! Quick question so I can help fast, what town are you in and what's the job?" We set these up for folks all the time, and the honest surprise is how many people answer a friendly text at night that they'd never have called back about.
Let AI write the wording, then make it sound like you
Here's where a tool like ChatGPT or Claude (chatbots that draft text from a plain-English request) actually saves you time. You're not paid to write chirpy little screening questions, and you shouldn't have to be good at it.
Give it the raw facts and let it draft. A prompt this simple works: "I'm an electrician in Lowell covering a 20-mile radius. Write three short, friendly screening questions for my website form and one auto-reply text asking town, type of job, and timeline. Keep it casual, no corporate tone." Then read what comes back out loud.
That last step is the one people skip. AI drafts tend to land a little stiff and a little too polite, so trim them until they sound like something you'd actually say. Swap "How may we assist you today" for "What's going on over there?" The goal is a question a real person would text, not a survey.
A light filter, not an interrogation
This is where the whole thing goes sideways, so it's worth slowing down on. The more you ask up front, the more good customers you lose. Somebody with a real job and real money will bail on a form that feels like a loan application, and they'll call the next name on the list who just made it easy.
Budget is the landmine. Ask for it too bluntly and people feel judged, or they lowball on purpose to keep their options open. So soften it: use ranges, make it optional, and frame it as helping them ("so I can point you at the right option"). If someone skips it, that's fine, the other three answers still tell you plenty.
Know what the filter can't do, too. It won't tell you if someone's pleasant to work with, whether they'll pay on time, or if the "small job" is actually a can of worms behind the drywall. It sorts out the obvious out-of-area and way-out-of-budget stuff so you're not driving to Pittsfield for nothing. Reading people is still your job, and it always will be.
Go easy on the automation while you're at it. If every reply is clearly a bot, some folks smell it and drop off. Let the questions do a first pass, then step in as a human fast, ideally within the hour.
Worth doing this week
Most of this you can wire up in an afternoon. Start small and adjust.
- Write your four questions: location, job type, timeline, budget range. Keep each one to a single sentence.
- Have AI draft the friendly versions, then read them out loud and cut anything that sounds like a robot wrote it.
- Add three or four short fields to your web form in place of the single message box, and make budget optional.
- Set up one auto-reply text for missed calls and after-hours messages that asks town and job type.
- Watch it for two weeks. If good leads are dropping off, you're asking too much, so pull a question. If tire-kickers still get through, tighten one up.
If you'd rather not fuss with the form fields and the texting yourself, that's the sort of thing Massachusetts AI Agency sets up for local shops in an afternoon (617-398-0033). Either way the payoff is the same: fewer wasted drives, and more of your day spent on the jobs that were always going to happen.