An AI receptionist for electricians

Configuring an answering system for an electrical shop is mostly an exercise in restraint. The trade has a safety dimension that no automated voice should go anywhere near, and the discipline of writing down what it must refuse to do takes longer than everything else combined.

The refusal list comes first

Before any script exists, there should be a written list of what the system will not do under any circumstances.

It will not suggest resetting a breaker. It will not suggest checking, opening or looking inside a panel. It will not suggest testing an outlet, unplugging something to see what happens, or any other action involving contact with electrical equipment. It will not offer an opinion about whether a situation is safe.

These sound obvious and they are not the default. Systems configured from a generic trade template will cheerfully offer a helpful suggestion, because helpfulness is what they were optimised for, and in this trade a helpful suggestion is a liability.

Anything that sounds unsafe goes straight to a person

A caller describing a burning smell, visible sparking, a warm outlet or a panel making noise should reach a licensed human as quickly as the system can arrange it.

The correct behaviour is narrow: take the address, confirm the caller is reachable, escalate. No questions about the property. No suggestion about what to do in the meantime. No attempt to establish how serious it is, because that judgement requires a licence.

This is a different escalation from the plumbing case described on the plumbing receptionist page, where the system is triaging urgency. Here it is recognising a category and stepping out of the way.

Charger enquiries deserve their own path

Vehicle charger installation has become one of the largest sources of new residential electrical work, and those callers are unlike any other enquiry the shop receives.

They have usually read a great deal. They know roughly what a load calculation is. They want to talk about whether their panel has capacity, what a service upgrade would involve, and how the permitting affects the timeline. Running a four-question service script on that caller wastes the most informed enquiry of the week.

The useful configuration collects what an electrician would actually want to know before visiting: the vehicle, where the panel is, the property’s approximate age, whether the garage is attached, and what amperage the service is if the caller knows. A caller who has done that much reading will happily supply all of it, and the return call starts from a real position instead of from scratch.

Panel upgrades and the permit question

Upgrade enquiries invariably include a question about how long it will take, and the honest answer depends on a jurisdiction rather than on the shop.

The system should capture the enquiry properly — property age, current service, what prompted the question — and leave the timeline to a human. A date offered on a first call and then revised because the permitting took longer is a small promise broken at the worst possible moment, and it is entirely avoidable by not making it.

The administrative trail that follows is covered on the electrical hub, and it is where a shop’s organisation becomes visible to the customer.

Service calls are the simple case

Everything that is not a safety call, a charger enquiry or a permitted project is a straightforward service enquiry: what is not working, where, when can someone come. Those should be quick, and the system should get out of the way.

The general principles are the same as any trade — answer on the first ring, take the address early, put the record somewhere a human sees. The plumbing page covers those mechanics in more detail, and the general contracting hub covers where phone coverage sits in the order of things.

What to check after a month

Listen to a sample of calls. Specifically, listen for the moments where the system was helpful in a way it should not have been, because that is where a generic configuration reasserts itself.

Existing customers and the panel on file

A shop that has worked at a property before knows things the caller does not have to repeat — where the panel is, what the service is, what was done last time.

Configuring the system to recognise a known number and confirm those details rather than ask for them changes the character of the call entirely. It also improves the information quality, because a homeowner’s recollection of their own panel is frequently wrong and your own record is not.

This depends on the records described on the electrical hub, which is the usual pattern: the answering system is only as useful as what sits behind it.

What to listen for in the first month

The configuration will drift toward helpfulness, because that is what these systems are built to do. The review should be looking specifically for that drift.

Pull a sample of calls and listen for any moment where the system offered a suggestion, softened a safety escalation, committed to a date, or answered a question it should have passed on. Each of those is a line to add to the refusal list.

A month of this is usually enough to settle it, and it is worth doing properly once rather than discovering a problem through a complaint.

Commercial calls are a different shape

An electrical shop taking commercial work receives calls from facilities people rather than from homeowners, and they behave differently — they know their building, they describe the problem accurately, and they want to know when somebody is coming.

Those calls need less qualification and more scheduling clarity. Handling them with a residential script wastes the caller’s time and makes a competent business sound like it does not do commercial work. The general contracting hub covers the broader point about building for the customer you actually have.

The demos include a receptionist you can try to push past its boundaries, which is the right way to evaluate one. Starting a project begins with the refusal list.