60 seconds, not 8 hours
Most small businesses do not lose enquiries to a competitor's better offer. They lose them to a slow reply. This page describes one small business where the wait for a first reply used to be about 8 hours and is now about 60 seconds. The AI drafts the reply, and a named person approves it before anything goes out. Nothing is sent on its own.
What it replaced
Enquiries came in by email, through the website and by message, during the day and through the night. They collected in one shared inbox until someone with the right knowledge had a free half hour. That person was also running the business, so the wait for a first reply was about 8 hours.
The replies were good when they arrived. The person writing them knew the answers. The trouble was timing. By the time the reply landed, the enquirer had usually written to other businesses as well, and the first one to answer tends to set the terms of the conversation. The cost never appeared as a line in the accounts. It appeared as enquiries that went quiet.
What the system does
The system works through four steps for every enquiry, in the same order each time.
First, it reads the enquiry in full. It works out what is being asked, which dates or quantities are involved and whether anything is missing. A message that says "are you free next weekend for four" has several questions hidden inside it, and the system lists them before it does anything else.
Second, it checks the diary. It looks at availability in the calendar or booking system the business already keeps, so the reply can say what is actually free instead of promising to check and come back. This is the step that used to mean opening another screen and cross-checking by hand.
Third, it drafts the reply in the enquirer's language. If the enquiry arrives in Italian, the draft is in Italian. If it arrives in English, the draft is in English, in the plain tone the business already uses with its customers. The draft answers what was asked, offers the options that are really available and asks for whatever is still missing.
Fourth, a named person approves and sends. The draft appears next to the original enquiry. The person reads it, changes a line if they want to and sends it. If nobody approves, nothing goes out, and that is the point.
The 60 seconds is the time from the enquiry arriving to a reply that is drafted and approved. It assumes a person is there to approve, and we say that plainly, because the system speeds up the work but does not replace the person who owns it.
What stays human
Everything that needs judgement stays with the person. Pricing exceptions, a difficult customer, an unusual request, a promise the business has not made before. When the system is unsure, it flags the enquiry for a person instead of guessing, so every edge case reaches a human. The decision to send is always a person's, and so is everything after the first reply, such as the call, the quote and the yes.
The business also keeps control of its own voice. The person who approves can rewrite a draft completely, and those corrections are useful to us when we adjust the system in the weeks after it goes live.
What it took to set up
Days, not months. Most of the time did not go on technology. It went on the owner describing how they actually answer enquiries, reading through past replies together and agreeing which questions the system should never try to answer alone. Connecting the inbox and the diary was the shorter part. The aim throughout is a low technical burden, so the team keeps the tools they already use and the approval step sits where they already read their messages.
What we would do differently
Three things. We would write down the five questions every enquiry asks before connecting anything, because that list shapes the whole draft and is quicker to agree on paper than on a live system. We would name the approver and a back-up on day one, since the speed of the reply depends on a person being there. And we would start with the two or three most common types of enquiry and add the rest later, instead of switching everything on at once. Teams trust a system faster when its first week is narrow and a little boring.
What it is worth
Whether a faster first reply is worth it depends on the business, so we measure it rather than argue about it. On a Proof Sprint or Core Build, our guarantee reads as follows.
Measurable ROI in 90 days — or 50% of your project fee back.
Retainers are month-to-month and sit outside the guarantee.
If your enquiries wait hours for a first reply, the 15-minute audit is the place to start. We look at where they arrive, how long they wait and what a drafted, approved reply would change. It costs nothing. Book it here.
Want that question answered for your own business?
Book a free 15-minute audit, or reply to get a one-page written audit within two working days.