The contact form works, the enquiry has been sent, the customer is waiting. What happens next decides whether that enquiry turns into a job – and in many small businesses this is exactly the part nobody has agreed on. An audit of 2,241 companies shows how wide the gap is: 23 per cent did not answer an incoming enquiry at all, 24 per cent took longer than a day, and the average response time was 42 hours (Harvard Business Review 2011). Yet response time is not a side issue; it is the lever with the strongest effect. Firms that made contact within an hour were almost seven times as likely to reach a qualified conversation as those that reacted just one hour later (Harvard Business Review 2011). This article is neither about building the form nor about missing traffic. It is about the operational routine that follows: who is responsible, within what deadline the reply goes out, what a confirmation should contain, when to follow up, and how open cases stay visible without notes piling up on the counter.
The blind spot between form and job
Between the click on the send button and the signed job lies a stretch that is visible on no website. It consists of a mailbox, a person and a decision about when that person replies. This is exactly where businesses lose work they had essentially already won. In the audit of 2,241 companies mentioned above, 37 per cent replied within an hour, another 16 per cent within a day, 24 per cent took longer than 24 hours and 23 per cent did not reply at all (Harvard Business Review 2011). When almost a quarter of all enquiries go unanswered, that is not a motivation problem but an organisational one: nobody has agreed who takes care of it.
Seen from the customer side, the picture is the same in mirror image. In a 2016 survey by the German digital association Bitkom, roughly half of consumers had already had poor experiences with the customer service of companies. Among those affected, 44 per cent reached no one or received no reply, 55 per cent missed having a fixed contact person, and 15 per cent reported that the answer came very late (Bitkom 2016). For a small business there is good news in that: the benchmark is low. Replying reliably within one working day and giving a name already sets you apart – without any extra advertising budget. If the enquiries do not arrive in the first place, the cause lies elsewhere; the most common reasons are covered in the article on visitors but no enquiries.
The scale behind this is considerable. 99.3 per cent of all companies in Germany are small and medium-sized enterprises (Statistisches Bundesamt), and in the skilled trades alone around 6 million people work in roughly one million businesses as of 2025 (ZDH). These businesses rarely have a sales department sorting incoming enquiries. The enquiry lands in the same mailbox as invoices, supplier post and advertising – and competes with a building site that feels more urgent right now. The result is not negligence but a missing rule. How enquiries on a tradesperson website arise in the first place is one half of the work; what happens to them afterwards is the other.
Who owns the enquiry before the first one arrives
The first decision is the simplest and the one most often skipped: incoming enquiries need a name, not an address. A shared mailbox such as info@ or contact@ is technically convenient but organisationally a grey area – everyone can look inside, so no one feels responsible. Decide who opens the mailbox on working days, morning and afternoon, who steps in when that person is away, and who gets pulled in for larger enquiries. Three written lines are enough, but they have to be written down and known in the team. Who holds which access and permissions is worth sorting out once anyway; the article on maintaining a website as a team describes that for the website itself.
A mailbox with a name instead of an address into the void
The deadline: how fast the reply goes out
A response rule only works if it contains a number. “Promptly” is not a deadline. The evidence here is unusually clear: businesses that made contact within an hour were almost seven times as likely to have a qualified conversation with the decision maker as those that reacted just one hour later – and more than 60 times as likely as those who waited 24 hours or longer (Harvard Business Review 2011). For a trades or service business the one-hour mark is rarely realistic, because the work happens on site and not at a desk. What is realistic is a two-stage promise: an automatic confirmation in the minute the form is sent, and a personal reply by the end of the next working day. That deadline then also appears visibly on the contact page – as a promise the business can keep.
A name, not an address
One person owns incoming enquiries, not a mailbox. The name is written down and known across the team.
A deadline in working days
Instead of “as soon as possible”, a number: a reply by the end of the next working day, stated on the contact page.
A confirmation with substance
The confirmation mirrors the submitted details, names the responsible person and the next step instead of a platitude.
Cover with real access
A second person reads along and can take over. Holidays and sick days then barely change the routine.
A visible status
Every case carries a state: received, answered, quote out, won or declined. One place, one list.
Two follow-up dates
A short nudge after three and after ten working days. After that the case is closed deliberately rather than forgotten.
The confirmation mail is the most underrated piece of text on a website. In most cases it reads roughly: “Thank you for your message, we will get back to you as soon as possible.” That sentence serves no purpose – it names neither a person nor a deadline nor a next step. A usable confirmation repeats the details that arrived, names the person who will reply, states a deadline in working days and explains what the customer can contribute in the meantime, such as sending photos or adding something by phone. How the form itself is set up and evaluated for this is covered in the article on the contact form and its evaluation.
Scroll table sideways
| Aspect | Standard sentence | Confirmation that carries weight |
|---|---|---|
| Sender | Info address without a name | Responsible person with a direct line |
| Timing | “as soon as possible” | “by the end of the next working day” |
| Content | Only thanks for the message | Details from the form mirrored back |
| Next step | Left open | Named: callback, site visit or quote |
| Waiting period | Customer waits with no task | Note on what the customer can still add |
| Impression | Reads as automated | Reads like a business with a routine |
Templates for the three most common enquiry types
Anyone moving daily between site and office writes every reply from scratch – and needs time for it that is gone by the evening. Templates solve this, as long as they are not mistaken for finished mail merges. A good template is a frame with gaps: it carries the structure, the questions to ask back and the next step, while the responsible person fills in the concrete details in two minutes. In most businesses, three templates cover the majority of what comes in.
- The price question. “Roughly what does that cost?” is not answered with “it depends”. The template states a range together with the assumptions behind it, explains in one sentence what drives the price, and offers the next step: a site visit, photos or a short phone call. Businesses that are open about showing prices on the website anyway get fewer follow-up questions here.
- The appointment request. Here availability matters, not consultation. The template offers two concrete time slots, asks for the address and the best way to reach the customer, and states what will be brought along. A business with online appointment booking can replace the template with a booking link and skip the coordination round entirely.
- The fault or emergency. Here the response time is the service. The template confirms in one sentence that the report has arrived, names the next point of contact and – more importantly – the phone number for urgent cases. Email is the wrong medium for a burst pipe; the template says so openly.
Part of the back-and-forth can be avoided before the reply is even written. Every enquiry that arrives without a location, a time frame or a scope creates an extra round, and every round costs days. The form should therefore ask for exactly the fields needed for a first solid answer – and no more. Analyses by the Baymard Institute show an average of 11.3 fields in checkout forms in 2024, although most flows would need only eight (Baymard Institute); for enquiry forms the same logic applies on a smaller scale. If the price question is the most common trigger, an upstream price estimator that pre-qualifies enquiries helps more than another mandatory field.
Following up after three and ten days
The second gap sits behind the quote. A quote goes out, the customer does not respond, and the case disappears. In many businesses the story ends here – not out of indifference, but because nobody set a date for it. Two fixed follow-up dates are enough: one after three working days, one after ten. The first clarifies whether the quote arrived and is understood. The second is the final reminder, combined with a clear note that the case will be closed afterwards. Both are short messages, not sales calls. How strongly the time gap works is already visible in the comparison between one hour and 24 hours of waiting for the first reply: a factor of 60 in the likelihood of a qualified conversation (Harvard Business Review 2011). Follow-ups run on the same mechanism, just over longer intervals.
- Put the responsible person and their stand-in for incoming enquiries in writing.
- Send the form mail to at least two recipients, one of them read by the stand-in.
- Write a confirmation with a name, a deadline and a next step instead of a standard sentence.
- State the response deadline on the contact page and keep to it in daily work.
- Prepare templates for the price question, the appointment request and the fault report.
- Set both follow-up dates, after three and ten working days, when the quote goes out.
- Actively decline enquiries outside your service area, with a recommendation where possible.
- Keep open cases in one place and review the list once a week.
- Check delivery of the form mails once a quarter with a test enquiry.
Two calendar entries replace gut feeling
Holidays, sickness and enquiries outside your area
A routine that only works when everyone is present is not a routine. Holidays, sick days and trade fair days are foreseeable, so they belong in the rule. In practice that means: the form mail also goes to a mailbox the stand-in reads; the out-of-office note names a reachable person with a direct line instead of a general address; and the deadline on the contact page is adjusted for that period if it cannot be kept. On top of that comes a technical point that is easily missed: form mails end up in spam folders more often than ordinary correspondence, because they are sent automatically. How the right records for your own domain prevent that is described in the article on business email deliverability.
The second edge case is the enquiry that does not fit: too far away, the wrong trade, too small in scope – or the order book is simply full. The most common reaction is silence, and it is the worst one. A decline costs two sentences and leaves behind a business that keeps its word. It can also carry a recommendation, and recommendations come back. If capacity is a permanent theme, it belongs on the website rather than in every individual decline: how to manage a full order book through your website is a chapter of its own. And if the same question arrives daily, it belongs on an FAQ page with real customer questions rather than in thirty separate replies.
An enquiry without a responsible person is not an enquiry. It is a message waiting for a coincidence.
From enquiry to quote, without scraps of paper
The handover from enquiry to quote is where information gets lost. What was discussed on the phone is not in the mail; what is in the mail is unknown to the colleague on site. A simple counter-measure: every enquiry becomes a case with five entries – date, name, the request in one sentence, responsible person, current state. That can be a spreadsheet, a list in the calendar or a folder in the mailbox; what matters is that there is exactly one place and not three. Phone calls belong in the same list, otherwise half the picture is missing – how to attribute phone calls coming from the website is covered in the corresponding article.
- Received – the enquiry has arrived, the confirmation has gone out.
- In clarification – questions are open, a site visit or photos are pending.
- Quote out – the send date is noted, both follow-up dates are set.
- Won – the job is confirmed, handed over to the people doing the work.
- Declined – the decline has been written, the reason noted in one keyword.
One look at this list per week replaces every reminder routine in your head. Five minutes on a Friday afternoon are enough to see which cases are older than three days with no response. The same list answers a question that otherwise stays open: how many enquiries arrive per month and how many of them become jobs. For existing customers a separate route is worth having, so that service requests do not land in the same pot as new enquiries – what that looks like is described in the article on service forms for existing customers.
How XICflow secures the path after the send button
The hurdle in small businesses is rarely the insight but the effort of setting things up. XICflow therefore builds the enquiry form so that the routine behind it is already accounted for: an immediate, individually worded confirmation instead of a standard sentence, with a name, a deadline and the next step; forwarding to several recipients so an enquiry does not hang on a single mailbox; a copy to the mailbox of whoever is covering during holidays and sick days; and required fields that ask for exactly the details without which no sensible answer is possible. On top of that comes a delivery check for the sending domain so form mails do not end up in spam folders.
None of this replaces the internal agreement about who handles which enquiry – that decision stays with the business, and it takes ten minutes to make. What it does remove are the technical stumbling blocks. Which building blocks are available for this is listed in the XICflow service overview; how a project runs from briefing to launch is shown on the page how XICflow works; and what finished sites including their enquiry path look like can be seen in the example sites in the demo gallery.
Sources and Studies