Home services phone intake

For a plumber, an electrician, an HVAC or field-service team, the phone is the business — and it always rings when you can't answer it. You're under a sink, on a ladder, or driving between jobs when a customer calls with a burst pipe or a dead boiler. It goes to voicemail. Half those callers don't leave a message; they call the next number and book someone else. Every missed call is a missed job, and for a small field team those add up fast. The cost of missed business calls is rarely small.

Agent Vani covers that line so the call is always answered live. It picks up on the first ring and talks with the caller in real time. This is a two-way, two-way call — the caller can interrupt, explain the problem in their own words, and talk over a long answer, and the agent keeps up. It is not a phone menu, and it is not a chatbot reading scripted turns aloud. It sounds like a competent person taking the job details, which is exactly what someone with a leak wants to hear.

The focus is inbound intake. When customers call, the agent captures the service request, gauges urgency, and routes it to you — so you never lose a job because your hands were full. It doesn't quote firm prices it can't stand behind or promise arrival times it can't guarantee. It catches the work and hands you a clean, prioritised request.

What the line handles

For a field-service business, the line's value is turning a missed call into a captured, prioritised job. Typically that means:

• The service request. What's wrong, where it is, and what the customer needs — captured in their own words and structured into a job you can action.
• Urgency. Whether this is an emergency (a burst pipe, no heat in winter, no power) or a routine booking, so you can prioritise. The agent flags urgency; you decide the response.
• Service area and availability. Whether you cover their location, your general hours, and how bookings work, from the details you provide.
• Booking intent. The customer's preferred days and times and their contact details, routed into your scheduling. The agent captures the request; you confirm the slot.
• Pricing and policy basics. Call-out fee ranges, how you charge, and the policies you're happy to state on a call — without quoting a firm price for a job you haven't seen.
• Routing to you. An urgent job flagged and passed to you fast; a routine one captured for follow-up.

What to put in the knowledge base

The agent answers from the knowledge you configure. For a home-services line, keep it factual and current:

• Services you offer and the ones you don't, so mismatched calls are redirected early.
• Service area: the areas you cover, and how far you'll travel.
• Hours and emergency policy: normal hours, whether you do emergencies, and what "urgent" means for routing.
• Pricing basics: call-out fee ranges and how you charge — general enough to state honestly without quoting a specific job.
• Booking rules: how jobs are scheduled, typical lead times, and how a request should be captured and routed.
• Urgency rules: what counts as an emergency and how those are flagged and passed to you.

Keep specific quotes out of the static knowledge — the agent should capture the details and let you price the job. See sales and booking intake for how request capture works.

A typical call, start to finish

You're on a job with your hands full when the line rings. Agent Vani answers with your greeting — your business name, a steady, capable tone, in the caller's language.

"Hi, my kitchen's flooding, water's coming out under the sink — can someone come out?" Because the call is two-way and realtime, the agent doesn't run a rigid script while the customer is panicking. It listens, captures the problem and the location, and recognises the urgency. It asks the few things you need — is the water shut off, how bad is it, the address and contact number — and flags the job as an emergency, routing it to you immediately so you can decide whether to divert.

For a routine call — "my boiler's due a service, can I book next week?" — the agent captures the request, confirms you cover the area, gathers preferred times and contact details, and routes a clean booking request into your process. It doesn't promise a firm price for the flood or a guaranteed slot for the service; it captures the details so you can price and schedule. Either way, the job is caught instead of lost to voicemail, and you get a structured request rather than a half-second missed-call notification you'll never follow up.

After hours, the same line keeps catching emergencies and routine bookings so nothing is lost overnight — see after-hours coverage.

Escalation and human handoff

The agent captures and flags; you decide and quote. You configure when it hands off:

• Emergencies → flagged as urgent and routed to you immediately, or transferred live if you want, so you can respond fast.
• Firm quotes and commitments → not made by the agent; it captures the details and leaves pricing and scheduling to you.
• Anything outside its knowledge or service area → an honest "I don't think we cover that, but I'll take your details" or a clean redirect, not a wrong answer.
• Caller wants a person → honoured immediately, no loop.

Handoff can be a live transfer for a genuine emergency, a captured callback with the job details attached, or a message. The job is never dropped. See the human handoff guide.

Persona, hours, and numbers you control

You configure everything in a free control plane — no charge to set up or tune the agent. You pay only for the minutes it spends on calls.

• Persona. Set a voice that matches your business — friendly and local, or crisp and professional. You choose the greeting, how it names the business, and the default language.
• Hours. Decide when it answers: as overflow when you're on a job and can't pick up, after hours so emergency and routine calls aren't lost overnight, or all day. You set what it says outside working hours.
• Knowledge. The services, area, urgency, and pricing base above, edited as your coverage and rates change.
• Numbers. Connect the number customers already call, or a dedicated line, so no caller reaches a dead end. See product.

