XM Directory Task - record initial response in directory | XM Community
Skip to main content

Hi folks! I am creating a survey with a workflow XM Directory task. The idea is that once the respondent takes the survey for the first time, their information is added to a contact list. This survey is for feedback for an in-person service. People will be asked to scan a QR code and fill out the survey each time they visit the service. I want to be able to track their responses each time, and see how many times they have filled out the service, as there are limits to how many times they can access it. Hence, why I wanted them added to a contact list. But, I won’t be sending them personalized links, they will always be scanning this anonymous QR code. 

I was able to set up an authenticator, so that if they select the option “I have visited the service before” in the first question in the survey, they are asked to input their email/ID number and this then connects their response to their contact ID (rather than using a personalized link). This seems to work just fine. However, the issue I am running into is that their first response (I.e., the one that triggers them to be added to the contact list) is never connected to their contact. So if they have taken 3 surveys total, it only shows they have taken 2 because the initial one is not connected to their contact ID. Does any one have solutions for this? 

@JordanDaniels You could track the number of times they take the survey using an embedded data field. In the workflow where you create the contact, you’d create a field, “Submissions” with a value of 1. 


You would bring the “Submissions” in as an embedded data field each time they authenticate. 

 

In a subsequent embedded data field, you would add 1 to the “Submissions” field using a mathematical operation.

 

You would then save this new value as the “Submission” in using a directory update workflow. You would need to use logic so that this workflow triggers when it is a repeat submission and your original workflow triggers if it is not a repeat. 

 

@jmborzick - thank you for this! I will give it a try. For the subsequent embedded data field using the mathematical operation - is this embedded data field being added to the same workflow or a different one? Also - do you have any suggestions for how to connect the initial submission to their contactID? I want to be able to bring up their contact card in my directory and see their first submission in the touchpoint along with all their subsequent ones

@JordanDaniels My initial thought was that it would have to be a different workflow, but upon reflection, no, it wouldn’t. In the initial response, it would pull a zero for the “Submissions” embedded data field and the calculation would turn it into a 1 for the first submission. If you pipe the results of the calculated field into the workflow, it would work just fine using just the one workflow. 

 

Regarding getting the initial submission as a touch point, I don’t know of a way to do that. However, you could accomplish this using embedded data by inserting the data from the initial submission as an embedded data field using the workflow. 

Leave a Reply


Terms & Conditions