A Reply-Ready Summary for Website Enquiries: Capture the Customer's Question in One Sentence First
Many small teams answer website enquiries quickly and still miss the point. The reply is polite, accurate and aimed at a different question. A simple habit can reduce this: before writing any reply, the person handling the enquiry writes one sentence that restates what the customer is asking. This article proposes that habit as a small workflow, with a field in your inbox or tracking sheet for the sentence.
Inputs to collect
For each enquiry you need the customer's original message, any attachments, and the page or form they came from. Add one field, "Question in one sentence", filled by the person replying. Add a second short field, "What the customer needs next", with a few options such as information, a price indication, a date, a human call, or nothing yet.
Branching decisions
After writing the sentence, test it. If the sentence needs the word "and" to join two unrelated requests, split the enquiry into two lines and reply to both, in order of what the customer seems to need first. If you cannot write the sentence without guessing, do not guess: your reply becomes a single clarifying question, and the tracking field says "clarify". If the question is outside what your business does, the reply politely says so and, where you honestly know of no suitable alternative, does not invent a recommendation. If the sentence reveals the customer already received the answer in an earlier message, the reply points to that message instead of repeating it.
A hypothetical worked example
Imagine a fictional enquiry from a customer named Lina, to a small printing service: "Hi, I saw your cards, can you do something like that but smaller, and when could it be ready, and do you deliver?" The first draft sentence reads: "Lina wants a smaller version of a card design, a ready date, and delivery information." The word "and" appears twice, so the enquiry is split into three lines: size, timing, delivery. The person replying notices that "something like that" does not say which card. The sentence field now says "clarify which card", and the reply asks one question first: which design she means. Timing and delivery are answered only after that, with a note that dates depend on the final choice. No quote is sent on a guess.
Stop conditions
Stop drafting a full reply when the sentence cannot be written, when two team members write sentences that disagree, or when the enquiry involves a complaint or a sensitive personal situation. In those cases hand it to a named person rather than answering with a template.
Small acceptance checks
Pick five recent enquiries and apply the habit. Check that every one has a sentence under about twenty-five words. Check that at least one enquiry led to a split or a clarifying question, otherwise the sentences may be too loose. Check that a colleague reading only the sentence and the reply can tell whether the reply answers the question. Check that the sentence is stored with the enquiry, not discarded after sending. And check that the field adds under a minute per enquiry; if it takes longer, simplify the options.
This is a proposed team routine, not a technical requirement. Its value is that the restated question becomes visible, so mismatches are caught before the customer sees them.