Skip to main content
EzyConn
An engineer in workwear, seen from behind, adjusting the valves on an open wall-mounted boiler

3 processes for home services · 1 complete

An AI receptionist for HVAC, plumbing and electricalthat actually books the visit.

Somebody messages at nine at night with no hot water. EzyConn checks the postcode is one you cover, works out whether it is heating, plumbing or electrical, takes a number that dials, offers times your diary genuinely has free, and books a real appointment for the length that trade takes.

Start freeRead the limits first

The limit, up front: The job sheet carries a postcode, not a street address, and you can offer three services.

The problem

The week this is actually for

Four situations that need answering and need no judgement at all. Every one of them is somebody being interrupted, or a customer going somewhere else.

  1. 01

    Nobody answers a phone from a loft

    The people who can answer the question are the people holding a torch over a boiler. The phone rings out, the customer works down the list, and you never find out it happened.

  2. 02

    A fifth of the calls are outside the patch

    Twenty minutes about a boiler in a town you stopped covering two years ago — and you find out at the end, after taking the name, the number and the fault. EzyConn asks the postcode first, before it promises anything, and stops there if you do not cover it.

  3. 03

    The when-can-you-come loop

    Four messages to agree Thursday morning and a fifth to change it to the afternoon. It is the most common conversation in the business, it needs no judgement at all, and nobody is paid for it.

  4. 04

    Saturday night, water coming through a ceiling

    Offering somebody Tuesday at two while their kitchen fills up is worse than saying nothing. That message needs a person, a postcode and a number that dials — not a diary.

Gloved hands offering a threaded elbow up to a radiator, two pipe wrenches lying on the bench

Real enquiries

What arrives, and what happens to it.

These are the phrases the processes are built to recognise, written the way a customer types them at half past eight on a Sunday.

  • Boiler's not firing and there's no hot water — can someone come out?

    Coverage checked, trade worked out, visit booked

  • There's water coming through the kitchen ceiling. How fast can you get here?

    Coverage checked, details taken, a person put on it

  • Half the sockets upstairs have gone dead. Do you cover DE22?

    Coverage answered from your own postcode list

  • I've got a visit booked Thursday morning and I can't be in.

    Appointment found, moved or cancelled

  • Kitchen drain's blocked again — what's the soonest you've got?

    Real openings offered, visit booked

The processes

Three processes, built for home services.

Each one is published with its status. Complete means every step runs. Available with a limit means it runs and something named is missing — and the name of the missing thing is on this page and on the process page.

Every industry runs on the same handful of shapes carrying different data, which is why a new trade is a configuration change rather than a rebuild. Browse the whole catalogue.

The outcome

What a finished job looks like.

Not a form submission and not a callback promise. An appointment in your diary, at a real time, for the length that trade takes.

HS-01

Appointment booked — new service request

These are the starting labels and lengths. You replace all of them with your own, and the times offered are computed from yours.

Heating & cooling
1 hr 30 min
Plumbing
1 hr
Electrical
45 min

HS-03

Enquiry captured and routed

Nothing is booked, on purpose. A person picks the conversation up already knowing which of these it is, who is asking and how to reach them.

  • Water coming in — a burst or a leak
  • No heat or no hot water
  • No power

The job carries the customer name, a number the phone-format check accepted, an email, the postcode, which of your three services it is, whether they called it an emergency, and whatever they typed about the fault. A confirmation email goes to the customer.

What you configure.

Five things, entered once. Every time the process offers a customer a time or a price, it is reading these — never a default we chose for you.

  • Your opening hours

  • Your timezone

  • The postcodes you cover

  • Your services, their length and their price

  • Your price list

Without opening hours and a timezone, a booking process offers nothing and hands every customer to a person. That is deliberate — an appointment at a time you are shut is worse than no appointment.

The limits

What EzyConn will not do for home services.

Trades buy this because the coverage check and the diary are real. These are the places it stops being real. None of them is hidden in a footnote or behind a toggle, and none of them is on a roadmap slide.

