@j o ,
You have two options to streamline this process and avoid manual branching:
1. XM Directory (Contact List) Approach:
Keep your employee list in the XM Directory. You can dynamically populate a dropdown or autocomplete question in your survey using embedded data from the directory. When a respondent selects an employee, store their selection as embedded data and use piped text in your email task to send the notification directly to the selected employee’s email address. Updating the contact list in the directory automatically updates your survey and workflow logic, no need to manually edit branches or tasks.
2. Supplemental Data Source (SDS) Approach:
Alternatively, you can create an SDS with your employee list. SDS allows you to reference the dataset in autocomplete questions or customize survey flows. When an employee is selected, you can pull in additional details (like their email address) from the SDS and pipe that info into your email task. SDS is ideal for high-turnover lists, since you only need to update the SDS file in your library or survey flow, and changes are instantly reflected in your survey and workflows.
Both methods let you automate the process and keep your survey logic clean and scalable. Just update your employee list in the directory or SDS, and everything else stays in sync!
