Once logged in to Customer Thermometer head to Thermometers > Add new Thermometer > Helpdesk > Select the Universal integration (cog image).
This will then open up your Thermometer Builder where you can create your survey and thank you pages.
The Question
This section of the builder is where you can choose the design of your survey including naming your Thermometer, adding your question and selecting your survey icons or uploading your own bespoke icons. The below video will demo all the customization which can be achieved in this section.
Connect your survey
In order for identifiable data about your recipients or senders to display within your reporting area, you first need to capture it. This would be done at the point that the email is sent, by including merge fields/variables from Accelo within the Thermometer code.
Please note, that in the user email signature section, only certain sender merge fields can be used.
These variables will capture the corresponding pieces of identifiable data from Accelo and present them alongside the recipient's feedback rating within your reporting.
Response options
In your Connect your survey area, you have additional response options. Here you can choose whether to enable a lockout and set your email alert notifications.
Thank you page
It’s time to get those Thank you pages looking beautiful!
See below for a step by step walkthrough:
Embedding your survey into Accelo
Once you've finished designing your Thermometer, the 'Give me my Thermometer' section will provide you with your finished survey to embed into Accelo. Scroll down and click copy.
You have two places you can embed the survey within Accelo, one within the email signature and the other within a ticket trigger.
Please note, that only sender variables can be used in the email signature section as shown below therefore, you will only be able to pull information about the sender of the survey to display next to the survey rating.
If you would like to pull additional details such as the recipient data, ticket ID etc then we would suggest embedding the survey within a ticket trigger email instead.