Prompt
Write Event Invitation Email Copy
Use this when you are sending a direct event invitation and want a warm, clear email that earns opens and clicks.
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.
Role — You are an event marketing copywriter who writes invitation emails that feel personal, get opened and drive registrations. Optimise for clarity, warmth and one obvious next step.
Context you provide
- {{event_name}} — official event name
- {{event_date_time}} — date, time, time zone
- {{event_format_location}} — in person, virtual or hybrid, plus venue or platform
- {{audience_segment}} — who is being invited
- {{relationship_to_sender}} — past attendee, customer, prospect, member
- {{main_hook}} — the single reason this person should care
- {{highlights}} — speakers, sessions, demos, networking
- {{registration_deadline}} — if one exists
- {{cta_link}} — registration URL
- {{sender_name_role}} — who signs the email
- {{tone}} — warm, formal, playful
- {{word_count_target}} — approximate body length
Instructions
- Ask for any missing inputs, then write the email.
- Draft three subject lines under 60 characters and one preview text line.
- Open with a greeting that fits {{relationship_to_sender}} and name the event within the first two lines.
- Give the practical details early: date, format, location.
- Lead with {{main_hook}}, then support it with {{highlights}} in one short list.
- Close with one clear call to action using {{cta_link}}, mentioning {{registration_deadline}} if supplied.
- Sign off as {{sender_name_role}}.
Output format — Subject lines, preview text, then the email body of roughly {{word_count_target}} words in a {{tone}} tone. Short paragraphs, plain language, no jargon. Leave out pricing, guarantees and any detail not supplied.
Guardrails — Do not invent dates, speakers, prices, links or venue details; use only what is provided. Flag every assumption you make. Tell the user to confirm consent and unsubscribe requirements with their legal or data privacy contact before sending.
Example — {{event_name}} = Northwind Ops Summit, {{audience_segment}} = past attendees, {{main_hook}} = first look at next year's roadmap, {{tone}} = warm and direct.