Start with an overflow or after-hours line and widen its hours as the captured jobs prove out.

Failure modes and how to avoid them

• Quoting a firm price. The agent should never commit to a price for a job it hasn't seen. Keep specific quotes out of the knowledge and configure it to capture details and leave pricing to you.
• Missing an emergency. If urgency isn't flagged, an emergency gets treated like a routine booking. Configure clear urgency rules so genuine emergencies reach you fast.
• Out-of-area jobs. If your service area is wrong in the knowledge, you'll capture jobs you can't serve. Keep the coverage current and redirect mismatches early.
• Trapping callers. Anyone who wants you directly should reach you or a callback immediately. No maze.
• Robotic pacing. A panicking customer with a flood needs a voice that listens and adapts, not a machine that talks over them. the two-way, interruptible design prevents this — but test it on real calls first.

Call the line yourself before customers do. Describe an emergency and a routine booking, interrupt it, and confirm the urgent job is flagged and routed to you fast. A trial with no card required lets you do this at no cost.

Getting started

Start a trial — no card needed — and configure the agent in the free control plane. Load honest knowledge: services, area, hours, urgency rules, and pricing basics. Keep firm quotes out and let it capture details for you to price. Point the agent at an overflow or after-hours line, test it hard on real calls — especially the emergency path — and widen its hours once it consistently captures jobs and flags urgency correctly. You pay only for the minutes it talks, and you stay in control throughout.

The result: the call you couldn't answer because your hands were full is answered live, the job is captured and prioritised, and an emergency reaches you fast — so you stop losing work to voicemail and start every follow-up with the details already in hand.

Why a live, two-way call matters when someone's got a leak

A field-service call is often made under stress. Water is spreading across a kitchen floor, the heating has died in the cold, or the power is out — and the caller is not in the mood to navigate a menu or wait for a beep. The way that call is answered decides whether they book you or the next number on their list.

A two-way, realtime conversation is what makes the caller feel heard in that moment. They can blurt out the whole problem in their own words — "there's water everywhere, it's coming from under the sink, I've turned the tap off but it's still going" — and the agent listens the entire time, rather than making them pause between scripted prompts. It can pick out the address, the severity, and the one safety question that matters without forcing the caller through a rigid form while they're panicking. That's a fundamentally different experience from a turn-based system that talks over the caller or resets when they interrupt.

Interruptibility isn't a nicety here; it's the whole point. A stressed caller will cut in with new information mid-sentence, and the agent needs to absorb it and adjust. Because the call is two-way and interruptible, the caller drives, and the agent keeps up — capturing a clean, prioritised job even from a chaotic call. That's what a good dispatcher does, and it's what a live agent has to do to be trusted with an emergency.

The commercial effect is direct. The calls you miss because your hands are full are exactly the ones worth the most — an emergency call-out often beats a routine booking on value. A live agent that answers on the first ring, captures the job, and flags the urgency turns those missed calls into work, instead of a voicemail you find hours later when the customer has already booked someone else.

The honest boundaries still hold: no firm quote for a job the agent hasn't seen, no guaranteed slot, and a fast route to you for anything urgent or out of scope. Within those, the realtime feel is what makes a caller trust the line with a burst pipe at 9pm. Test it before you rely on it — describe an emergency down the line, interrupt it, and confirm the urgent job reaches you fast and the details come through clean.

FAQ

Can it book jobs? It captures the service request — what's wrong, where, and the customer's preferred times and contact details — and routes it into your scheduling. It records the request rather than guaranteeing a slot, so you confirm the timing and no job is lost to voicemail.

Does it quote prices? No firm quotes. It can state your general pricing basics — call-out fee ranges and how you charge — but it never commits to a price for a job it hasn't seen. It captures the details and leaves pricing to you.

How does it handle emergencies? You configure what counts as urgent. The agent recognises an emergency from what the caller says, flags it, and routes it to you immediately — or transfers the call live if you want — so you can respond fast. See the human handoff guide.

Does it feel like a machine? No — it's a two-way, realtime conversation. A stressed caller can explain the problem in their own words, interrupt, and talk over a long answer, and it keeps up. It isn't a phone menu or a scripted turn-based bot. Test it on real calls before going live.

What does it cost, and do I need a card to try it? The control plane where you configure persona, hours, knowledge, and numbers is free. You pay only for the minutes the agent spends on calls, and you can start a trial with no card required to set up and test the line first.

Can we use our existing business number? Yes. Connect the number customers already call, or a dedicated line, so every call is answered live even when you're on a job. See product, and the cost of missed business calls for why it matters.