A service enquiry confirmation should answer the question a customer has immediately after submitting a form: did my request arrive, and what happens now? Use a short message that reflects the actual state of the submission and the process your team can deliver. Write the confirmation alongside the enquiry form rather than treating it as an afterthought.
Confirm only what has happened
Distinguish a request being received from an appointment being booked or work being accepted. If the form sends an enquiry for review, say that. A cheerful “You're booked!” message can create an expectation the team has not agreed to.
Ask the person responsible for the form to explain the success and failure states. The wording should match the state shown to the customer. A technical problem needs a useful error message and recovery route, rather than a confirmation that implies delivery succeeded.
Name the next action and its owner
Explain whether a team member will review the request, ask for more details or send a proposed appointment time. Customers should know whether they need to do anything immediately. Avoid a generic “We'll be in touch” when a more specific sentence is available.
Keep promises grounded in the actual workflow. If the team has a verified reply window, include it with the relevant working-hours context. Use the service page response times guide to check that the form, confirmation and contact page describe the same expectation.
Use an original sample as a starting point
The following wording is fictional and illustrates the structure. It is not a statement of Lets Rank Now's own response commitment.
Thanks — your enquiry has been received. Our service team will review the details and contact you using the email address you supplied. This message confirms receipt of your request; appointment details will be agreed separately. Keep the reference shown below if you need to ask about this enquiry.
Use the reference sentence only if the system actually provides a usable reference. Likewise, mention an email receipt only if the form sends one and the team has checked that behavior. Remove any statement that the actual form cannot support.
Repeat useful details without exposing too much
A short summary can help the customer catch a mistake, such as an incorrect service selection. Choose the minimum useful information for the confirmation screen. Consider where the screen may be viewed and avoid unnecessarily repeating private details.
For an email receipt, keep the subject and opening clear enough that the customer can recognize the enquiry later. Give a practical route for correcting a detail, using a contact method the team monitors. Do not ask people to send passwords or unnecessary account information in a reply.
Explain how to correct a missing detail
Decide what the customer should do if they entered the wrong email address, forgot an attachment or chose the wrong service. A monitored contact route and an enquiry reference may be more useful than telling them to submit the whole form again.
If a correction requires another form, explain which details to provide and how the team will connect it with the original request. Keep the process consistent with any file upload instructions already on the site.
Test the message through the whole journey
Ask the site owner to run a clearly identified test enquiry using permitted test details. Compare what appears on screen, what arrives in the team's inbox and what the customer receives. Check both a successful submission and the form's supported error recovery process.
- Does the confirmation distinguish receipt from acceptance?
- Is the next action assigned to the customer or the team?
- Are any time commitments consistent with current operations?
- Do the reference and correction route work?
- Can the customer read the message easily on a narrow screen?
These are review prompts, not a claim that a test has been performed on your form. Record what was checked and who owns any unresolved issue.
Review the wording when the process changes
Update confirmation text when the monitored inbox, working hours, quoting process or booking system changes. Use the same review record as the service page review process so the message does not drift away from the main page.
A useful confirmation leaves the customer with a clear state, one practical expectation and a route for help. Keep it short enough to read at the point of submission, while preserving the details that determine what they should do next.