If the same Survey is sent twice in the same workflow, will the user be able to fill the survey twice?
It will depend on how the survey is used the second time, there are 2 ways:
- Use ‘Survey URL’ from previous node context, in which case user will not be able to fill/respond the survey twice.
- Adding Survey to Email and SMS from the UI option to add ‘Survey’ in this case since its a separate instance the user will be able to fill/respond to the survey twice.
Can users edit their survey responses after submission?
No, users cannot edit responses once submitted for a specific instance of the survey. For example, if the same survey is sent via two different emails, each email represents a separate instance, and responses are tied to that instance. Editing within the same link or instance is not supported.
If the same survey is received again via email, can users respond again?
Yes, users can submit the survey again if it is sent as a new instance—such as in a follow-up email. Each email constitutes a separate instance, allowing the user to submit a new response.
Can internal users be given different access levels to Surveys?
Yes, Survey 2.0 supports three levels of access for internal users:
- No Access
- View Access
- Edit and View Access
These can be configured based on user roles and permissions.
Can I add a Matrix-type question in the Survey?
Currently, the Matrix question type is not available. However, this can be considered for future releases based on customer feedback and demand.
Can I attach multiple surveys to the same email or SMS?
Yes, multiple surveys can be attached to the same email or SMS communication. Each survey will function independently.
Can surveys be shared via WhatsApp?
Surveys cannot be directly attached using the WhatsApp node. However, the Survey URL can be included in the WhatsApp template message to share the survey with users.
What are the available ‘Previous Node’ fields in Survey 2.0?
The following fields are accessible as part of the previous node context:
- Survey Responded (True/False): Indicates survey completion. Useful in path and split logic.
- Survey URL: Can be inserted into Email/SMS/WhatsApp templates, or used in Update Info and Write ATS Note.
- Survey Transcript: Can also be added to messages and ATS records, providing full response history.
If the same survey is used twice in a workflow, can users respond both times?
This depends on how the survey is re-used:
- Scenario A: If the Survey URL is reused from the previous node context, users cannot submit the survey again.
- Scenario B: If the survey is added directly through the Survey insertion option in the Email/SMS step, it is treated as a new instance. In this case, users will be able to submit a second response.
Is there a limit to the number of questions in a survey?
No, there is no hard limit on the number of questions you can add in a survey. However, for usability and response rates, we recommend keeping surveys concise.
Can a survey be used in multiple workflows?
Yes, there is no restriction on the number of workflows a survey can be attached to.
Is there a character limit for naming a survey?
Yes, the survey name must not exceed 40 characters.
Can we anonymize survey responses?
No, anonymization of user details is currently not supported. Responses are linked to identifiable user records.
Can I add Google, Facebook, or other review links at the end of the survey or on the Thank You page?
Yes, you can include review links either within the survey as an HTML-type question or on the Thank You page. To do this:
- Prepare the content with your review links. Example:
- Convert this content to HTML (you can use ChatGPT or any HTML editor).
- Use the HTML question type if you want to show this during the survey.
- Alternatively, embed it in the Thank You page settings if it should appear post-submission.
Can the Thank You page vary based on user responses?
Yes, dynamic redirection to different Thank You pages based on a respondent’s answers is supported. This can be achieved by configuring Triggers in the Survey Settings. You can refer to the implementation in the ‘NPS Placement’ survey used by ARMStaffing for a working example.
What is the difference between Surveys in Journeys and Surveys 2.0?
Type | Feature/Description | Surveys in Journeys | Survey 2.0 | |
Question Type | NPS Rating (Standard 1 to 10) | Yes | Yes | |
Free text | Yes | Yes | ||
Multiple Choice Questions - Checkbox | Yes | Yes | ||
Multiple Choice Questions - Dropdown | No | Yes | ||
Date Selection | Yes | Yes | ||
Date and Time Selection | No | Yes | ||
Month Selection | No | Yes | ||
Week Selection | No | Yes | ||
Rating Scale - Numbers (1 to 10) | Yes | Yes | ||
Rating Scale - Numbers (1 to 5) | No | Yes | ||
Rating Scale - Stars | No | Yes | ||
Rating Scale - Smiley | No | Yes | ||
Read only expression | No | Yes | ||
Matrix | No | No | Possible in new surveys, exlcuded from Initial Scope | |
Link re-direction | Ability to add links and re-direct users to it on clicking | Yes | Yes | In Journeys, this is possible by adding Message touchpoint, whereas in Survey 2.0 its possible thru HTML (Refer Workflows created in ARM Staffing and 24seven) |
Automated link re-direction | Ability to automatically open any link/website post completion of Survey | No | Yes | |
Navigation | Show single question per page | Yes | Yes | |
Show multiple questions per page | No | Yes | ||
Show Table of Content/All Pages and their questions before start | No | Yes | ||
Validation on Response | In Multiple choice q, show choices from previous questions | No | Yes | |
In Multiple choice q, apply rule on visibility of choices | No | Yes | ||
Text Piping | Response value from previous question to be embedded in subsequent questions | No | Yes | |
Conditional visibility | Single level conditional branching | Yes | Yes | |
Multi-level conditional branching | No | Yes | ||
Conditional visibility of any question based on any question | No | Yes | ||
Response Preview | Ability to preview response before submitting | No | Yes | |
Validations | Ability to validate email id | No | Yes | |
Ability to validate phone number length | No | Yes | ||
Ability to validate expressions such as - Age, Difference in dates | No | Yes | ||
Write-back | Field Write Back | Yes | Coming Soon | Planned in Q3 2025 |
Note Write Back - Candidate entity | Yes | Yes | In J2, its based on custom writeback node which needs to be added by user | |
Note Write Back - Candidate Owner entity | No | Yes | ||
Alerts | Ability to send alerts to specific recipients | Yes | Coming Soon | Planned in Q3 2025 |
Flagged Response | Ability to flag a response based on specified configuration | Yes | Coming Soon | Planned in Q3 2025 |
ABT | Survey Completion | Yes | Yes | |
Survey QnA | Yes | Coming Soon | Planned in Q3 2025 | |
J2 advantage | Ability to attach Survey URL in subsequent nodes as part of Previous Node Context | NA | Yes | |
Ability to attach Survey Transcript in subsequent nodes as part of Previous Node Context | NA | Yes |