Skip to content
wrangler

Email

Four messages, each rendered from a template you can edit in settings. Every one ships with working copy, so a fresh install sends sensible mail once a From address is set.

Plain text, or branded HTML

The templates you edit are always plain text, and they stay the single source of the words. What changes is the wrapper:

  • Nothing configured under Branding — mail goes out as plain text, exactly as written.
  • Any branding set — mail goes out as multipart HTML: your logo above a card, your accent colour on the button. The plain-text version you wrote is sent alongside as the alternative part, so a client that refuses HTML still shows the words rather than markup.

Plain text has the better deliverability of the two, which is why an admin who has configured nothing is never silently upgraded into HTML mail.

One thing worth knowing when you write a template: a line containing only a URL becomes a button in the HTML version. That is why the built-in copy puts {ticket_url} on its own line — the link is the whole reason the email exists. A URL sitting mid-sentence is left as text.

Email Sent to When
Acknowledgement The requester A ticket is opened. Contains the magic link for guests.
Staff alert — new ticket Staff notification recipients A ticket is opened.
Customer alert — staff replied The requester Staff post a public reply here.
Staff alert — customer replied Staff notification recipients The customer replies.

Swap variables

Available in all four templates:

Variable Value
{ticket_reference} WR-0042
{subject} The ticket subject
{message} The message that triggered the email
{ticket_url} Link to the ticket, including the token for guests
{requester_name} The customer's name, falling back to their email
{site_name} Your site name

{ticket_url} is empty until Ticket page URL is set in settings.

Editing templates

Clearing a textarea restores the built-in default rather than sending a blank message. There is no way to send an empty email by accident.

Mail is plain text. Subjects are not editable in settings; they are in the language file, keyed email_subject_ack, email_subject_staff_new, email_subject_customer_reply and email_subject_staff_reply, and each takes the ticket reference.

Internal notes send nothing

There is no template for an internal note because no email is ever generated for one. This holds in both directions: the note is absent from the customer's thread and absent from the mail queue.

When sending fails

A failure is written to EE's developer log and swallowed. Mail is a side effect of the request — a ticket or a reply that was already saved stays saved, and the customer still sees their confirmation. Check Developer Log if mail is not arriving.

The notification ceiling

Wrangler sends two emails per submission, which would make an abused form an outbound relay. The notification ceiling guards against that: if more tickets are opened site-wide in an hour than the threshold allows, Wrangler keeps accepting tickets but stops sending notification email until the hour rolls off, and logs that it did so.

Nothing is lost when this trips — the tickets are all in the list here. Set it to 0 to disable.