To qualify a new inquiry with AI, you need two things in place before the phone rings: a short list of facts that make a job quotable, and a decision rule for what to do once you have them. Beside answers inbound calls, asks the qualifying questions you configure, and applies routing rules you set to sort calls toward a book, a quote-pending, an escalate, or a decline outcome. That four-way sort is a workflow you configure and test, not a documented, guaranteed classification for every phrasing a caller might use. Beside captures the facts and writes them down; whatever tool or person turns those facts into a price, that price needs your approval before it ever reaches the customer.
We answer calls for small businesses all day, and the owners we work with rarely describe their problem as spam calls specifically. They describe getting interrupted by a call that turns out to be outside their service area, not urgent enough to justify dropping what they're doing, or simply not a job they take, and the interruption cost them the same ten minutes whether the caller was a good fit or not.
| What | Detail |
|---|---|
| What one job is worth | An average plumbing job costs $341, typically ranging $182 to $501 (HomeAdvisor, updated June 2026). |
| What an unqualified call costs | The same ten minutes as a good one, plus a possible wasted trip if location or scope was wrong. |
| What to automate first | The decision, not just the capture: which calls to book now, quote later, escalate to you, or decline. |
| What Beside costs today | Baseline $29/mo per user (30 AI-answered calls/mo) or Unlimited $99/mo per user (uncapped, 7-day free trial). Beside's own FAQ text shows $29.99/$99.99 per user; one phone line is included per user, and extra lines are $4.99/mo each on either plan. Verified on beside.com/pricing, 2026-09-23. |
The five facts that make a job quotable in one pass
Every intake guide talks about collecting information. Almost none say which information, which is the only part that matters. For physical work, a complete intake is short, and each item earns its place by deciding something.
| What to capture | Why it decides the job | What it costs to get later |
|---|---|---|
| A name and a number that reaches them | Everything else on this list is worthless without it | The whole job |
| The address, said back and confirmed | Sets travel, access, and whether it's even your service area | A wasted trip or a re-quote |
| What is actually wrong, in their words | Sets parts, time, and price | A second visit |
| When it broke and how urgent it is | Decides today versus Thursday, and premium versus standard | The emergency premium |
| How they found you | The only marketing data you'll ever get for free | Gone for good |
The qualification decision tree: book, quote-pending, escalate, or decline
Once you have the five facts, the question isn't 'do I have enough information,' it's 'what do I do with this caller.' Run every call through the same five checks, in this order, so the answer is the same whether you or an AI is on the phone.
- Requested service: is it a service you actually offer? If not, decline respectfully and, if you have one, refer them elsewhere.
- Service area: is the address inside where you travel? If it's borderline, flag it for you rather than guessing a travel fee.
- Urgency: same-day emergency, this-week, or flexible? This sets whether the call needs you now or can wait for a callback window.
- Scope: does the description match a job you can quote from a call, or does it sound like it needs an on-site look first? Say 'needs an estimate visit' instead of naming a number.
- Timing: do they need an appointment window today, or are they fine being called back? This decides whether the AI books directly or holds the details for you.
Beside's lead qualification runs on rules and custom questions you set, and its scoring and routing decide where the call goes before it ever reaches your team; a documented scoring formula isn't published, so treat this as configurable behavior you set up and test, not an automatic guarantee for every phrasing a caller might use. When a call needs a person, Beside can transfer it live and introduces the call with context so your team isn't starting cold.
Worked example, plumbing: a caller says their kitchen faucet has been dripping for two weeks, they're free any day this week, and the address is fifteen minutes outside your usual radius. Requested service: yes, you do faucet repair. Service area: borderline, so this gets flagged for you instead of an automatic yes or no. Urgency: low, so it doesn't need to interrupt you today. Scope: a simple repair, quotable without a visit. Timing: flexible, so a callback window works. Result: quote-pending, held for your five-minute review, not booked automatically and not escalated live.
Worked example, appointment: a caller wants their annual water heater flush and any day next month works. Requested service, service area, and scope are all clear yes; urgency is low; timing is flexible. Result: book directly onto the calendar, no owner review needed.
Thanks for calling — that's outside the area we service, so I don't want to send someone out and waste your time. If you'd like, I can text you a couple of other local plumbers, or you're welcome to call back if that changes. — Illustrative decline script, not a recorded call
A respectful decline names the reason (out of area, not a service you offer, doesn't meet a minimum job size) and offers something instead of a flat no, whether that's a referral or an invitation to call back if circumstances change.
I have a caller on the line who says there's water coming through their ceiling right now — I'm connecting you now, they're waiting. — Illustrative escalation handoff, based on Beside's call-transfer feature, not a recorded call
An emergency, a high-value job you don't want automated away, or a caller who's upset are all reasons to escalate live rather than let the call go to a summary. Set that threshold explicitly (a specific phrase, a specific urgency answer, a repeat caller) so it isn't left to judgment mid-call.
Why an AI shouldn't quote a price on the call itself: Beside's own guidance for emergency-style trades is to qualify and capture, not name a number, because a price given before anyone has seen the job rarely survives contact with the actual job, and a caller who books on a promised price you then have to revise starts the relationship annoyed. Whoever or whatever prepares the eventual quote, keep an approval step in place before any price reaches the customer — that safeguard is what protects you, not whether the drafting itself happens automatically.
An editable phone-intake card
| Question | What you're deciding |
|---|---|
| What can I help you with today? [service type] | Requested service — do you offer it? |
| What's the address, and can you confirm the zip? [location] | Service area — is it in range? |
| Can you describe what's happening, in your own words? [scope] | Complexity — quotable now or needs a visit? |
| Is this something that needs attention today, or can it wait? [urgency] | Today vs. scheduled, standard vs. emergency rate |
| When would you like someone to come by, or should we call you back? [timing] | Book directly vs. hold for owner review |
| How did you hear about us? [source] | Marketing attribution, not job-critical but free to capture |
A worked example: one call that gets booked, start to finish
Someone's AC quit. They found you on Google, they're calling three numbers, and yours is second. An average AC repair costs $417, typically ranging $172 to $664 (HomeAdvisor, updated June 2026).
- It gets answered. Not on the fourth ring, and not by hold music. Someone dialing three numbers stops at the first that picks up.
- Name and number, captured at hello, before anything later can go wrong.
- The address, repeated back. The fact that matters most and gets fumbled most.
- What is wrong, in their words: 'it's blowing warm and there's water round the bottom' beats 'AC repair,' because one tells you what to bring.
- Urgency: today or Thursday is the caller's answer to give, not yours to guess.
- Result: requested service yes, area yes, scope quotable, urgency high. Booked directly for today, with a summary and the transcript behind it, so the quote goes out from a parking lot.
Even if I'm teaching in the classroom, the phone is buzzing off, I get a ten-minute break — sometimes I don't have time to write stuff down. — Theodore S., The OA Firearms
The call got answered. The facts didn't get captured, and a call you answered but never wrote down is worth about what a missed one is. Qualification only works if the decision and the facts land somewhere you'll actually see them.
Test the AI before you trust it on a real call
Before you point real customers at any AI intake tool, call it yourself and try to break it. Beside publishes a live public demo line (+1 424-855-1231) where you can hear a generic, unconfigured version answer, ask questions, and qualify a call; confirm the number is still live before you rely on it, since demo lines change. That's a useful first listen, but it isn't set up for your trade, so the second step matters more: start a trial, configure your own qualifying questions, and run at least three real-style calls through it yourself, including one clear book, one clear decline, and one edge case (borderline area, ambiguous urgency), before you let it answer live customers unsupervised.
- Call the demo line and listen for how it asks and confirms the five facts.
- Start your trial and load your own service area, service list, and decision thresholds (what counts as an emergency, what's out of area).
- Run a clear 'book' call through it and check the booking or summary lands correctly.
- Run a clear 'decline' call (a service you don't offer) and check the tone and referral behavior.
- Run one deliberately borderline call (address at the edge of your area, ambiguous urgency) and check it escalates or flags for review instead of guessing.
Recording and consent: a caution, not a compliance claim
Be careful here, because Beside's own pages currently describe this differently. Its pricing page advertises 'call recording & consent notice' as a feature, with an automatic consent notice built in and the ability to exclude specific contacts from recording. A separate Beside article on recording says the opposite in places: that Beside 'does not technically record audio' and instead listens in real time and generates a summary and transcript, specifically to avoid consent issues. We can't resolve that conflict for you, so don't take either version as settled. Whether a call can be recorded, and whether you need one-party or all-party (two-party) consent, depends on your state and the states of everyone on the call; a handful of states, commonly cited examples being California and Florida, require all-party consent. Confirm the actual rule for your state and channel, and read the full recording guidance, before you turn on any recording or disclosure feature.
Automate one channel at a time
Intake arrives on three channels and lands in three different places, which is the actual mess. Start with the channel that carries the most first-time customers, and for most trades that's the phone by a wide margin. The phone is where the strangers are, and the only channel where the information is gone if nobody catches it live. Texts are easier because the words are already written; the work is getting them off one person's phone and somewhere the business can see. The web form is already solved by the rest of the internet: cut it to the five facts, make each required, and have submissions land somewhere that notifies you. Finish qualifying one channel before starting the next.
Where the intake has to land
A perfect qualification decision that lands in an app nobody opens is a lost job with better records. Before paying for anything, ask where each of the five facts and the book/escalate/decline decision ends up, and whether it reaches the software you already run jobs in.
Beside currently integrates with QuickBooks, HubSpot, Salesforce, Zoho Flow, Follow Up Boss, Pipedrive, Attio, Notion, Slack, Google Contacts and Sheets, Square, Shopify, Teams, and Zapier. It does not currently publish a Workiz, ServiceTitan, Jobber, or Housecall Pro integration. If you run one of those field-service tools, run three real calls through a trial and watch where the qualification decision actually lands before you commit.
We found no public documentation describing automated geofencing for service-area matching. Treat matching your service area as a setup step you configure yourself through rules and custom questions, not something that happens automatically.
| Option | What it costs | What you get | Where it breaks |
|---|---|---|---|
| Beside Baseline | $29/mo per user (page FAQ text: $29.99/user/mo) | Up to 30 AI-answered calls/month per user, with lead qualification, call routing, and transfer on every plan. One phone line included per user; extra lines $4.99/mo each. | Behavior once you exceed 30 calls in a month isn't documented; don't assume a graceful fallback |
| Beside Unlimited | $99/mo per user (page FAQ text: $99.99/user/mo), 7-day free trial | Uncapped AI-answered calls per user, same qualification and transfer features. One phone line included per user; extra lines $4.99/mo each. | Multiple lines and multiple seats multiply the monthly cost, not just a flat add-on |
| Voicemail and call back | Free | A name and a number, sometimes | You're calling back as an unidentified number, which many callers won't answer |
| A human answering service | Per minute or per call, varies by vendor | A person taking a message | Cost scales with your busiest month, and qualification depends on the operator's script |
| Write it down yourself | Free | All five facts, on the days you have a hand free | The days you don't |
FAQ
What information should I collect from a new customer before I can quote the job?
Five things: a name and a reachable number, the confirmed address, what is wrong in their own words, how urgent it is, and how they found you. With all five you can run the decision tree — book, hold for a quote, escalate, or decline — without a second call.
What qualifying questions should I ask before booking a job?
Ask, in order: what service do they need, is the address in your service area, how urgent is it, does the scope sound quotable from a call or does it need an on-site look, and when do they want it done. Answer those five and you know whether to book, hold for a quote, escalate to you live, or decline.
So where does a captured intake land?
With Beside, it lands in Beside: it creates contacts, transcribes and summarizes every call, and afterwards sends a summary with suggested actions and calendar events.
Do I need a CRM to automate my intake process?
No. Intake has to land somewhere you actually look, which for a small shop can be a shared number and a summary on your phone. A CRM matters once more than one person needs the same information.
How much does it cost to automate intake and qualification for a small business?
As of 2026-09-23, Beside's pricing page lists two plans, priced per user: Baseline at $29/mo per user for up to 30 AI-answered calls a month, and Unlimited at $99/mo per user, uncapped, with a 7-day free trial; the same page's FAQ text shows $29.99 and $99.99 per user, so confirm the live figure before you buy. Both plans include lead qualification, call routing, and transfer to you, with one phone line included per user and extra lines at $4.99/mo each. Weigh that against one job: an average plumbing job costs $341 on average (HomeAdvisor, updated June 2026).
Sources: HomeAdvisor on plumbing costs ($341 average, $182–$501 range) and AC repair costs ($417 average, $172–$664 range), both updated June 2026. Beside pricing, features, and integrations verified on beside.com/pricing and beside.com/integrations on 2026-09-23; Beside's recording guidance verified on beside.com/blog/how-to-record-phone-calls-safely-step-by-step-guide.