CA Service Management

We are going to be implementing surveys for our help desk and are trying to see if there is a way to include the ticket's number somewhere on the survey or in the email itself.  This is necessary as the users will likely not take the survey right away and it will help remind them of what took place.

We currently have the survey triggered by the 'Resolved' activity notification so the options for entering info are limited.

Hi Richard,

The Email subject for the survey should have the ticket number in it and so should the notification template used for the resolved notification.  As for getting it into the survey itself is an interesting one - I do see the use case for it, especially if folks get a lot of surveys for different tickets.  Unfortunately currently its not possible to do that - but I think thats a good one.  I would say to post that as an idea to the community here and let folks vote for it.

Thanks,
Jon I.

Hey Richard,

I have confirmed that by default, the mail notification that indicates for the survey will name the ticket number associated.  However, the survey itself will not include the associated ticket number.  There does not appear to be a direct approach to include the associated ticket number in the survey display either.

I would agree with Jon that this would definitely be worth a mention as an idea to communities.

I am currently testing with this and do not have the Incident/Request number in the email.  Is there a setting I am missing? 

Also, I will definitely put this up for an idea as it would really help keep track of what survey is for what ticket.

Which notification template is being used?

Jon

It was the Activity Notification for Resolved status and I have the Email Notification method selected.  David's suggestion below was able to provide the desired result.

Hello,

Please include this string sequence somewhere in the Survey Message Title of your activity notification:

@{call_req_id.type.sym} @{call_req_id.ref_num}

This will add the ticket type and ticket reference number.

I must have been using the incorrect version to call the objects because this worked right away. Thank you!