You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Table of Contents

The Support Manager is a support plugin included with Blesta. It may be installed under [Settings] > [Company] > Plugins and is not installed by default.

Support Emails

Support related email templates can be found under [Settings] > [Company] > [Emails] > Email Templates, in the section labeled "Plugin Templates".

Ticket Bounce

The ticket bounce email template does not support any tags.

Ticket Received

The ticket received email template allows for the following tags:

TagsDescriptionNotes

{ticket.id}

The system-level ticket ID 
{ticket.code}The ticket numbere.g. "182191"
{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.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.reply_by}The system-level type indicating where the ticket came fromi.e. "staff", "client", or "email"

 

Ticket Updated

The ticket updated email template alows for the following tags:

TagsDescriptionNotes
{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. "182191"
{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.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.reply_by}The system-level type indicating where the ticket came fromi.e. "staff", "client", or "email"

 

Staff Ticket Updated

The ticket received email template allows for the following tags:

TagsDescriptionNotes
{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. "182191"
{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.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.reply_by}The system-level type indicating where the ticket came fromi.e. "staff", "client", or "email"

 

Staff Ticket Updated (Mobile)

The ticket received (mobile) email template allows for the following tags:

TagsDescriptionNotes
{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. "182191"
{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.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.reply_by}The system-level type indicating where the ticket came fromi.e. "staff", "client", or "email"
  • No labels