What essential fields must appear in a ticketing confirmation email?
Include order number, purchaser name, ticket IDs/QR codes, venue name and full address, event date and times (doors open vs start), contact/support channel, payment/receipt link, and clear next steps for entry or transfers.
When should I send a confirmation and follow-up reminders?
Send the purchase confirmation immediately. Schedule a reminder 24–72 hours before the event and a final reminder the day of with arrival tips. For multi-day events, send daily highlights before each day.
How do I attach or link an ICS calendar invite and what copy should accompany it?
Attach a .ics file and include a short line: "Add to calendar: [Add to Google Calendar link] | [Download .ics]." Explain what the invite includes (start time, venue, directions) and recommend attendees check time zone settings.
How can I include QR codes and provide a plain-text fallback?
Embed the QR image with alt text describing its purpose and provide the ticket ID below the image (e.g., TICKET ID: 12345). For plain-text emails, use clear headings and include the full ticket ID and entry instructions.
How should I word refund, transfer, and rescheduling policies?
Use calm, actionable language: state whether refunds/transfers are allowed, the process to request them (email or manage link), and any deadlines. Keep legal terms concise and link to the full policy for details.
How can I structure confirmations for multi-ticket orders?
List each ticket on its own line with seat/row, ticket type, price, and ticket ID. If guest names can be updated, include a direct manage-attendees link and a short deadline for changes.
What localization and date/time formatting tips help international attendees?
Format dates and times per locale (e.g., DD/MM/YYYY vs MM/DD/YYYY), show time zone abbreviations, and translate key venue/practical instructions. Provide mapping links that respect local navigation apps and parking references.
How do I test subject lines, preheaders, and deliverability?
A/B test subject variants on small audience segments, preview preheaders on major clients, validate SPF/DKIM, and run seed inbox tests for inbox placement. Check spam filters after a small controlled send before full-scale dispatch.
What accessibility considerations should be included in confirmations?
Provide a well-structured plain-text alternative, descriptive alt text for images (including QR codes), readable fonts and sufficient color contrast in HTML, and simple language with clear headings and short paragraphs.
