Setting up and using the Survey App

The survey app allows you to ask 0 - 10 questions at the completion of each ticket. Those scores can then either be translated into satisfaction scores visible on the ticket or over in insights you can calculate things like *NPS®, averages, breakdowns and more. You can even define the look and feel of the survey based on the brand of the ticket!

This comes in super handy for companies that want to get more granular with the sentiment of their customers than Zendesk's existing 'Good' or 'Bad' sat ratings. It can also help companies that want to ask their customers for an NPS score after every ticket.

Note: When installing the app, it is not recommended that you restrict the survey app to any specific role or group of agents because the app will not be able to hide the app's ticket fields for the agents who have been restricted. The app actually contains it's own restriction settings where you can do this while retaining the required functionality for all of your Zendesk users.

Step 1: The most important part of the survey app is to actually send it. The way that we do this is to add the placeholder {{dc.survey_app_snippet}} to the trigger or automation that you want to send the survey.

If you're already using Zendesk CSAT ratings, then all you'll need to do is go into the trigger or automation you have sending it and replace the placeholder {{satisfaction.rating_section}} with {{dc.survey_app_snippet}}

Step 2: The next step is to define what your survey landing page looks like. This is where your customer is sent after they click on 0-10 in the trigger email you defined in step 1.

So to do this click on the survey app icon on the left of the screen and this click on the 'Brands' tab. If you have multiple brands you'll be able to change the colours, logos and other details for each one. If you only have one brand, no problems! You'll only see the one ;-)

To edit a brand's survey landing page simply click the "edit" button on the right like this:

As you can see below, in the edit screen you can upload your desired logo & colour, set the URL that your customer will be redirected to after they fill out the survey, and define the wording of both your questions.

Once you're happy with your settings, click 'save' at the bottom. You can then preview what your survey landing page will look like by clicking the eye icon on the right of the "brands" tab like this.

And a screen will pop-up to show your preview like this:

If you'd like to brand the URL of the survey landing page contact us at support@sweethawk.co and we'll help you get that setup.

Step 3: Once you're happy with the look of the survey lets make sure you're happy with the settings.

Click on the settings tab at the top like this:

Here you can decide if you want the satisfaction score to translate to a Zendesk good or bad satisfaction rating. And if you do, you also get to decide the threshold. In the image above, anything 7 and above will come through as a good satisfaction on the ticket.

If you'd only like to ask one question instead of two, uncheck the 'secondary NPS question'.

If you'd prefer to only ask the NPS question once every now and again instead of on every ticket, just select a minimum time that should expire before they will see that part of the survey.

Another option here is to show a summary of what the ticket was about at the bottom of the landing page. If you'd like to remove that from the survey screen, simply uncheck the box.

One small, but, far-reaching option in your settings, is to turn on ticket tagging like this:

By turning this on, any ticket that has been rated by a requester will have corresponding tags automatically added to the ticket. For example, if a sat score of 8 was given and an organisation score (ie. NPS score) of 10 was given, then the ticket will have the tags ticket_score_8 and org_score_10 added to it like this:

This may not seem like much, but what this means is that you can now build views, triggers and automations to do stuff based on the precise scores given.

For example, if you wanted to notify the whole company via slack and escalate the ticket to URGENT for all tickets rated from 0-3 then you could do this with a trigger!