“Thank you” tells a visitor that the website changed, but it does not explain what the business received. After a ChatGPT ad enquiry, the customer needs to distinguish a submitted request from an accepted order, a reserved appointment or a promise to provide a particular service.
Write the confirmation from the state your system can establish. If a request has reached the enquiry system, say it was received. If a separate review still determines price or availability, preserve that distinction. The page is a receipt for an action, and its wording should remain true when a colleague, customer or support agent reads it later.
Define the event that earns a confirmation
First identify the system evidence behind the success message. A click on the submit button is not enough. The front end might have sent a request while the receiving service failed, or the record might exist even though an email notification is delayed.
Agree with the implementation owner which response permits the page to show receipt. The editorial decision is simple: do not describe a later business event merely because the earlier technical step succeeded. A consultation request awaiting staff review is not a calendar reservation.
This boundary also helps when an enquiry remains in an uncertain state. The slow-submission guide covers waiting and recovery before receipt is established. Keep that uncertainty out of the completed-state wording instead of combining “submitted successfully” with “we are not sure whether we received this.”
Draft a receipt for one concrete service
Imagine a hypothetical ChatGPT ad offering an office-cleaning assessment. The visitor provides the premises location, approximate floor area and preferred start month. The confirmation could identify the completed action as an assessment enquiry and repeat a short, non-sensitive summary of those choices.
It should then explain what the quote team does next: review whether the premises fit the service and arrange any further assessment required before producing a proposal. The preferred start month remains a request. The confirmation must not turn it into an agreed commencement date.
A useful internal writing test is to replace the headline with the most concrete truthful sentence available. “Your office-cleaning assessment request has been received” provides more information than “You’re all set.” The latter could be read as a finished booking, particularly after an ad that emphasised speed.
Put the unresolved decision into ordinary language
Explain what has not yet been decided when it materially affects the customer. For the cleaning example, scope, price and start date may still need agreement. A short sentence close to the next-step explanation is easier to understand than a legalistic block at the bottom.
Do not list every theoretical contingency. Select the decisions the customer might reasonably assume were completed. If the form requested a quote, the absence of a final price may be obvious; if the button said “Reserve an assessment,” the difference between a request and a reservation needs urgent correction throughout the journey.
The confirmation cannot repair misleading earlier copy by itself. Read the ChatGPT ad, destination headline, form label and receipt in sequence. They should describe a coherent progression. The process-visibility guide helps explain the wider service stages without crowding the receipt.
A received enquiry is its own state
- Received
The office-cleaning enquiry has been recorded.
Checkpoint - Next action
The quote team reviews premises and requested start date.
- Not confirmed
Price and start date are established in an offer.
Reconsider
Make the next action accountable
Name the team or role responsible for the next step and identify the channel they will use. “We will be in touch” leaves the customer watching every inbox and missed call. If the customer chose email, reflect that choice using a suitably masked address when needed.
A response-time statement should come from an operational commitment that staff can maintain. Explain the applicable business days or opening hours if they alter the expectation. Do not invent a short turnaround because it looks reassuring beside a successful submission.
Include a contact route for corrections, with a reference if the system provides one. Do not manufacture a reference number merely for the design. Where the customer can amend details directly, the amendment path should identify the existing enquiry so it does not quietly create another record.
Let the customer retain the useful facts
GOV.UK’s confirmation-page pattern identifies receipt information, next steps and a way to retain a record as useful elements. Adapt those principles to the actual business service rather than copying government wording or assuming all its interface conventions fit.
Decide which details belong on the page, in a confirmation email and in any downloadable receipt. They should agree about the status and next action. An email subject saying “Booking confirmed” would undermine a page that correctly says “Request received.”
Separate receipt of the enquiry from delivery of its confirmation email. A customer who sees a valid receipt but cannot find the email should not be told to submit the whole form again. Provide the supported way to retrieve the receipt or contact the team using the existing reference. Only describe an email as sent when that state has been established; successful receipt of the form alone does not establish delivery to the customer’s inbox.
Consider a return visit to the confirmation address. A customer may bookmark it, refresh the page or reopen it on a shared device. Ask the technical owner to define safe behaviour for those cases. The page must not resubmit the enquiry, disclose private details through a public link or claim a new request has just arrived.
Verify the finished state with a real workflow
Use an authorised test submission and follow the record through the receiving system. Compare the submitted service, customer preferences, visible confirmation and staff notification. Inspect the wording on mobile and after switching between the supported languages.
Then let someone who did not write the page answer three questions: what has happened, what happens next and what should they do if something is wrong? If the answers differ from the business process, revise the receipt before adding promotional links.
Related offers can wait until these answers are secure. The confirmation has done its job when the customer can close the page with an accurate understanding of their request and a practical way to continue it.
Sources and scope
Design the receipt after a ChatGPT ad enquiry so the customer understands submission status, a retainable record and the next step without mistaking receipt for a confirmed sale or appointment.
Working methods and examples are editorial suggestions. Check current platform requirements and available features before implementation.