How do I write a confirmation message after a user completes a website action?
Quick answer
Name the specific action the website confirmed, then describe what—if anything—happens next. Keep completed and pending steps distinct: “Your request was submitted” confirms submission, while “We’ll review it next” describes a future step. Label optional actions as optional, and include only details you can verify. Avoid promising a timeframe or outcome unless the website can support that promise.
The question, the details, the next step.
How do I write a confirmation message after someone completes an action on my website?
Start by identifying the exact action the website has confirmed. Say that plainly, then explain the next step only if there is one the reader needs to know about. For example, if a form has been submitted but not yet reviewed, write “Your request was submitted” rather than “Your request is approved.”
A useful pattern is:
“[Completed action]. [What happens next, or what the user can do now].”
That keeps the confirmation specific without making a separate, unfinished process sound complete.
How can I tell the difference between what’s complete and what’s next?
Treat those as two separate facts. First, ask: what did the website actually confirm? Put that in the completed-action sentence. Then ask: what is the next step, and who is responsible for it? Describe it as upcoming, ongoing, or optional—not as already done.
For example, assuming a website confirms receipt of a support request but a person still needs to review it:
“Your support request was submitted. Our team will review it next.”
The first sentence confirms submission. The second describes a future review. Don’t change the second sentence to “Your issue has been resolved” unless that is actually what the confirmation represents.
What if the next step is something the user can choose to do?
Make the choice clear and separate it from the confirmation. For instance, assuming the site has confirmed that a draft was saved and the user can either keep editing or leave it:
“Your draft was saved. You can keep editing it now or return to it later.”
Use this only if saving is the action the site confirmed and those choices are genuinely available. If the next step is required, say so directly instead: “Your request was submitted. Complete the verification step to continue.” Don’t present a required step as optional, or an optional step as necessary.
Can you give me a reusable template that covers both situations?
Use this copyable template, filling in only what is known:
“[Name the action that was completed]. [State the next step and who takes it, if applicable]. [Offer an optional action, if applicable].”
For example, assuming the site has confirmed that a draft was saved and the user can view it:
“Your draft was saved. You can view it now or return to it later.”
If there is no useful next step, don’t invent one just to fill the space. A short “Your changes were saved” may be enough. Before publishing, check that each sentence matches the actual state of the action and process.
A practical checklist
Name the exact action the site has confirmed.
Describe the current state, not a hoped-for result.
Label future steps as future, and name who takes them when known.
Make required and optional actions distinct.
Include only next steps and details the website can support.
A few more useful answers
Should a confirmation message say “Thank you”?
It can, but gratitude should not replace the confirmation. State what happened first, then add a brief thank-you if it suits the interaction.
What if I don’t know when the next step will happen?
Say what the next step is without promising a timeframe. Avoid phrases such as “shortly” or “within a day” unless that timing is established.
How short should the message be?
Keep it as short as the situation allows: one sentence for a simple completed action, and a second sentence when the user needs to know what happens next.