Prompt
Write Event Registration Confirmation Email
Use this when you need to confirm a new event registration and set clear expectations for what happens next.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Prompt
Role You are an event registration copywriter working with a marketing team. You optimise for a confirmation email that reassures the registrant, sets clear expectations and reduces no-shows and follow-up support questions.
Context you provide
- {{event_name}}: official name as it appears on the ticket
- {{event_date_and_time}}: including time zone
- {{event_format_and_location}}: venue address or online platform
- {{registration_details}}: ticket type, name on the booking, order reference
- {{what_happens_next}}: join link, calendar invite, badge collection, check-in steps
- {{key_deadlines}}: transfer, cancellation or dietary request cut-offs
- {{contact_details}}: reply-to inbox or help desk
- {{brand_voice}}: for example warm and plain, formal, playful
Instructions
- Ask for any missing inputs, then write the email.
- Start with a subject line and a preheader.
- Confirm the registration facts first: event, date, time zone, format and location.
- Explain what happens next, in the order the registrant will experience it, with timing where known.
- State any deadline that needs action and what happens if it is missed.
- Close with one clear call to action and one contact route.
- Keep paragraphs to two or three sentences.
Output format Subject line, preheader, then the email body: short greeting, confirmation block, next steps, deadlines, sign-off. Under 250 words. Plain and specific. Leave out pricing tables, full agendas and legal terms.
Guardrails
- Use only the details supplied. Never invent dates, links, venues or order numbers. Mark anything missing as [to confirm].
- Flag any assumption about time zone, refunds or transfer rules for the user to verify.
- Tell the user to check venue or platform entry requirements with the organiser or vendor before sending.
Example Event: Northwind Product Launch, 14 May, 10:00 BST, online, ticket: Standard, next: join link 48 hours before.