“You’re all set” is an awkward ending to a quote-request form. The customer may believe a date has been reserved, a price accepted or a job booked. The business may only have received an enquiry that nobody has reviewed yet.
A good confirmation page closes the action the customer actually completed. It says what was received, what remains undecided and how the next step will happen. That gives the buyer something useful to rely on without making a promise the sales or operations team cannot keep.
The examples here use a fictional print shop and invented references. They illustrate content choices, not a real supplier’s response times or the legal status of a quotation.
Give receipt a precise meaning
The GOV.UK confirmation-page guidance calls for a reference when available, next steps and timing, contact details and information people may need afterward. Applied to a commercial enquiry, those elements help distinguish a completed submission from the later decision about the work.
Start with an exact headline: “We’ve received your quote request.” It tells the customer that the form reached the business. It does not imply that the requested date is available or that the work has been priced.
Then identify the request in terms the customer recognizes. A reference number is useful, but a brief description helps too: “Request Q-218: printed event brochures.” Show the main contact address in an appropriately protected view so the person can spot a typing mistake before waiting for a reply that will never reach them.
If the system has only received some of the required information, avoid an unqualified completion claim. Explain what is missing and how to provide it. The customer should not have to infer that “Thanks” actually means the request is sitting in a queue that cannot progress.
Separate three useful confirmation states
A quote journey often needs more than one version of its final page. The following examples are proposed states for the fictional print shop.
Request received. The form and the required details arrived successfully. The page says the team will review the specification and respond through the agreed channel. It also states that the requested delivery date has not yet been confirmed.
More information needed. The team cannot prepare a useful quote until the customer supplies a missing detail, such as the finished page count. The page names that detail, explains how to add it to the existing request and retains the reference.
Quotation ready. The business has prepared a price and scope for the customer to review. The page points to the actual quotation and explains the genuine next step for accepting, asking a question or requesting a change.
These labels should match operational states. A page cannot claim that a quotation is ready merely because a generic price calculator finished. If the estimate still depends on a file review or a production decision, say which information remains provisional according to the business’s approved process.
The distinction also helps with repeat visits. A saved request page can move from received to more information needed or quotation ready without making the customer reconstruct the conversation from several unrelated emails.
Write a response expectation the team can meet
Suppose the fictional shop has an established target of replying within two business days. Its page might say:
We’ve received request Q-218 for your event brochures. Our print team will review the specification and email you within two business days. Your requested delivery date is not confirmed yet. If you need to change the quantity or upload a revised specification, update this request using the link below.
The response target is part of the fictional example. A real business should use its actual staffing and workflow to choose the promise. “Soon” is vague, but an unsupported deadline is worse because it turns ordinary queue time into an apparent service failure.
Specify the response channel. A customer expecting a call may not watch for an email. If the team needs a phone conversation, explain how it will arrange one. Avoid suggesting that someone should remain on the page until a salesperson becomes available unless that is genuinely how the service works.
Seasonal or weekend staffing changes may affect the expectation. Keep the wording tied to the process the business operates, and give the customer a route to ask about a time-sensitive requirement. Do not make an urgent-request button look like a confirmed expedited service.
Make correction easier than resubmission
A customer who notices the wrong quantity should be able to correct the existing enquiry. Asking them to submit another form creates two versions that the team may treat as separate opportunities.
Provide an edit route where the system supports one. Otherwise, explain how to contact the team with the request reference and the change. Tell the customer whether the update will replace earlier details or be added for review, according to the actual workflow.
The same applies to attachments. If a revised specification arrives after submission, it should be clear which file the team will use. A filename alone may not be enough when two documents have the same name. The confirmation view can help by showing the latest accepted version and when it was received, provided those facts are actually recorded.
Keep receipt and review separate. “File received” confirms transfer; it does not promise that the document is complete, readable for production or approved. That additional decision belongs to the relevant review step.
Keep the promise consistent before submission
The form’s final button, confirmation headline and follow-up message should describe the same action. If the button says “Book now” but the page later says a team will decide whether the job is possible, the ambiguity began before the confirmation screen.
GOV.UK’s check-answers pattern recommends making the final action clear and letting people review and change their information before submitting it. For a quote request, that means a buyer should see the specification they are sending and understand that the next step is a quotation process.
Use wording such as “Send quote request” when that accurately describes the action. If payment, reservation or acceptance happens elsewhere, name that later step where it becomes relevant. Do not make the confirmation page repair an earlier misleading call to action through a small qualification at the bottom.
A short review of the request can also prevent avoidable follow-up. Display the quantity, requested timing and other decisive details in a compact form. Give changes clear destinations so the buyer can correct a field without restarting the entire enquiry.
Leave a useful record
A confirmation email should preserve the same reference and status as the page. It can summarize the request and provide a route back to the current view. If the system cannot send email, do not display a claim that a message has been sent. Offer whatever record the service can reliably provide.
Think about someone returning after the response target has passed. The page should still identify the request and explain how to check its progress. A generic expired-link screen with a fresh enquiry form is a poor substitute for a support route tied to the existing reference.
When reviewing performance, separate completed enquiries from quotations issued and jobs accepted. The form-optimization guide helps examine the submission experience, but a clean confirmation screen cannot establish whether the enquiry was commercially suitable or whether the team followed up.
Read the final page as if you were the buyer planning around it. You should be able to answer: did my request arrive, what remains to be decided, when will I hear back and how can I correct it? If the page answers those questions precisely, it has completed its part of the sale.