CONVERSION

Confirmation page review

Use when the page after conversion is a dead end and you want it to do more work.

confirmation-and-thank-you-page-review.md

Download .md

You are reviewing the page a user sees immediately after converting. Most of these pages waste the highest attention moment in the journey.

CONVERSION ACTION JUST COMPLETED: {{ACTION_COMPLETED}}
CURRENT CONFIRMATION PAGE CONTENT: {{CURRENT_CONTENT}}
WHAT HAPPENS NEXT OPERATIONALLY: {{NEXT_STEPS_INTERNAL}}
TYPICAL TIME UNTIL NEXT CONTACT: {{TIME_TO_NEXT_CONTACT}}
SECONDARY GOALS THAT WOULD BE USEFUL HERE: {{SECONDARY_GOALS}}

Assess the page against these jobs and mark each Done, Partly Done, or Missing:
1. Confirms unambiguously that the action succeeded
2. Says exactly what happens next and when, in concrete terms
3. Tells the user what to do if nothing arrives
4. Reduces the anxiety that causes duplicate submissions or support tickets
5. Gives the user something useful to do in the waiting period
6. Captures a secondary action that suits someone who has just committed
7. Sets up the next step of the relationship

Then write the recommended page content in full: heading, confirmation line, what happens next as a numbered timeline with real timings, the fallback instruction, and at most one secondary action.

Constraints: do not add more than one secondary action. Do not promise a timing I have not given you - use a placeholder and flag it. No exclamation marks, no em dashes, no closing paragraph restating the confirmation. Do not ask for a review or referral at this point unless the action completed was a purchase that has already been fulfilled.

Fill in before running

Replace each placeholder with your own detail. The more specific you are, the less the model invents.

{{ACTION_COMPLETED}}
{{CURRENT_CONTENT}}
{{NEXT_STEPS_INTERNAL}}
{{TIME_TO_NEXT_CONTACT}}
{{SECONDARY_GOALS}}

Getting a better result

Real timings are the whole point - "shortly" causes the support tickets you are trying to avoid.
Check whether duplicate submissions drop after you add the fallback instruction.
One secondary action only; two turns the page back into a dead end.

Questions about this prompt

When is the confirmation page worth this attention?

When it says thank you and nothing else. This is the highest attention moment in the journey and usually the least worked on. Reach for it when support sees duplicate submissions or where has my order got to questions, since both are symptoms of a page that never said what happens next or when.

What do I need in front of me before running it?

What was just completed, the current page content, what happens next operationally, the typical time until the next contact, and any secondary goals. The real timings are the whole point. Where you cannot supply one, the prompt leaves a flagged placeholder rather than writing shortly, and shortly is what generates the tickets.

What comes back, and which part is worth acting on?

Seven jobs marked Done, Partly Done or Missing, then the recommended page written out in full: heading, confirmation line, a numbered timeline with real timings, the fallback instruction and at most one secondary action. The timeline and the fallback are what reduce support contact, so write those before considering anything else.

What is the mistake that costs me here?

Adding a second secondary action because both looked useful. Two turns the page back into a dead end, which is why only one is allowed. It also declines to ask for a review or a referral unless the purchase has already been fulfilled, and that restraint is worth keeping: nobody reviews what has not arrived.