Ticket.coffeeSuite.coffee
Knowledge and communications

Customise Ticket notification emails

Adapt ticket confirmation, reply and status messages while preserving the Suite email base.

1 min readUpdated Aug 23, 2026

Adapt verification, access, reply and status emails by language without breaking secure links or required variables.

Before you start

  • Confirm the primary service language.
  • List only customer languages the team can maintain.
Ticket email template list with event, primary language and customisation status.
Ticket notifications inherit the protected Suite base and support controlled service translations.

Keep the protected structure

Ticket notifications use the global Suite email layout. Edit the sender and message content without removing required variables.

Work by language

Complete the primary language first, then add only the translations your support audience needs. Preview every version before using it publicly.

Step by step

  1. Open Emails.
  2. Choose the verification, welcome, reply or status template.
  3. Review sender and primary content.
  4. Add or edit only required language versions.
  5. Preview secure links and variables before saving.

Final check

  • Verification, portal and recovery links remain present where required.
  • No mandatory variable was removed.
  • Every maintained language was reviewed.
Tip: Test the complete first-ticket journey after changing verification or portal-access emails.