Example workflow: catching urgent job enquiries for a plumbing business
This is not a customer story. It is an example of how we configure a deployment for this industry. There is no named company, no testimonial and no performance figures on this page, because there is no customer behind it.
This is an example of how we configure Boafo Agent for a plumbing or home services business, where the difference between an urgent job and a quote request decides what happens next. It is a configuration walkthrough, not a customer result.
The problem
When someone has water coming through a ceiling they contact whoever answers. If you are under a sink, that is not you.
Evenings and weekends are when the urgent work lands, and that is exactly when the office is shut.
Even when an enquiry does come in, it often arrives as a single line with no address, no access details and no idea how urgent it is, so the first job is chasing the customer for basics.
The solution
The agent identifies itself as AI, then triages: is this an emergency, a repair that can wait, or a quote for planned work.
For urgent enquiries it collects the things you need before you get in the van: what has happened, the postcode, whether the water is off, and the best number to ring.
You get an email alert the moment the enquiry completes, so an emergency does not queue behind a quote request.
For planned work the agent captures the job description and can offer an appointment slot from a connected Google Calendar.
Everything is written into a Google Sheet you control, so you have a record of every enquiry rather than a scroll of half remembered messages.
What this changes, and what we will not claim
This page carries no percentages or savings figures, because there is no customer here to measure. The concrete change is that an out of hours enquiry arrives with the postcode, the problem and a number to ring, instead of arriving as nothing at all.
To put a value on that for your business, use the missed call cost calculator with your own average job value.
Without the agent, and with it
| What happens | Without Boafo Agent | With Boafo Agent |
|---|---|---|
| Out of hours enquiry | Web form, no response | Answered and triaged by urgency |
| Urgent job detail | My boiler is broken | Problem, postcode, water isolated, contact number |
| Alerting you | Seen the next morning | Email the moment it completes |
| Planned work | Chased by phone | Booked into a connected Google Calendar |
| Phone calls | Rings out to voicemail | Not covered yet, voice is on the roadmap |
Implementation playbook
Step one is the content pass. We read your website, your service list and your pricing page, then train the agent on what you actually offer and how you describe it. You review the answers before anything goes live.
Step two is the enquiry pass. We agree what the agent needs to collect on every enquiry, and where it goes: your inbox, a Google Sheet you control, or both. On Growth we can post it into your CRM.
Step three is go live. We give you a single line of code for your site, or we add it for you. Most set ups are answering enquiries within 24 hours.
Step four is tuning. You read the conversation summaries in the first week, tell us what the agent got wrong, and we adjust the answers. That loop is included, not billed as extra work.
What is next
Voice and phone answering is on the roadmap and is not live today. Everything described on this page happens in website chat.
If you want to see this running on your own site, book a demo. We train the agent on your live website first, so you are looking at your own answers rather than a generic script.