Automate quote requests: hand over the admin, keep the answer
To automate quote requests well, hand software the admin and keep the answer. Software can log every request from the form, the phone, email and WhatsApp. It can reply at once with who will call and when, collect the photos and postcode, and route the request to one named person. A person sets the price, does the visit and makes every promise.
This guide is for the owner of a building, trades or installation firm of 5 to 50 people, where you or an estimator price every job. Requests arrive through four channels. Some get two answers, and a few turn up a week late. Someone has probably offered you an AI that replies to every lead in seconds.
Speed does matter. In a study published in Harvard Business Review in 2011, James Oldroyd, Kristina McElheran and David Elkington sent a web enquiry to 2,241 US companies. 37% replied within an hour, and 23% never replied at all.
A second study, of 1.25 million leads, found that firms which tried to reach the customer within an hour did far better. They were nearly seven times as likely to have a real conversation with a decision maker as firms that tried an hour later.
Both studies are old and American, and one author ran a sales software company, so hold the exact multiples loosely. The lesson survives: many quotes are lost before anyone prices them. Automation should get a person who knows the job to the customer faster. It shouldn't replace that person with something that sounds like them.
We build business automations. We also built the quote routes on two trade sites: ES Construction, a London builder, and KOP44, a flooring and wall covering contractor in Nantes. Here is each part of a quote request, and who should handle it.
What to automate in a quote request, step by step
A quote request is a chain of small jobs. Software can do most of them. The price, the visit and the promises decide whether you win the work, and those stay with a person.
| Step | What happens | Automate it? | What a person does |
|---|---|---|---|
| Arrive | Each request becomes one record, with its channel and the time it came in | Yes | Nothing |
| Acknowledge | A reply saying who will get back to the customer, and by when | Yes, with a message a person wrote once | Writes the message, then keeps its promise |
| Collect details | Job type, postcode, photos, preferred timing | Yes, through form fields and set questions | Asks the questions only someone in the trade would think of |
| Check the fit | Is the postcode in your area, and do you do this job? | Yes, for clear cases | Decides the borderline ones, and says no kindly |
| Route | The record goes to one named owner | Yes | Covers for a colleague who is away |
| Chase internally | An alert if nobody has replied by the promised time | Yes | Replies |
| Book the visit | Free slots offered from the diary | Suggest only | Confirms, then visits |
| Price and write the quote | A draft from your templates and price list | Draft only | Sets the price, checks the scope and sends it |
| Follow up | Reminders after the quote goes out | Yes, until the customer replies | Answers questions and handles the negotiation |
| Close | Won or lost, with a reason | Prompted | Picks the reason from a short list |
Microsoft's own worked example draws the line in the same place. In its 2022 guide to quote requests, software reads the customer's email, finds them in the CRM and looks up prices. Then it hands a proposal to a member of staff, who writes the reply and sends it.
One named person for every quote request
Routing works when each request has exactly one owner and the customer knows who that is. We built KOP44's quote request flow to reach one point of contact rather than a general inbox.
A customer asking three firms for a price judges each one on the first contact. Their request shouldn't sit in a shared inbox until someone notices it. Our guide to sorting a shared inbox covers what goes wrong when everyone, and so nobody, owns an email.
Keep the rules simple. The HBR researchers named rules that shared out leads by geography and "fairness" as one reason companies replied slowly. One owner per job type, one named backup and one clock will do.
Say you run a 15-person kitchen and bathroom fitting firm in Leeds. Kitchens go to you, bathrooms to your estimator, Sam, and repairs and small jobs to the office manager. Anything the software can't place also goes to the office manager, so "unsure" has an owner. When Sam is on leave, bathrooms come to you, and that's one setting to change.
The first reply is where the personal touch starts, and it needs no AI. Write it once, in the owner's words, and sign it with their name: "Thanks for the photos. I'm Sam, I price all our bathroom jobs, and I'll call you before 5pm tomorrow." The routing fills in the name and the time. The message is personal because a real person wrote it, and because the promise in it gets kept.
Give that promise a clock. If nobody has replied by the time the message named, the software alerts the owner, and an hour later the backup. A reminder sent to the whole team is a reminder nobody owns.
Taking quote requests on WhatsApp without losing them
For ES Construction, we built quote routing by phone, email or WhatsApp. WhatsApp sits level with the phone number, because for a builder it is often the first contact. Our guide to website design for tradesmen explains why. The risk sits on your side: a WhatsApp enquiry lives on one phone, where nobody else can see it.
The free WhatsApp Business app covers the basics. A greeting message goes out when a customer messages you for the first time, or after 14 days of silence. An away message can go out on a schedule or outside your business hours.
Both need the phone to be online. Since April 2023, up to four more phones can use the same business account, so your office manager can answer from their own.
Label the request before it arrives. WhatsApp's click to chat link can carry a pre-filled first line. Give each service page its own, such as "Hi, I'd like a quote for a bathroom". Customers can edit it, but when they don't, the job type arrives in the first line, where your routing can read it.
To put WhatsApp requests in the same record as the rest, you need Meta's Cloud API. Meta now lets a number stay in the Business app while connected to the Cloud API, and keeps the history in sync. A few app features switch off.
Two rules then apply. You can reply freely for 24 hours after the customer's last message, and after that only with pre-approved templates. And Meta's business messaging policy lets you message people only if they gave you their number and agreed to hear from you.
Meta now offers the AI part too. In June 2026 it made Meta Business Agent available to businesses worldwide. It answers customers, qualifies leads and books appointments, and you decide when a person steps in.
Let an agent like this collect details, and keep it away from prices and start dates. Meta's business messaging policy also requires an automated chat to offer a quick, direct route to a person, such as a handover in the chat or a phone number. If the agent talks to people in the EU, it must say it is an AI; our guide to AI chatbots on business websites covers those rules.
What stays personal: the price, the visit and every promise
Keep a person on anything that sets a price, makes a promise or needs judgement. The list is short, and it's where customers decide:
- The price, and what it includes.
- Start dates and how long the job will take.
- Whether to take the job at all. A quick, kind no, with the name of someone who might help, protects your reputation.
- The site visit or survey, and what you notice while you're there.
- Anything unusual: an urgent leak, a customer let down by their last builder, a job twice your usual size.
- Bad news, such as a price that has gone up or a date that has slipped.
Promises carry more weight than they look. Under section 50 of the Consumer Rights Act 2015, what a trader says or writes to a consumer about a service can become a term of the contract. That covers anything said "by or on behalf of the trader", if the customer relies on it.
On our reading, an automatic reply or an AI agent answering in your firm's name speaks on your behalf. If it says "we can start in two weeks", you may have agreed to start in two weeks.
Software can still help with the price. Jobber, a job management tool for trades, can draft a quote from a new request with AI and flag drafts that come out above your average quote. Treat that as a first draft. Someone who knows the job checks the scope against the photos and sets the figure.
A merged-in first name doesn't make a message personal. A reply that mentions the damp patch in the customer's second photo does, because it shows someone looked.
Follow-ups that stop the moment a customer replies
A quote with no answer deserves a follow-up, and software never forgets to send one. It's bad at knowing when to stop, so write the stopping rules first.
- Check the live conversation just before sending. The reminder was scheduled days ago, and since then the customer may have replied, rung the office or said no. If anything has happened, cancel it.
- Send it from the person who quoted, in words they wrote once. Replies go straight back to them.
- Stop after two. A third reminder about the same quote reads as pressure.
- Never chase a no. Record it and stop.
The law has a view too. A chase that encourages someone to go ahead can count as direct marketing. The ICO's guidance on the soft opt-in says an enquiry about buying from you can count as "negotiations for a sale".
If so, you can email or text that person about your similar services without separate consent. You must have offered a way to opt out when you took their details, and you must offer it again in every message.
That rule covers individuals, including sole traders; messages to companies follow different rules. In the EU, Article 13(2) of the ePrivacy Directive has a similar exception, and each country writes it into its own law. We aren't lawyers, so check your wording with yours.
Last, close every quote with a reason: won, lost on price, lost on timing, no reply, or we declined. Make the reason a required field with fixed choices, not a free-text note. After three months you can count where your quotes are lost, which a folder of notes will never tell you.
Make sure no quote request goes missing
The most expensive failure is a request nobody sees. It's also the hardest to spot, because the form shows its thank-you message once the website hands the email on, not once someone reads it.
Check email delivery first. Some website forms send their notification "from" the customer's own email address. The author of Contact Form 7, a WordPress form plugin, advises against it. Use an address on your own domain in the From field, and put the customer's address in Reply-To.
Mail that claims to come from a domain it wasn't sent from looks like spam to mail providers. Google's sender guidelines tell senders not to impersonate Gmail addresses, and warn that doing so can hurt delivery.
Then add checks that don't depend on email:
- Save every request to a store you own before any email goes out, so a lost email isn't a lost enquiry.
- Send a test request through each channel once a week, the form and WhatsApp alike.
- Alert someone when a weekday passes with no requests. It may be a quiet day, or a broken form, and someone should find out which.
Keep the record in your own hands, too. Customers used to message businesses through Google Business Profile chat. Google removed it on 31 July 2024, and the old records could be downloaded through Google Takeout until 30 August 2024.
A firm whose enquiries lived only there had a month to save them. Whatever channels feed your quote requests, keep the record in an account in your company's name.
When you don't need to automate quote requests
Plenty of firms don't need this built. Skip it in these cases.
- You get a handful of requests a week, and one person answers them all within a few hours. Turn on the WhatsApp away message, keep a list, and stop there.
- The bottleneck is pricing, not intake. If requests already arrive faster than you can visit and price them, faster intake only grows the pile. Say which jobs and areas you don't take, on the site and in the first reply.
- You already pay for job management software. Jobber, for example, has automatic quote follow-ups by email and text. Set up the tool you have first, with the stopping rules above.
A build pays when requests come through several channels that need to land in one record, next to your own diary, price list or job system. It also pays when you want to know where quotes are lost and your current tools can't tell you. If you're deciding what else to automate, start with our checklist of what not to automate with AI.
Start with your last 30 quote requests
Before you change anything, look back. Take your last 30 quote requests, and for each one write down the channel, when it arrived, when a person first replied, who replied, and how it ended.
The gap between arrival and first reply is your "before", and the number you want to see fall. Any request that got no reply is your first fix. If one channel is always slower, route that one first. The endings show whether you lose jobs before the quote or after it, which tells you whether to automate the intake or the follow-up.
Questions
Do we need a CRM to automate quote requests?
Not necessarily. Job management tools for trades already keep requests, quotes and jobs in one place. A small firm can start with a shared table that every channel writes to, as long as each row has an owner and a status. Weighing up a CRM? Our guide to custom CRM vs HubSpot or Pipedrive explains why to set one up before you build.
Is it honest to send an automatic reply signed with a person's name?
Yes, if it's true. A message that a real person wrote, promising that person's call, comes from them, even when software sends it. The line is pretending to be someone in the middle of a conversation. If an AI answers the chat, say so. In the EU, the AI Act has required that since 2 August 2026.
What does it cost to automate quote requests?
We don't publish prices, because every project is quoted. Four things move the cost. The first is how many channels feed the record, and the second is whether it links to your diary, price list or job system. Third, whether WhatsApp runs through the Cloud API, which has its own pricing. Fourth, who writes and checks the messages. A proper quote should list each one.
How we wrote this: drafted with AI, then checked and edited by the people who build our projects. Figures come from our own work or from the linked sources.