Six 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.
| Sent to | When | |
|---|---|---|
| Acknowledgement | The requester | A ticket is opened. Contains their magic link. |
| 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 | The assignee, or the staff recipients if nobody is assigned | The customer replies. Set Customer replies alert to All staff recipients to copy everyone instead. |
| Staff alert — assigned to you | The new assignee | Someone else assigns them a ticket. |
| Ticket links reminder | The address that asked | The "lost your link?" form is used and the address has tickets. |
Swap variables
Available in the ticket templates:
| Variable | Value |
|---|---|
{ticket_reference} |
WR-0042 |
{subject} |
The ticket subject |
{message} |
The message that triggered the email |
{ticket_url} |
Link to the ticket, for whoever is reading the email |
{ticket_cp_url} |
Link to the ticket here in the control panel |
{requester_name} |
The customer's name, falling back to their email |
{site_name} |
Your site name |
{custom_fields} |
The custom field answers, one Label: value per line |
{assigned_by} |
Who assigned the ticket (assignment alert only) |
The links reminder has its own two: {ticket_links} (every ticket's reference, subject, status
and link) and {site_name}.
With email replies on, the two customer emails carry a per-ticket Reply-To and open with a "Reply above this line" marker.
{ticket_url} points wherever that email's reader can actually open the ticket:
- In the two customer templates, it is the front-end ticket page, carrying the guest's
requester's magic-link token.
{ticket_url}is empty here until Ticket page URL is set in settings. - In the two staff templates, it is the control panel. Staff work tickets here, and the front-end page would turn them away — it authorizes a member against the ticket's owner, and the owner is the customer.
{ticket_cp_url} is always the control panel link, if you want it somewhere explicitly.
Every requester gets a token — members as well as guests. A member's ticket is also reachable by simply being signed in, but the link in an email is very often opened somewhere they are not: a phone, a second browser, a private window, a session that expired last week. Without a token on the link, all of those tell the person who filed the ticket that it does not exist.
The token is the same every time, so the link in the acknowledgement and the link in every later "we replied" email open the same page. Nothing expires and there is nothing for the customer to keep track of beyond the most recent email.
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,
email_subject_staff_reply and email_subject_staff_assigned, and each takes the ticket
reference. The links reminder's is email_subject_recover.
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.
Staff alerts with no recipients configured are logged too, as is any error while building a message — none of these ever stop the ticket or reply being saved.
Staff alerts do not set the customer as Reply-To. Hitting Reply on one goes back to your From address, not the customer: answers belong in the control panel, where they stay on the ticket and reach the customer with their link.
A message can also be sent successfully and still never be seen: the receiving server accepts it and files it as junk. Nothing on this side of the send can detect that. The usual cause is a From address on a different domain from the site — use an address on the site's own domain, or send through SMTP (EE's Settings → Outgoing Email) authorized for that address.
Dashboard widget
Wrangler adds a Support tickets widget to the control panel home page. It lists the tickets waiting on a staff reply, oldest wait first, with counts of those and of new tickets.
Above the list it flags any setting that will stop notification mail working:
- no staff notification recipients, or one that is not a valid address
- no valid From address
- a From address on a different domain from the site (likely to land in junk)
- the notification ceiling tripped in the last hour
The widget is registered when Wrangler is installed or updated. It appears on the default dashboard automatically; on a customised dashboard layout, enable it under Edit Layout. Dashboard widgets need ExpressionEngine Pro's dashboard; on a site without it the CP home page shows EE's fixed layout and no add-on widgets.
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.