Email Notifications
Support Tickets sends five distinct transactional emails across the ticket lifecycle. All five are sent automatically while Enable Support Tickets is set to Yes (the default), with no additional configuration beyond the Admin Notification Email and Email Sender settings under System Settings.
The five notification events
| Event | Trigger | Recipient | Default template |
|---|---|---|---|
| New ticket - customer | Customer submits a new ticket | The customer who opened the ticket | ocmlabs_ |
| New ticket - admin | Customer submits a new ticket | Admin Notification Email from config | ocmlabs_ |
| New comment - customer | Admin posts a reply | The ticket owner | ocmlabs_ |
| New comment - admin | Customer posts a reply | Admin Notification Email from config | ocmlabs_ |
| Ticket resolved - customer | Customer clicks Mark as Resolved | The ticket owner | ocmlabs_ |
Admin-side notifications go to the single address set in Stores > Configuration > OrangeCollar > Support Tickets > General > Admin Notification Email. If you want multiple staff to receive the same alerts, use a distribution list or alias rather than trying to configure multiple addresses. Leave the field empty to turn off admin emails.
Admin status changes, from the ticket page or the grid’s bulk actions, do not send any email. Setting a ticket to Resolved in the admin does not send the resolved email.
Available template variables
Every template receives these variables:
| Variable | Description |
|---|---|
ticket_ | Numeric ticket ID |
ticket_ | The ticket title |
ticket_ | Current status code (open, pending, in_, or resolved) |
ticket_ | Priority code (low, medium, high, or urgent) |
view_ | Customer-facing URL to the ticket view page |
account_ | URL of the customer’s Support Tickets list |
Some templates receive extra variables:
| Template | Extra variables |
|---|---|
| New ticket - admin | customer_, customer_, admin_ |
| New comment - customer | comment_ (the reply that triggered the email) |
| New comment - admin | customer_, comment_, admin_ |
admin_url is the admin ticket edit URL. The new ticket - customer and ticket resolved templates use only the common variables.
Customizing a template
Each of the five templates can be replaced with a custom Magento email template from the admin:
- Go to Marketing > Communications > Email Templates > Add New Template.
- In the Template dropdown, pick the default Support Tickets template you want to override (for example, “Support Ticket - New Ticket (Customer)”).
- Click Load Template to populate the editor with the shipped version.
- Edit subject and body, then save under a recognizable name.
- Return to Stores > Configuration > OrangeCollar > Support Tickets > Email Templates and select your custom template from the dropdown for that event.
Finally, flush the config cache:
$ bin/magento cache:flush config Because the shipped templates use standard Magento variable syntax ({{var ticket_subject}}, etc.), your custom template can use any of the variables listed above for that template.
Sender identity
The Email Sender setting controls which Magento email identity (General Contact, Sales Representative, Customer Support, etc.) is used as the From address for every outgoing notification. Configure identities under Stores > Configuration > General > Store Email Addresses and then pick one in the Support Tickets config.
Troubleshooting delivery
No admin emails arriving. Confirm Admin Notification Email is set. A blank value means admin notifications have no recipient and are silently skipped. Also confirm Enable Support Tickets is set to Yes; when it is No, no ticket emails are sent at all.
- Emails sending to the wrong address. Sender identity is per store view. On multi-store installations, override the sender per store view under the scope switcher on the configuration page.
- Template changes not appearing. Flush the config cache (
bin/magento cache:flush config) after changing the template selection. - Magento email queue. Support Tickets uses the standard Magento transport, so if your Magento instance queues email (via
system/smtp/or a third-party module), ticket emails are queued alongside everything else.