...
| Tags | Description | Notes | Since |
|---|---|---|---|
| {ticket_hash_code} | A hash code for validating ticket replies | Required to be in the subject line to allow for tickets to be replied to by email | |
{ticket.id} | The system-level ticket ID | ||
| {ticket.code} | The ticket number | e.g. "1821914" | |
| {ticket.department_id} | The system-level department ID of the department this ticket belongs to | ||
| {ticket.staff_id} | The system-level staff ID of the staff member assigned to this ticket | May be empty | |
| {ticket.service_id} | The system-level service ID of the service this ticket is in relation to | May be empty | |
| {ticket.client_id} | The system-level client ID of the client this ticket is assigned to | ||
| {ticket.email} | The email address the ticket was emailed in from | Only set when the email address is piped in and unrecognized | |
| {ticket.summary} | A brief ticket summary | ||
| {ticket.priority} | The system-level ticket priority | e.g. "critical", "high", "medium", etc. | |
| {ticket.priority_language} | The language for the translated ticket priority | e.g. "Critical", "High", "Medium", etc. | |
| {ticket.status} | The system-level ticket status | e.g. "open", "awaiting_reply", "closed", etc. | |
| {ticket.status_language} | The language for the translated ticket status | e.g. "Open", "Awaiting Reply", "Closed", etc. | |
| {ticket.date_added} | The UTC datetime stamp of ticket creation | Formatted as "YYYY-MM-DD HH:MM:SS" | |
| {ticket.date_closed} | The UTC datetime stamp the ticket was closed | May be empty. Formatted as "YYYY-MM-DD HH:MM:SS" | |
| {ticket.reply_id} | The system-level reply ID attached to this ticket | ||
| {ticket.reply_staff_id} | The system-level staff ID of the staff member that sent this reply | ||
| {ticket.reply_type} | The system-level type of reply | i.e. "reply", "note", "log". Emails are only sent when the type is "reply" | |
| {ticket.reply_has_attachments} | Whether or not this specific reply has any attachments | v2.3.0 | |
| {ticket.has_attachments} | Whether or not any replies to this ticket have any attachments | v2.3.0 | |
| {ticket.details} | The ticket reply details in plain text | ||
| {ticket.details_html} | The ticket reply details in HTML | ||
| {ticket.reply_date_added} | The UTC datetime stamp of the reply | Formatted as "YYYY-MM-DD HH:MM:SS" | |
| {ticket.company_id} | The system-level company ID this ticket was created under | ||
| {ticket.department_name} | The name of the department this ticket belongs to | ||
| {ticket.department_email} | The email address of the department this ticket belongs to | ||
| {ticket.override_from_email} | Whether or not the email template's from address has been replaced with the department email | i.e. "1" or "0" | v1.6.0 |
| {ticket.reply_by} | The system-level type indicating where the ticket reply came from | i.e. "system", "staff", "client", or "email" |
Ticket Updated
The ticket updated email template alows for the following tags:
| {client.first_name} | The first name of the client that opened this ticket | v2.20.0 | |
| {client.last_name} | The last name of the client that opened this ticket | v2.20.0 | |
| {reply_contact.first_name} | The first name of the last contact | ||
| Tags | Description | Notes | Since |
|---|---|---|---|
| {update_ticket_url} | The URL for a client to visit to reply to this ticket | v2.20.0 | |
| {reply_contact.last_name} | The last name of the last contact to reply to this ticket | v2.20.0 |
Ticket Updated
The ticket updated email template allows for the following tags:
| Tags | Description | Notes | Since |
|---|---|---|---|
| {update_ticket_url} | The URL for a client to visit to reply to this ticket | ||
| {ticket_hash_ticket_hash_code} | A hash code for validating ticket replies | Required to be in the subject line to allow for tickets to be replied to by email | |
{ticket.id} | The system-level ticket ID | ||
| {ticket.code} | The ticket number | e.g. "1821914" | |
| {ticket.department_id} | The system-level department ID of the department this ticket belongs to | ||
| {ticket.staff_id} | The system-level staff ID of the staff member assigned to this ticket | May be empty | |
| {ticket.service_id} | The system-level service ID of the service this ticket is in relation to | May be empty | |
| {ticket.client_id} | The system-level client ID of the client this ticket is assigned to | ||
| {ticket.email} | The email address the ticket was emailed in from | Only set when the email address is piped in and unrecognized | |
| {ticket.summary} | A brief ticket summary | ||
| {ticket.priority} | The system-level ticket priority | e.g. "critical", "high", "medium", etc. | |
| {ticket.priority_language} | The language for the translated ticket priority | e.g. "Critical", "High", "Medium", etc. | |
| {ticket.status} | The system-level ticket status | e.g. "open", "awaiting_reply", "closed", etc. | |
| {ticket.status_language} | The language for the translated ticket status | e.g. "Open", "Awaiting Reply", "Closed", etc. | |
| {ticket.date_added} | The UTC datetime stamp of ticket creation | Formatted as "YYYY-MM-DD HH:MM:SS" | |
| {ticket.date_closed} | The UTC datetime stamp the ticket was closed | May be empty. Formatted as "YYYY-MM-DD HH:MM:SS" | |
| {ticket.reply_id} | The system-level reply ID attached to this ticket | ||
| {ticket.reply_staff_id} | The system-level staff ID of the staff member that sent this reply | ||
| {ticket.reply_type} | The system-level type of reply | i.e. "reply", "note", "log". Emails are only sent when the type is "reply" | |
| {ticket.reply_has_attachments} | Whether or not this specific reply has any attachments | v2.3.0 | |
| {ticket.has_attachments} | Whether or not any replies to this ticket have any attachments | v2.3.0 | |
| {ticket.details} | The ticket reply details in plain text | ||
| {ticket.details_html} | The ticket reply details in HTML | ||
| {ticket.reply_date_added} | The UTC datetime stamp of the reply | Formatted as "YYYY-MM-DD HH:MM:SS" | |
| {ticket.company_id} | The system-level company ID this ticket was created under | ||
| {ticket.department_name} | The name of the department this ticket belongs to | ||
| {ticket.department_email} | The email address of the department this ticket belongs to | ||
| {ticket.override_from_email} | Whether or not the email template's from address has been replaced with the department email | i.e. "1" or "0" | v1.6.0 |
| {ticket.reply_by} | The system-level type indicating where the ticket reply came from | i.e. "system", "staff", "client", or "email" |
Staff Ticket Assigned
| {client.first_name} | The first name of the client that opened this ticket | v2.20.0 | |
| {client.last_name} | The last name of the client that opened this ticket | v2.20.0 |
Staff Ticket Assigned
This email is This email is sent to a staff member when a ticket has been assigned to them. This email template was made available in v2.6.0 of the plugin. The following tags are supported:
...
| Tags | Description | Notes | Since |
|---|---|---|---|
| {ticket_hash_code} | A hash code for validating ticket replies | Required to be in the subject line to allow for tickets to be replied to by email | |
{ticket.id} | The system-level ticket ID | ||
| {ticket.code} | The ticket number | e.g. "1821914" | |
| {ticket.department_id} | The system-level department ID of the department this ticket belongs to | ||
| {ticket.staff_id} | The system-level staff ID of the staff member assigned to this ticket | May be empty | |
| {ticket.service_id} | The system-level service ID of the service this ticket is in relation to | May be empty | |
| {ticket.client_id} | The system-level client ID of the client this ticket is assigned to | ||
| {ticket.email} | The email address the ticket was emailed in from | Only set when the email address is piped in and unrecognized | |
| {ticket.summary} | A brief ticket summary | ||
| {ticket.priority} | The system-level ticket priority | e.g. "critical", "high", "medium", etc. | |
| {ticket.priority_language} | The language for the translated ticket priority | e.g. "Critical", "High", "Medium", etc. | |
| {ticket.status} | The system-level ticket status | e.g. "open", "awaiting_reply", "closed", etc. | |
| {ticket.status_language} | The language for the translated ticket status | e.g. "Open", "Awaiting Reply", "Closed", etc. | |
| {ticket.date_added} | The UTC datetime stamp of ticket creation | Formatted as "YYYY-MM-DD HH:MM:SS" | |
| {ticket.date_closed} | The UTC datetime stamp the ticket was closed | May be empty. Formatted as "YYYY-MM-DD HH:MM:SS" | |
| {ticket.reply_id} | The system-level reply ID attached to this ticket | ||
| {ticket.reply_staff_id} | The system-level staff ID of the staff member that sent this reply | ||
| {ticket.reply_type} | The system-level type of reply | i.e. "reply", "note", "log". Emails are only sent when the type is "reply" | |
| {ticket.reply_has_attachments} | Whether or not this specific reply has any attachments | v2.3.0 | |
| {ticket.has_attachments} | Whether or not any replies to this ticket have any attachments | v2.3.0 | |
| {ticket.details} | The ticket reply details in plain text | ||
| {ticket.details_html} | The ticket reply details in HTML | ||
| {ticket.reply_date_added} | The UTC datetime stamp of the reply | Formatted as "YYYY-MM-DD HH:MM:SS" | |
| {ticket.company_id} | The system-level company ID this ticket was created under | ||
| {ticket.department_name} | The name of the department this ticket belongs to | ||
| {ticket.department_email} | The email address of the department this ticket belongs to | ||
| {ticket.override_from_email} | Whether or not the email template's from address has been replaced with the department email | i.e. "1" or "0" | v1.6.0 |
| {ticket.reply_by} | The system-level type indicating where the ticket reply came from | i.e. "system", "staff", "client", or "email" |
Staff Ticket Updated (Mobile)
The ticket received (mobile) email template allows for the following tags:
| {client.first_name} | The first name of the client that opened this ticket | v2.20.0 | |
| {client.last_name} | The last name of the client that opened this ticket | v2.20.0 | |
| {reply_contact.first_name} | The first name of the last contact to reply to this ticket | v2.20.0 | |
| {reply_contact.last_name} | The last name of the last contact to reply to this ticket | v2.20.0 |
Staff Ticket Updated (Mobile)
The ticket received (mobile) email template allows for the following tags:
| Tags | Description | Notes | Since | ||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| {ticket_hash_code} | A hash code for validating ticket replies | Required to be in the subject line to allow for tickets to be replied to by email | |||||||||||||||||||||||||||||||||||||||
{ticket.id} | The system-level ticket ID | ||||||||||||||||||||||||||||||||||||||||
| {ticket.code} | The ticket number | e.g. "1821914" | |||||||||||||||||||||||||||||||||||||||
| {ticket.department_id} | The system-level department ID of the department this ticket belongs to | ||||||||||||||||||||||||||||||||||||||||
| {ticket.staff_id} | The system-level staff ID of the staff member assigned to this ticket | May be empty | |||||||||||||||||||||||||||||||||||||||
| {ticket.service_id} | The system-level service ID of the service this ticket is in relation to | May be empty | |||||||||||||||||||||||||||||||||||||||
| {ticket.client_id} | The system-level client ID of the client this ticket is assigned to | ||||||||||||||||||||||||||||||||||||||||
| {ticket.email} | The email address the ticket was emailed in from | Only set when the email address is piped in and unrecognized | |||||||||||||||||||||||||||||||||||||||
| {ticket.summary} | A brief ticket summary | ||||||||||||||||||||||||||||||||||||||||
| {ticket.priority} | The system-level ticket priority | e.g. "critical", "high", "medium", etc. | |||||||||||||||||||||||||||||||||||||||
| {ticket.priority_language} | The language for the translated ticket priority | e.g. "Critical", "High", "Medium", etc. | |||||||||||||||||||||||||||||||||||||||
| {ticket.status} | The system-level ticket status | e.g. "open", "awaiting_reply", "closed", etc. | |||||||||||||||||||||||||||||||||||||||
| {ticket.status_language} | The language for the translated ticket status | e.g. "Open", "Awaiting Reply", "Closed", etc. | |||||||||||||||||||||||||||||||||||||||
| {ticket.date_added} | The UTC datetime stamp of ticket creation | Formatted as "YYYY-MM-DD HH:MM:SS" | |||||||||||||||||||||||||||||||||||||||
| {ticket.date_closed} | The UTC datetime stamp the ticket was closed | May be empty. Formatted as "YYYY-MM-DD HH:MM:SS" | |||||||||||||||||||||||||||||||||||||||
| {ticket.reply_id} | The system-level reply ID attached to this ticket | ||||||||||||||||||||||||||||||||||||||||
| {ticket.reply_staff_id} | The system-level staff ID of the staff member that sent this reply | ||||||||||||||||||||||||||||||||||||||||
| {ticket.reply_type} | The system-level type of reply | i.e. "reply", "note", "log". Emails are only sent when the type is "reply" | |||||||||||||||||||||||||||||||||||||||
| {ticket.reply_has_attachments} | Whether or not this specific reply has any attachments | v2.3.0 | |||||||||||||||||||||||||||||||||||||||
| {ticket.has_attachments} | Whether or not any replies to this ticket have any attachments | v2.3.0 | |||||||||||||||||||||||||||||||||||||||
| {ticket.details} | The ticket reply details in plain text | ||||||||||||||||||||||||||||||||||||||||
| {ticket.details_html} | The ticket reply details in HTML | ||||||||||||||||||||||||||||||||||||||||
| {ticket.reply_date_added} | The UTC datetime stamp of the reply | ||||||||||||||||||||||||||||||||||||||||
| Tags | Description | Notes | Since | ||||||||||||||||||||||||||||||||||||||
| {ticket_hash_code} | A hash code for validating ticket replies | Required to be in the subject line to allow for tickets to be replied to by email | {ticket.id} | The system-level ticket ID | {ticket.code} | The ticket number | e.g. "1821914" | {ticket.department_id} | The system-level department ID of the department this ticket belongs to | {ticket.staff_id} | The system-level staff ID of the staff member assigned to this ticket | May be empty | {ticket.service_id} | The system-level service ID of the service this ticket is in relation to | May be empty | {ticket.client_id} | The system-level client ID of the client this ticket is assigned to | {ticket.email} | The email address the ticket was emailed in from | Only set when the email address is piped in and unrecognized | {ticket.summary} | A brief ticket summary | {ticket.priority} | The system-level ticket priority | e.g. "critical", "high", "medium", etc. | {ticket.priority_language} | The language for the translated ticket priority | e.g. "Critical", "High", "Medium", etc. | {ticket.status} | The system-level ticket status | e.g. "open", "awaiting_reply", "closed", etc. | {ticket.status_language} | The language for the translated ticket status | e.g. "Open", "Awaiting Reply", "Closed", etc. | {ticket.date_added} | The UTC datetime stamp of ticket creation | Formatted as "YYYY-MM-DD HH:MM:SS" | {ticket.date_closed} | The UTC datetime stamp the ticket was closed | May be empty. Formatted as "YYYY-MM-DD HH:MM:SS" | |
| {ticket.replycompany_id} | The system-level reply company ID attached to this ticket was created under | ||||||||||||||||||||||||||||||||||||||||
| {ticket.reply_staff_id} | The system-level staff ID of the staff member that sent this reply | {ticket.reply_typedepartment_name} | The system-level type of replyi.e. "reply", "note", "log". Emails are only sent when the type is "reply"name of the department this ticket belongs to | ||||||||||||||||||||||||||||||||||||||
| {ticket.replydepartment_has_attachmentsemail} | Whether or not this specific reply has any attachments | v2.3.0The email address of the department this ticket belongs to | |||||||||||||||||||||||||||||||||||||||
| {ticket.hasoverride_from_attachmentsemail} | Whether or not any replies to this ticket have any attachments | v2.3.0 | {ticket.details} | The ticket reply details in plain text | the email template's from address has been replaced with the department email | i.e. "1" or "0" | v1.6.0 | {ticket.details_html} | The ticket reply details in HTML | ||||||||||||||||||||||||||||||||
| {ticket.reply_date_addedby} | The UTC datetime stamp of the reply | Formatted as "YYYY-MM-DD HH:MM:SS" | system-level type indicating where the ticket reply came from | i.e. "system", "staff", "client", or "email" | |||||||||||||||||||||||||||||||||||||
| {client.first | {ticket.company_id} | The system-level company ID this ticket was created under | {ticket.department_name} | The first name of the department client that opened this ticket belongs to | v2.20.0 | ||||||||||||||||||||||||||||||||||||
| { | ticketclient. | departmentlast_ | emailname} | The | email address of the department this ticket belongs to|||||||||||||||||||||||||||||||||||||
| {ticket.override_from_email} | Whether or not the email template's from address has been replaced with the department email | i.e. "1" or "0" | v1.6.0 | ||||||||||||||||||||||||||||||||||||||
| last name of the client that opened this ticket | v2.20.0 | ||||||||||||||||||||||||||||||||||||||||
| {reply_contact.first_name} | The first name of the last contact to reply to this ticket | v2.20.0 | |||||||||||||||||||||||||||||||||||||||
| {reply_contact.last_name} | The last name of the last contact to reply to this ticket | v2.20.0 | {ticket.reply_by} | The system-level type indicating where the ticket reply came from | i.e. "system", "staff", "client", or "email"
Departments
| Info | ||
|---|---|---|
| ||
When selecting POP or IMAP for email handling, be sure to select the proper Security option for the port you are using. None, TLS, or SSL may be required depending upon the port number you are connecting to. See http://www.arclab.com/en/amlc/list-of-smtp-and-pop3-servers-mailserver-list.html for a list of common configurations. |
...