Exclude from a mailing list those who have already replied to a survey | XM Community
Skip to main content

Hi everyone, 

I have a survey that will be made accessible to a pre-determined list of customers through an app, which will simply notify them to access an anonymous link that will have an authenticator asking to log in.

Then, since we want to make sure we get as much response as possible, we will be later pushing by sending an email with the anonymous link, but I would like to have the email not being sent to those who already replied to the survey even partially. Is there a way in the mail sending allowing us to exclude those whose answers are already recorded?

I’d be very grateful if I could get a few hints on this one.

Thank you much in advance,

 

Guillaume

Hi @guillaume_JP. As you already know which customers might take the survey, you could create a mailing list with all of them. In your survey flow, add a web service task at the very start. This will be executed for each respondent - also for those who maybe did not complete. 

I am not 100% sure if the authenticator makes the contact ID available as this would be needed to update the mailing list contact or remove it from there. So you might want to try adding some embedded data ContactID after the authenticator. If this is available, you could either update the mailing list contact (e.g. with embedded data hasStarted = 😵 or you could completely delete it from the mailing list so that you could just send the reminder to anyone that remains in the list. 

If the ContactID is not available, you could only add all those to a new mailing list which have started/completed the survey using this web service request right at the start of your survey. Just like that: 

You would then need to exclude the contacts in this new mailing list from your overall list of potential respondents. The delta would be your target group for the reminder. 

Best
Christian

Thanks for your comment! As the list had an externaldatareference to be used as the contact ID of the customer, all that was needed was to set the embedded data in the survey flow, then create a branch in case the respondent doesn’t have an identified externaldataref. - which occurs when they access the anonymous link. 

The authenticator is then branched to the customer if he answered yes to a question asking him if he had an ID or if he had an identified externaldataref (which would apply if they receive an email invitation linked to their email). Then for the mail question, the system recognized those who already answered and did not dispatch an invitation to them.

Leave a Reply


Terms & Conditions