Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Added "system" to the list of values for "reply_by" tags

...

TagsDescriptionNotesSince
{ticket_hash_code}A hash code for validating ticket repliesRequired 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 numbere.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 ticketMay be empty 
{ticket.service_id}The system-level service ID of the service this ticket is in relation toMay 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 fromOnly set when the email address is piped in and unrecognized 
{ticket.summary}A brief ticket summary  
{ticket.priority}The system-level ticket prioritye.g. "critical", "high", "medium", etc. 
{ticket.priority_language}The language for the translated ticket prioritye.g. "Critical", "High", "Medium", etc. 
{ticket.status}The system-level ticket statuse.g. "open", "awaiting_reply", "closed", etc. 
{ticket.status_language}The language for the translated ticket statuse.g. "Open", "Awaiting Reply", "Closed", etc. 
{ticket.date_added}The UTC datetime stamp of ticket creationFormatted as "YYYY-MM-DD HH:MM:SS" 
{ticket.date_closed}The UTC datetime stamp the ticket was closedMay 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 replyi.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 replyFormatted 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 emaili.e. "1" or "0"v1.6.0
{ticket.reply_by}The system-level type indicating where the ticket reply came fromi.e. "system", "staff", "client", or "email" 

...

TagsDescriptionNotesSince
{update_ticket_url}The URL for a client to visit to reply to this ticket  
{ticket_hash_code}A hash code for validating ticket repliesRequired 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 numbere.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 ticketMay be empty 
{ticket.service_id}The system-level service ID of the service this ticket is in relation toMay 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 fromOnly set when the email address is piped in and unrecognized 
{ticket.summary}A brief ticket summary  
{ticket.priority}The system-level ticket prioritye.g. "critical", "high", "medium", etc. 
{ticket.priority_language}The language for the translated ticket prioritye.g. "Critical", "High", "Medium", etc. 
{ticket.status}The system-level ticket statuse.g. "open", "awaiting_reply", "closed", etc. 
{ticket.status_language}The language for the translated ticket statuse.g. "Open", "Awaiting Reply", "Closed", etc. 
{ticket.date_added}The UTC datetime stamp of ticket creationFormatted as "YYYY-MM-DD HH:MM:SS" 
{ticket.date_closed}The UTC datetime stamp the ticket was closedMay 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 replyi.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 replyFormatted 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 emaili.e. "1" or "0"v1.6.0
{ticket.reply_by}The system-level type indicating where the ticket reply came fromi.e. "system", "staff", "client", or "email" 

...

TagsDescriptionNotesSince

{ticket.id}

The system-level ticket ID  
{ticket.code}The ticket numbere.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 ticketMay be empty 
{ticket.service_id}The system-level service ID of the service this ticket is in relation toMay 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 fromOnly set when the email address is piped in and unrecognized 
{ticket.summary}A brief ticket summary  
{ticket.priority}The system-level ticket prioritye.g. "critical", "high", "medium", etc. 
{ticket.priority_language}The language for the translated ticket prioritye.g. "Critical", "High", "Medium", etc. 
{ticket.status}The system-level ticket statuse.g. "open", "awaiting_reply", "closed", etc. 
{ticket.status_language}The language for the translated ticket statuse.g. "Open", "Awaiting Reply", "Closed", etc. 
{ticket.date_added}The UTC datetime stamp of ticket creationFormatted as "YYYY-MM-DD HH:MM:SS" 
{ticket.date_closed}The UTC datetime stamp the ticket was closedMay be empty. Formatted as "YYYY-MM-DD HH:MM:SS" 
{ticket.last_reply_date}The UTC datetime stamp of the last ticket replyFormatted as "YYYY-MM-DD HH:MM:SS" 
{ticket.last_reply_staff_id}The system-level staff ID of the staff member from the last replyMay 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 fromi.e. "system", "staff", "client", or "email" 
{ticket.last_reply_first_name}The first name of the user that last replied to the ticketMay be a client or staff user 
{ticket.last_reply_last_name}The last name of the user that last replied to the ticketMay be a client or staff user 
{ticket.last_reply_email}The email address the last reply came fromOnly 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  

...

TagsDescriptionNotesSince
{ticket_hash_code}A hash code for validating ticket repliesRequired 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 numbere.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 ticketMay be empty 
{ticket.service_id}The system-level service ID of the service this ticket is in relation toMay 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 fromOnly set when the email address is piped in and unrecognized 
{ticket.summary}A brief ticket summary  
{ticket.priority}The system-level ticket prioritye.g. "critical", "high", "medium", etc. 
{ticket.priority_language}The language for the translated ticket prioritye.g. "Critical", "High", "Medium", etc. 
{ticket.status}The system-level ticket statuse.g. "open", "awaiting_reply", "closed", etc. 
{ticket.status_language}The language for the translated ticket statuse.g. "Open", "Awaiting Reply", "Closed", etc. 
{ticket.date_added}The UTC datetime stamp of ticket creationFormatted as "YYYY-MM-DD HH:MM:SS" 
{ticket.date_closed}The UTC datetime stamp the ticket was closedMay 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 replyi.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 replyFormatted 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 emaili.e. "1" or "0"v1.6.0
{ticket.reply_by}The system-level type indicating where the ticket reply came fromi.e. "system", "staff", "client", or "email" 

...

TagsDescriptionNotesSince
{ticket_hash_code}A hash code for validating ticket repliesRequired 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 numbere.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 ticketMay be empty 
{ticket.service_id}The system-level service ID of the service this ticket is in relation toMay 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 fromOnly set when the email address is piped in and unrecognized 
{ticket.summary}A brief ticket summary  
{ticket.priority}The system-level ticket prioritye.g. "critical", "high", "medium", etc. 
{ticket.priority_language}The language for the translated ticket prioritye.g. "Critical", "High", "Medium", etc. 
{ticket.status}The system-level ticket statuse.g. "open", "awaiting_reply", "closed", etc. 
{ticket.status_language}The language for the translated ticket statuse.g. "Open", "Awaiting Reply", "Closed", etc. 
{ticket.date_added}The UTC datetime stamp of ticket creationFormatted as "YYYY-MM-DD HH:MM:SS" 
{ticket.date_closed}The UTC datetime stamp the ticket was closedMay 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 replyi.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 replyFormatted 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 emaili.e. "1" or "0"v1.6.0
{ticket.reply_by}The system-level type indicating where the ticket reply came fromi.e. "system", "staff", "client", or "email" 

...