Fixed quote after a free call

An AI receptionist for home service businesses that books the details, not the promises

We build an AI receptionist for your phone line, website chat or text number that answers the questions you hear every day (areas covered, services, opening hours, call-out policy, guide prices you publish) from your own approved answers, collects job details and photos, creates a booking request in your field service software and sends emergencies to the on-call tech. It says it is an AI assistant and never quotes a firm price. Projects typically cost $2,500 to $7,500 and take five to eight weeks.

The problem

What an AI answering service for contractors should and should not do

A small service business cannot staff the phone all day, and a traditional answering service only takes a name and number. Customers still wait for a call back to learn whether you cover their area or do the job at all.

An AI answering service can do more, but contractors are right to worry: a bot that promises "someone will be there in an hour" or quotes a price for a job it has not seen creates angry customers. It has to be narrow, honest about being automated and quick to hand over.

What we build

What our AI receptionist for plumbers and home services includes

Approved answer library

Service areas, services, hours, call-out policy, guide prices you publish and warranty basics, written and approved by you.

Phone, chat and text

One assistant on a voice line, a website chat widget and a text number, sharing the same answers.

Job intake

Service type, address, access notes, urgency and photos collected into a booking request.

Emergency routing

Emergencies by your definition go to the on-call tech by call or text, with the details attached.

AI disclosure

The assistant says it is automated at the start and offers a person at any time.

Call and chat review

Transcripts, a weekly list of unanswered questions and an admin view for the office.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Customer calls or chats

    A customer reaches the assistant by phone, chat or text.

  2. 02 Automated

    Answers from your library

    Routine questions are answered from your approved answers only.

  3. 03 Automated

    Job details collected

    Service, address, urgency and photos go into a booking request.

  4. 04 Office review

    Office confirms

    The office confirms booking requests and calls back anything unclear.

  5. 05 Owner or office manager decides

    Price and schedule

    Firm prices, arrival windows and job acceptance are decided by the owner or office manager.

How it behaves

How the home service AI receptionist behaves

What each person sees and what runs in the background, including what happens when something goes wrong.

What the customer sees

  • A clear note that they are talking to an AI assistant
  • Straight answers about areas, services and hours
  • A booking request confirmed by the office
  • A person fast in an emergency

What the office sees

  • Booking requests with job details and photos
  • Emergencies routed to the on-call tech
  • A weekly list of unanswered questions

What the automation does

  • Answers only from approved wording
  • Never quotes firm prices or arrival times
  • Logs every conversation

Edge cases and fallbacks

Question not in the library
The assistant says it does not know, offers a call back and adds it to the review list.
Caller describes danger such as gas or sparking
Your safety instruction (such as calling the utility or emergency services) is given first, then the on-call alert.
Caller insists on a price
Guide price only, with a call back from the owner.
AI or telephony outage
Calls fall back to voicemail and the missed-call text-back.

Architecture

An AI receptionist for a service business at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Customer Call, chat, text Assistant service Voice and chat Language model Claude, Gemini, GPT Approved answers Owner-written Booking request Field service app On-call tech Emergencies Transcripts Weekly review
  • Input
  • Logic and services
  • AI step
  • Data
  • Output
  • People

How it flows

  1. 1 A customer calls, chats or texts and is told they are speaking with an AI assistant.
  2. 2 The assistant service retrieves matching approved answers and passes them, with fixed rules, to the model.
  3. 3 Routine questions are answered and job details become a booking request in your field service software.
  4. 4 Emergencies go to the on-call tech, and every conversation is logged for review.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

AI receptionist & answering service project plan

Typical time to launch: about 6 weeks, then support

  1. 01

    Discovery

    About 1 week

    Listen to real calls and messages, agree what the assistant may and may not say.

  2. 02

    Answer library

    About 1 week

    Write and approve answers, emergency definitions and after-hours wording.

  3. 03

    Build

    About 2 weeks

    Voice line or chat, retrieval, job intake, emergency routing, logging and admin view.

  4. 04

    Test

    1 to 2 weeks

    Real, tricky and emergency scenarios tested; the owner signs off.

  5. 05

    Launch

    2 to 3 days

    After-hours only first, then daytime overflow.

  6. 06

    Support

    Ongoing

    Weekly transcript review at first, then seasonal updates.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

Claude, Gemini or OpenAI models Twilio Voice and Messaging n8n AI Agent node or Laravel Jobber, Housecall Pro or ServiceM8 (route confirmed per project) Website chat widget SMS or Slack alerts to the on-call tech

Cost estimate

What it costs, line by line.

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and answer library

    Real calls reviewed, answers written and approved.

    $500 – $1,200

  • Build

    Voice or chat assistant, retrieval, intake and routing.

    $1,200 – $4,000

  • Integrations

    Telephony, field service software and alerts.

    $300 – $1,000

  • Testing and evaluation set

    Real, tricky and emergency scenarios tested.

    $300 – $900

  • Launch and training

    After-hours launch and team walkthrough.

    $200 – $400

  • Total project estimate

    $2,500 – $7,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. A voice line costs more to build and run than chat. Model usage and telephony are billed to your accounts directly.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • AI model usage: Billed by the provider per use; scales with call and chat volume.
  • Telephony: Twilio voice and messaging at published rates; a voice line costs more to run than chat.
  • Hosting: n8n Cloud from about €20 a month, or your own server.

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

EU: tell people they are talking to AI

Article 50 of the EU AI Act requires AI systems that interact with people to inform them they are interacting with AI, from 2 August 2026. We disclose in every market.

Source: artificialintelligenceact.eu

US: texting from the assistant

Text conversations run on a registered A2P 10DLC number, and opt-outs are honoured.

Source: www.twilio.com

EU and UK: processors

Voice, model and hosting providers handle caller data as processors under written contracts, and recordings are kept only as long as you choose.

Source: gdpr-info.eu

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

FAQ

AI receptionist & answering service questions, answered.

It is an AI assistant that answers your phone, chat or text when you cannot, answers routine questions from your own approved answers and takes job details for a booking request. It hands emergencies and anything unclear to a person.

It answers more questions and creates a proper job request with photos, at any hour. A human answering service is better for complex conversations; some businesses use both, with the AI handling after-hours overflow.

Only guide prices you have published, such as a call-out fee or "from" price, and it says the final price is confirmed after a look at the job. It never gives a firm quote.

It creates a booking request for the office to confirm. Direct booking into open slots is possible with some field service software, but we start with confirmation until the assistant has a track record.

Yes, mostly for after-hours and overflow calls. The key is keeping it narrow: correct details, honest disclosure and fast emergency hand-off.

Review transcripts weekly at first. Watch booking requests created, calls handed to a person, emergencies routed and questions it could not answer.

Free 20-minute call

Want this for your local service?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call