Service reply templates
Template variables, also known as parser variables, are the mechanism used by Customer Service to dynamically insert data into a text like a reply template, it is used throughout the whole system. The syntax for a parser variable is the name of the variable enclosed by the tags
To get a complete overview of template variables available for your database, create a new reply template with the plain text body
%PARSER_TREE% (case sensitive).
When this reply template is used in a request, you will get a list of all available template variables by using the parser tree variable.
You will also find a complete list of all standard fields (this will not cover your user-defined fields) in our help file.
Not all parser variables are available in every context in SuperOffice Service. This section will describe which of the variables are available where in the solution. If you ever wonder which variables are available and the value of them, you can always use the special parser code
%PARSER_TREE%. This will be exchanged with all available variables and the values. This is especially useful when you want to debug why something is not working.
A parser variable may be available even if it has no value. One example is when creating a new request. If you use a reply template with the parser variable
ticket.id, it will contain no value since the request does not exist yet.
Some parser variables that exist will not be described. These are present only for backward compatibility.
It really depends on where the reply template is being used. Below the most common places to use them will be listed.
This feature requires a Service Essentials license. For details, see the list of user plans.
The same parser variables are available for new requests, edit requests, and add messages.
Reply templates on incoming email
Each incoming email box can be configured to send an automatic answer back to the customer using a reply template. The following parser variables are available:
In addition, you have a parser variable called
ticket.lastMessage which will contain the last message on the request, normally the text the customer wrote.
Here you may send a reply template to the customer or another email address. The following parser variables are available:
You can also extract anything from the email using Find regular expressions, and those matches will be available as parser variables (see the help for syntax).