Do we send a 'feedback received' email??

[bert-granberg]

What's the best practice for a web app to email back automatically a confirmation to the email address provided. This could possibly be used to send unwanted anonymous emails with any sort of messages. I think we need to gatekeep this function or hide the specific feedback provided from the confirmation. Your thoughts?

[stdavis]

I'm not sure what best practice is. Maybe @steveoh has some thoughts on this. I know many websites send a confirmation code to your email address and ask for it back. Maybe we could implement something like that.

[stdavis]

My current thought is the we make the following changes:

• Add reCAPTCHA to the form to prevent bot submissions

For users who input an email address:

• Once the form is submitted, send them an email with a verification link in it that they have to click on before their submission is processed. Then they would get a second email with the confirmation content that we currently have. This would make sure that the user owns the email address that they input into the form. If the user never clicks the verification link in the email, the feedback is discarded after 14 days.

I'd love to get @steveoh's thoughts on this when he gets back next week.

[steveoh]

I apologize for missing my mention here. I do have some thoughts.

I would like to propose that we use existing software instead of writing it. We have access to qualtrics and I learned that it can handle this use case and much more.

We should be able to create a form with embedded data from the bike app that can capture feedback. Qualtrics can handle the recaptcha bot issues and the submission can trigger workflows to contact the person if they provided an email address. Qualtrics can also notify wfrc of the new submission and create an internal ticket for them to triage. The ticket can be acted on which can then trigger more emails to notify the submitter of any updates, fixes, or rejections.

I would prefer we use a system like this instead of writing code.

[stdavis]

From Jake Ball at Qualtrics:

Thanks for the follow up. I think based on our conversation the other day, it probably just makes sense to use an iframe like we discussed.

The SV value is the surveyID. You can see this in the URL when you are in the survey within Qualtrics. I think I grabbed the right one from your account, but maybe check to be sure. We should be in the pdx1 server with utconcierge.

<iframe height="850px" src=://[utconcierge.pdx1.qualtrics.com/jfe/form/SV_1ZdnjA8jUjskoAK?FieldName1={set](http://utconcierge.pdx1.qualtrics.com/jfe/form/SV_1ZdnjA8jUjskoAK?FieldName1=%7Bset) this with JS}&FieldName2={set this with JS}" width="100%"></iframe>

Then within the survey builder in survey flow, we would just want to add matching fields in embedded data so that we capture these fields with the response upon completion. Once we can confirm that we are able to pass data through it might make sense to meet about setting up any additional workflows like email, ticketing, or Google Sheets.