Prepare customer emails and tickets before go-live

Use this checklist before publishing a new shop, event series, or ticket type.

Before you start

Prepare:

sender name and support email
order confirmation wording
ticket PDF and wallet pass branding
legal text that must appear in customer communication
staff who can resend emails and download documents

Review email templates

Open Comms > Email Templates and select the template to review.

Check Subject, Body, language variants, variables, and attachments. Keep variables such as customer name, order number, event date, and ticket links in place unless you are replacing them with an approved equivalent.

Email template editor in the back office — Email templates control the messages customers receive after booking, payment, or operational actions.

Review ticket and wallet templates

Open Comms > Passbook.

Check:

Area	What to verify
Colors	Foreground and background colors are readable on mobile wallets.
Logo	The logo is current and not cropped.
Icon	The icon is recognizable at small sizes.
Background	The image does not hide ticket details.

Passbook template editor — Review wallet pass colors, logo, icon, and background for readability.

If your account uses editable PDF templates, review the ticket PDF layout as well. Keep QR codes, event name, date, attendee information, and terms readable.

Approve the customer communication

Review the subject, body, variables, attachments, and enabled language variants for each template the launch uses.
Review the ticket PDF and wallet pass layouts, keeping ticket identifiers and QR codes unobstructed.
Confirm which staff roles may edit templates, resend emails, and download customer documents.
Document the approved secure fallback for a customer who cannot receive an email.

Expected result

The approved templates contain the intended wording, translations, variables, attachments, branding, and readable ticket identifiers, and staff know who may edit or resend them.

Troubleshooting

Problem	What to check
Email is missing	Customer email, order History, template status, spam folder, and whether sending failed.
Email summary is incorrect	Selected prices and sub-products in the order, their quantities and presentation settings, and whether the email was generated after the latest order change.
Ticket PDF is missing	Order state, payment state, ticket generation, template setup, and attendee data.
Variable shows as raw text	Restore the approved variable or reinsert it from the template editor.
Wallet pass looks wrong	Passbook colors, logo, icon, background image, and mobile wallet constraints.
Resend email has no ticket	Confirm the ticket exists before resending; resending does not create missing documents.