Page History

...

Tags	Description	Notes	Since
{update_ticket_url}	The URL for a client to visit to reply to this ticket
{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. "staff", "client", or "email"

Staff Ticket Assigned

This email is sent to a staff member when another staff member has assigned a ticket to them. This email template was made available in v2.6.0 of the plugin. The following tags are supported:

Tags	Description	Notes
{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.last_reply_date}	The UTC datetime stamp of the last ticket reply	Formatted as "YYYY-MM-DD HH:MM:SS"
{ticket.last_reply_staff_id}	The system-level staff ID of the staff member from the last reply	May be empty. Only set when {ticket.last_reply_by} is 'staff'
{ticket.department_name}	The name of the department this ticket belongs to
{ticket.company_id}	The system-level company ID this ticket was created under
{ticket.assigned_staff_first_name}	The first name of the staff member assigned to this ticket
{ticket.assigned_staff_last_name}	The last name of the staff member assigned to this ticket
{ticket.last_reply_by}	The system-level type indicating where the ticket reply came from	i.e. "staff", "client", or "email"
{ticket.last_reply_first_name}	The first name of the user that last replied to the ticket	May be a client or staff user
{ticket.last_reply_last_name}	The last name of the user that last replied to the ticket	May be a client or staff user
{ticket.last_reply_email}	The email address the last reply came from	Only set when {ticket.last_reply_by} is 'email'
{staff.id}	The system-level ID of the staff member this ticket is now assigned to
{staff.first_name}	The first name of the staff member assigned to this ticket
{staff.last_name}	The last name of the staff member assigned to this ticket

Expand

title	Additional Tags

Due to the nature of tag objects containing several fields, many of which are likely irrelevant for use in email templates, but may be useful to you in certain circumstances, an example dump of the {staff} tag object is shown below.

Code Block

language	php
title	The {staff} object
collapse	true

stdClass Object
    (
        [id] => 2
        [user_id] => 3
        [first_name] => First
        [last_name] => Last
        [email] => first.last@domain.com
        [email_mobile] => 
        [status] => active
        [username] => first.last@domain.com
        [two_factor_mode] => none
        [two_factor_key] => 6017d177a590b9cf0c04806e3634566a8f00190f
        [two_factor_pin] => 
        [groups] => Array
            (
                [0] => stdClass Object
                    (
                        [id] => 1
                        [company_id] => 1
                        [name] => Administrators
                    )
            )
        [notices] => Array
            (
                [0] => stdClass Object
                    (
                        [staff_group_id] => 1
                        [staff_id] => 1
                        [action] => payment_ach_approved
                    )
            )
    )

Staff Ticket Updated

The ticket received email template allows for the following tags:

...

Page tree

Versions Compared

Old Version 29

New Version 30

Key

Staff Ticket Assigned

Staff Ticket Updated