The job sheet carries a postcode, not a street address, and you can offer three services.

  • The job sheet carries a postcode, not a street address

    No process asks for house number and street, and the appointment has nowhere to put one. A van cannot be driven to a postcode, so somebody still confirms the address — usually on the call-back the customer was expecting anyway. If you need a full address captured by the bot, this is the limit that should stop you.

  • Three services, and no more

    A business sets its own three labels, lengths and prices — and three is the ceiling, because the service list overwrites three fixed slots rather than adding to them. A firm doing heating, plumbing, electrical and drainage has to fold drainage into one of the three.

  • Urgency is a word on the appointment. It re-orders nothing

    A customer who picks "emergency" is offered exactly the same times, in the same order, as one who picks "routine". There is no dispatch queue, no priority, no paging and no service-level rule in the platform to sort into. If you want urgent work handled differently, use the urgent callout process, which deliberately books nothing and puts a person on the conversation instead.

  • It does not know a customer of ten years from a stranger

    No step reads an existing record, so a repeat customer answers every question again. On the process that moves or cancels a visit, the match is a name, an email and a phone number typed into an anonymous chat window: careful, scoped to your workspace, and still two facts somebody else could know.

  • One engineer-shaped thing it cannot do

    There is no per-person diary. The appointment is written against the business, not against Dave — so "can I have the same engineer as last time" is never offered and cannot be honoured.

  • No calendar sync, of any kind

    Not Google Calendar, not Outlook, not Calendly. Availability is worked out only from appointments EzyConn made itself, so a time you blocked out in your own calendar is still offered to a customer.

  • No system connectors

    There is no customer-record, scheduling-system, order or field-service connector in the product. Everything that leaves does so through Zapier or a signed webhook to your own endpoint.

  • The confirmation is an email, never a text message

    No process sends SMS. The confirmation email is best-effort: if the queue behind it is down, a real appointment can be made without the email arriving. A cancellation sends the customer nothing at all — the chat window is their only confirmation.

  • Nothing is paid for in the conversation

    There is no payment step anywhere in a process. No deposit, no card, no voucher, no balance.

  • A service area is a list of postcodes, not a radius

    You give a list of postcodes or a prefix to match on, for one country. A radius is refused outright, and so is covering everywhere.

Every limit these three processes publish

Written by the people who built them, carried onto this page unedited, and shown in full on each process page.

  • A confirmation EMAIL is sent.
  • Urgency is written onto the appointment for whoever works it.
  • No individual member of staff is chosen.
  • The bot does not know whether this person is already a customer.
  • IDENTIFICATION IS NOT AUTHENTICATION.
  • A cancellation sends the customer NOTHING.
  • It moves or cancels ONE appointment — the one that matched.
  • A cancelled appointment is not RE-booked.
  • The team is NAMED, not ASSIGNED.
  • It books nothing, on purpose.
  • A business that wants urgent work BOOKED rather than escalated should install HS-01, whose urgency question carries an emergency level.

Channels

Where your customers already are.

A trade lives on the phone. That is why the phone line is not an afterthought here — the same agent that answers your website answers an inbound call on your own Twilio number.

  • Your phone line

    The channel a customer with no heat reaches for first, and the one that goes to voicemail while everyone is on a job.

    You connect your own Twilio number. Inbound only — EzyConn does not make outbound calls.

  • Your website

    The out-of-hours enquiry. Answers stream in as they are written, so nobody watches a spinner.

  • WhatsApp

    How customers send a photo of a leak and expect a reply. Two-way, with your team able to take over.

  • Email

    The enquiry form and the quote chase, answered or routed instead of sitting until morning.

  • Slack

    Where your office answers from, without learning another console.

EzyConn has no CRM, dealer-management, practice-management, EHR, order-management or field-service connector, and it does not sync with Google Calendar, Outlook or Calendly. Availability is worked out from bookings EzyConn made itself. Everything else leaves through Zapier or a webhook.

The product turns on at Starter.

Workflows, the phone line and custom actions all turn on at Starter. The free plan will answer questions; it will not run the booking process. Every plan has a published seat count and a published message allowance — no plan on this site is described as unlimited.

See what each plan includes

Questions

What home services businesses ask first.

Can it tell a customer whether we cover their postcode?
Yes, and it asks that first, before it takes a name or a number — collecting contact details for a job you can never serve wastes everybody’s time. You give a list of postcodes or a prefix to match on, for one country. A radius is not supported and never will be on this data.
Does an emergency job jump the queue?
No. Urgency is recorded on the appointment for whoever works it, and it re-orders nothing — there is no dispatch queue, no priority field and no service-level rule in the platform. For genuinely urgent work, the urgent callout process books nothing on purpose: it checks coverage, finds out what has happened, takes a number that dials and puts a person on the conversation.
Does the engineer get the customer’s address?
They get the postcode, what the job is, how urgent the customer said it was, and a phone number. The full street address is not collected by any process and there is nowhere on the appointment to store one, so somebody confirms it when they call.
We do four trades. Can we offer four services?
No. You choose your own three labels, with your own durations and prices, and three is the cap — the service list replaces three fixed slots rather than extending them. Most firms fold the fourth trade into the closest of the three and let the free-text description carry the detail.
Will it sync with our Google Calendar?
No. There is no external calendar sync of any kind. Availability is computed only from appointments EzyConn made itself, which means a job you wrote into your own calendar does not block the slot here.
Does the customer get a text confirmation?
No. No process sends SMS. An email confirmation is queued as soon as the appointment is written, and it is best-effort — if the queue behind it is down the appointment still exists but the email may not arrive. A cancellation sends nothing at all.

Keep reading.

Or read all the processes and everything EzyConn does not do.