---
title: "Survey Configuration"
slug: "survey-configuration"
updated: 2025-09-24T07:57:24Z
published: 2025-09-24T07:57:24Z
canonical: "zenoplesupport.aqore.com/survey-configuration"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://zenoplesupport.aqore.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Survey Configuration

## ![](https://cdn.document360.io/f6cab4f2-9572-4cd7-96b4-39b941f22824/Images/Documentation/image-1758700002011.png)

- **Initial Question**: The first question posed to the entity.
- **Response Options**:
  - Positive response (e.g., “Yes”) leads to a configured follow-up question or action.
  - Negative response (e.g., “No”) leads to a different follow-up question or action.
- **Add New Step**: Allows additional questions or actions based on prior responses.
- **Action Options**:
  - **Select Action**: Choose SMS or Email for follow-up.
  - **Sender Profile**: Select the profile for the action.
  - **Select Recipient**: Options include User Role (notify a specific role associated with the entity) or Office Profile (notify the office).
  - **Body**: The message content for the action.
- The survey UI supports easy branching, visually displaying question paths.

## **Example Survey Configurations**

The following examples illustrate how surveys can be configured for specific use cases, demonstrating the branching logic and action integration.

**Example 1: Candidate Pre-Screening Survey**

This survey assesses a candidate’s interest and qualifications through a series of questions.

| **Step** | **Question** | **Responses and Next Steps** |
| --- | --- | --- |
| **Entry Point** | “Hey, do you have a few minutes to chat?” | - **Yes**: Proceed to Step 1. - **No**: End survey. |
| **Step 1** | “Are you currently looking for a new job opportunity?” | - **Yes**: Proceed to Step 2 (Experienced). - **No**: Proceed to Step 2 (Not looking). |
| **Step 2 (Yes)** | “Do you have at least 1 year of experience in your field?” | - **Yes**: Proceed to Step 3. - **No**: Proceed to Step 3. |
| **Step 2 (No)** | “Would you like us to notify you when future opportunities arise?” | - **Yes**: Proceed to Step 3. - **No**: End survey. |
| **Step 3 (Yes)** | “Are you open to contract or temp-to-hire roles?” | - **Yes**: Proceed to Step 4. - **No**: Proceed to Step 4. |
| **Step 3 (No)** | “Would you be interested in entry-level roles or internships?” | - **Yes**: Proceed to Step 4. - **No**: End survey. |
| **Step 4 (Yes)** | “Are you authorized to work in the U.S.?” | - **Yes**: Proceed to Step 5. - **No**: Proceed to Step 5. |
| **Step 4 (No)** | “Would you like us to filter roles only based on your preferences?” | - **Yes**: Proceed to Step 5. - **No**: End survey. |
| **Step 5** | “Would you like to schedule a quick call with a recruiter?” | - **Yes**: Trigger calendar invite or contact. - **No**: End survey with thank-you message. |

**Example 2: First Day of Assignment Survey**

This survey gathers feedback on an employee’s first day of an assignment.

| **Step** | **Question** | **Responses and Next Steps** |
| --- | --- | --- |
| **Entry Point** | “Hey, do you have a few minutes to chat?” | - **Yes**: Proceed to Step 1. - **No**: End survey. |
| **Step 1** | “Were you able to reach the work location without any issues today?” | - **Yes**: Proceed to Step 2. - **No**: Proceed to Step 2. |
| **Step 2 (Yes)** | “Did someone guide you onwatkins on your tasks or give you an orientation?” | - **Yes**: Proceed to Step 3. - **No**: Proceed to Step 3. |
| **Step 2 (No)** | “Was the issue related to transport, confusion, or something else?” | - **Transport/Confusion**: Proceed to Step 3. - **Other**: Proceed to Step 3. |
| **Step 3** | “Do you feel comfortable with your assignment so far?” | - **Yes**: End survey with “Great! Wishing you a successful assignment!” - **No**: Offer support or notify recruiter for follow-up. |

## **Special Scenarios**

For the “When Assignment Shift Starts” and “When Assignment Shift Ends” triggers, when the **Delay Time Unit** is set to **Days**, the action is executed based on the specified number of shifts. For example:

- A delay of “4 Days” means the action occurs on the fourth shift.
- **Hour** and **Minute** units function as standard time delays (e.g., 10 minutes before the shift starts).

This functionality is particularly useful for scheduling actions like surveys or reminders tied to specific shift milestones.