Add Survey Link to Incident Closed Email

alhicks
Tera Guru

We're looking at combining our Survey email with our Incident has been closed and our Ritm has been completed, emails.     Our management is wanting 1 email to be sent to the customer and the survey to be included.   So basically, on every closed incident or ritm, our customer would have a link to the survey.

I'm trying to figure out what the survey link should be and will we break something by doing this?    

1 ACCEPTED SOLUTION

If you want a survey every time, then simply take all your closure info, and put it into the Survey trigger email instead.   You might have to be a little more creative in dot-walking to the fields that you need, but this is the only way to pull it off.



EDIT:   The reason you can't just add a Survey link to the Incident closure email is that the incident closure email is triggered by an event.   That event is fired by a business rule that only looks for the Incident to be moved to Resolved.   That could be miliseconds or even seconds before the survey is launched, so there's no record for which to form a Survey URL.  


View solution in original post

29 REPLIES 29

Happy to be of service.  Maybe a half decent topic for my Youtube channel.

gbernie
Kilo Expert

We sort of do this for when incidents are resolved and are assigned to a certain group.


We have a survey that has no conditions and we simply put the survey URL inside the resolved emails.


The issue with doing it this way is that there is no link to the incident as anyone who has the link can complete the survey. We have also found that not many people actually read the resolved emails and a better option was to send it as a separate email using conditions so there is a link. We do the later for our HR Department and the response rate is far higher.


TrevorK
Kilo Sage

We do something similar to what you are asking, with a slight twist (just a little logic because we don't want surveys 100% of the time, obviously it would be easy to just send all the time). Because my answer is rather long, I have just copied what I have posted before (Re: Survey Management and data gathering).



(we are using assessments and not legacy surveys, but a solution below should be able to be adapted)


1) Upon closure of an Incident or RITM, we determine if a survey is required. For example, we do not want to survey students and there are certain assignment groups that do not receive a survey. We use a flag on the TASK table that we fill in if a survey is required.


2) Our notifications are two-tiered. We send a normal "Your Incident has been resolved" if our "Survey Required" flag is false. This comes off the Incident table. If "Survey Required" is true, we send a notification off of the Assessment Instance table. Because the Assessment Instance has "Trigger ID" (a field that contains the sys_id of the record calling it), we use a Mail Script to lookup the associated Incident or RITM information based on the sys_id. We then send out a "Your Incident has been resolved" email similar to above, however it is from the Assessment Instance table. We include our survey specific information in it (we use some cool graphics to entice them to click on the survey) and the Incident/Task information, which is obtained through the mail script.


3) Client takes the survey, we then do a custom table to transform the results into a format that is much easier for management to handle (a table where each row contains the questions/answers, rather than the ServiceNow format of each row being a question). We have some reporting we need to do based on the results of a specific question, and this kept it the "prettiest" for management and the most functional for our user base. The table just updates upon a survey changing to "Complete". Because we have the "Trigger ID" value (which again is the sys_id of the incident/task that called it), we can reference who the analyst was that did the ticket, the business service, etc.



This survey is limited to the client themselves (only they can fill it out), and clicking on the face translates what they selected into the first question (whether you are happy, neutral or upset determines what questions you are asked). Our response rate was 12% last time I checked, but I have not checked in awhile. We have been told by our research people that 12% is a pretty good response rate for electronic surveys that are unsolicited.




We have found that the survey module required more work than we assumed it would, so I would be happy to share any information with you to help you get this up and running. You can feel free to message me and we can chat over email/phone - I have helped out a couple other people who wanted this sort of functionality in their environment. For some reason SN didn't make it as easy to do as I think it should have been to have this work in many real-life scenarios.




Below is a copy of our email, I believe this is what you are ultimately looking for?



Survey Email.PNG


Hi,



We are also looking to implement something similar.



When the incident gets resolved, an email is sent out. In that email, I want to include 3 options



Satisfied, Neutral, Not Satisfied



If the user selects Satisfied or Neutral, nothing will happen


If user selects not satisfied, then a field on the associated INC will get updated and that will trigger a survey.



How are you passing the information or updating a field on the INC if the user clicks the red or not satisfied button?


Can this be achieved using a API call or web service. Any suggestion would be of great help!!




Thanks,


Our survey works a little different then what you are thinking of doing - clicking on one of the faces in the email opens up the survey itself with the first question populated, and because the first question was answered it opens up the set of questions that relates to the face they clicked.



For example, when they click the happy face they do not receive the series of questions that relate to what made their experience poor.




I may be biased because of how we did our survey, however I would think that you would want to store Satisfied/Not Satisfied/Neutral in the survey itself. The survey is linked to the Incident, so there is a relationship there to report on. If they click Satisfied or Neutral it would take them to the survey webpage thanking them for their feedback while Not Satisfied would prompt a series of questions on the survey webpage.



I am not sure if our example is what prompted you to think of doing it in Incident - we do not store the value on the Incident table. Our notification is based on Incident closure, but all the data is stored completely within the survey table.




Any questions let me know!