What are some of the advantages of pre-creating survey records with Simple Survey?

 

Calculate True Response Rates: With survey records being pre-created, it is easier to identify if a survey was taken. You may leverage the status field on survey records to get more granular information in your reporting. For example, surveys that were sent but were not taken will maintain the "Pending" or "Sent" statuses, versus the "Responded", "Partial", or "Completed" statuses when "Capture Partial Responses" is enabled.

 

Multi-Channel Survey Invitations: Send the same survey link across multiple channels. For example, you can provide a link to a survey at the end of a chat session; if the person doesn’t respond, you can follow up the next day with an email invitation using the same survey link.

 

Resume Unfinished Responses: If respondents abandon the survey partway through, they can click the same link to continue showing their saved progress.

 

No Duplicate Records: Whether a human clicks the link multiple times or a security scanner clicks every link simultaneously, all go to the same record. This prevents multiple submissions from the same respondent or unexpected records from bots.

 

Easier Reporting for Any Object: We include a “Survey Response Rate for Cases” report that works well for the traditional method of dynamic record creation on the Case object. However, when surveying from other objects where there may be more than one survey recipient per object record, you can build a report that shows percentages of the different record statuses, like partially responded and completed.

 

 

How do I choose whether to pre-create or dynamically create survey records?

You should pre-create the survey records if you know who, when, and why you want to send a survey invitation. For example, when a customer orders a product, you create the survey record specifically for that customer and send the survey invitation when the order status changes to shipped or delivered.

You would not want to pre-create survey records for a “suggestion box” type of survey. For example, scanning a QR code printed in a manual would dynamically create the survey record. 

 

 

Should I switch from dynamic record creation to pre-creation?

If you have an existing survey program that works as desired, you don't need to change anything. If you plan to modify an existing survey program, consider the benefits of pre-creating survey records and using Simple Survey’s packaged Flow automation for sending email invitations.

 

 

Additional Notes

Unresponded Survey Records: When you pre-create survey records, you will likely have survey records without a response. These are unlikely to cause significant storage issues but may impact users’ list views. You should update the relevant list view filters to view only records with a response. You may also wish to delete old empty survey records to maintain data cleanliness.

 

Automation Adjustments: Your existing local automation (Flows or Triggers) may run when survey records are created. Your automation should incorporate Survey record statuses to prevent unintended processing. For example, if you currently have a Flow that creates a task for a manager to review a new survey record, you will want to change this to look at survey records when the status changes to responded or completed.

 

Enable Human Confidence Scoring: Simple Survey includes functionality to prevent responses from security scanners or bots. Use the “Human Confidence Score” field to filter bot responses your list views and prevent local automation from running due to a security scanner.

 

 

For any questions, please open a case with Vicasso's support team by emailing simplesurvey@vicasso.com.