Survey Triggers
Survey triggers let you automate follow-up actions when a respondent reaches the end of a survey. From the Survey Builder, you can send notification emails to stakeholders, send SMS messages, or invite respondents to a video interview — based on how the survey ended or on custom answer conditions.
Tip
Triggers run on live responses only. They do not fire when you test or preview a survey in the builder.
Related documentation
- Embedded Data
- Survey Builder Deep Dive
- Survey Logic & Branching
- Email Templates
- Sending Video Interview Scheduling Invitations via Survey Triggers
Open the Triggers panel
Open your survey in the Survey Builder
Go to Activities → Surveys, then open an existing survey or create a new one.
Open Tools → Triggers
In the Survey Builder top bar, click Tools, then select Triggers.
Review existing triggers
The Triggers dialog lists all configured triggers for this survey. Each row shows the trigger name, action type, enabled/disabled status, and event type.
Create a trigger
Click Create New Trigger
In the Triggers dialog, click Create New Trigger.
Choose an action
Select one of three actions:
- Send Email — notify stakeholders or team members
- Send SMS — send a text message to contacts
- Send Video Interview Invitation — invite a respondent to schedule or join a video interview
Configure the trigger
Fill in the form fields for your chosen action (see sections below).
Save
Click Save Trigger. The trigger appears in the list and is active when Enabled is checked.
You can Enable, Disable, Edit, or Delete any trigger from the list at any time.
When triggers fire
Triggers evaluate when a respondent reaches a terminal survey state:
| Survey outcome | Trigger event |
|---|---|
| Respondent completes the survey | Completed |
| Respondent is screened out / terminated | Terminate |
| Survey or quota group is full | Quota Full |
| Any terminal outcome | General |
| Answers match custom logic | Custom condition |
For Custom condition, use the same condition builder as survey logic. Quali-Fi creates a linked logic rule behind the scenes to evaluate the respondent's answers when the survey ends.
Send Email triggers
Use email triggers to notify colleagues, clients, or other stakeholders when something happens in your survey.
Each email trigger owns one reusable campaign (and, when needed, one managed contact list). Quali-Fi no longer creates a brand-new list and campaign on every fire, which keeps Email → Lists and Campaigns cleaner when a survey collects many completes.
Configuration
| Field | Description |
|---|---|
| Trigger Name | Internal label for this trigger |
| Enabled | Turn the trigger on or off |
| Send email if | Choose Completed, Terminate, Quota Full, General, or Custom condition |
| Conditions | Shown when event is Custom condition; build rules based on question answers |
| Recipient source | Choose exactly one mode (see below) |
| From email | Sender address for the notification |
| Email Template | Optional. Choose Default message (no template) or an active custom template from Email → Templates. Use New to create a template in a new tab, or Clear to revert to the default message. |
| Subject | Email subject line. Supports trigger placeholders and survey response recall via Insert recall / piping. |
| Schedule | Available for list and fixed-email modes; see Schedule options |
| Email Content (Message) | HTML message body. Same recall and placeholder support as Subject. When a custom template is selected, switch between Preview and Edit; edits apply to this trigger only and do not change the saved template. Without a template, a live Email Preview appears below the editor when content is present. This is the trigger form editor — not the campaign Visual / HTML / Preview builder used on Email → Campaigns and custom templates. |
Recipient source
Choose one recipient source. The modes are mutually exclusive:
| Mode | Who gets emailed | Notes |
|---|---|---|
| Enter specific email address(es) | The addresses you type (comma-separated) | Quali-Fi maintains one managed list for this trigger from those addresses. Optional member segments can be added. |
| Select existing email list(s) | Everyone on the selected Email module list(s) | Uses one reusable campaign per trigger. Optional member segments can be added. |
| Send to email collected in survey | Only the newly collected address from that response | Pick an email-capable question (Contact Form, Short Text, Long Text, and similar). Always sends immediately; schedule options are hidden. Duplicate emails already on the managed list are skipped. |
If no recipients can be resolved for a fire, the trigger is skipped silently.
Default content for new triggers
When you create a new email trigger, Quali-Fi pre-fills the subject and body with a built-in starter message (not your org's system Email Trigger Template):
- Subject:
{{surveyTitle}} update - Body: includes placeholders such as
{{message}},{{surveyTitle}},{{triggerName}},{{eventType}}, and{{orgName}}
Edit these fields before saving, pick a custom template from the Email Template dropdown, or replace the content entirely with your own copy.
Placeholders in email content
At send time (and in test sends), Quali-Fi substitutes trigger-level placeholders in the subject and HTML:
| Placeholder | Replaced with |
|---|---|
{{surveyTitle}} | Survey title |
{{triggerName}} | Trigger name |
{{eventType}} | Event label (for example Completed, Terminate, Quota Full, Batch) |
{{orgName}} | Organization name |
{{message}} | Default status message text |
{{responseId}} | Response id when available (empty for some batch sends) |
{{survey_url}} | That respondent’s survey access link when the fire has a response; otherwise the survey’s public entry URL. {{surveyUrl}} is the same value. |
Recipient contact variables ({{first_name}}, {{last_name}}, {{full_name}}, {{email}}) are still filled per recipient when that contact data exists on the resolved email list. Direct typed addresses usually have no name fields.
The trigger record keeps the {{...}} placeholders so the next send can resolve them again for that fire.
Survey link in trigger emails
If the message should open the survey, put {{survey_url}} on the button Link URL or in the body. Do not paste a one-off public URL if the respondent already has a personalized access link.
On a live fire, Quali-Fi uses the access link stored on that response (access_url) when it exists. That is the same link the respondent used to start. If that metadata is missing, the survey’s public entry URL is used instead.
Send test email and weekly batch have no single response to attach. Those sends use the public survey URL so the button still works. Answer-recall tokens stay blank on those paths — same rule as before.
Custom templates list {{survey_url}} in the variables panel. See Email Templates.
Recall survey answers in triggers
Subject and message body also support Insert recall / piping for prior answers, embedded data, other-specify text, multi-field parts, ranked items, and computed values. See Piping and Recall.
Contact fields ({{contact.first_name}}) do not belong here. Those tokens fill in the live survey after a signed email invitation, not in a trigger send. If the trigger email needs a name, use the campaign-style merge tags on a list send — or pipe a value you already captured in the survey.
A few send paths have no single response to pull from:
- Weekly batch emails — survey answer recalls stay blank (the batch is not tied to one response).
- Send test email — sample merge data only; survey answer recalls stay blank because the test is not linked to a live response.
Use immediate (per-response) sends when the email must include that respondent’s answers.
Using a custom email template
The Email Template dropdown lists active custom templates from Email → Templates → Your Custom Templates (the same reusable templates used for survey email distribution).
- Default message (no template) uses the built-in starter subject and body above.
- Custom template copies that template's subject and HTML into the trigger form. Switch to Edit to customize content for this trigger only; your saved template stays unchanged.
- New opens the custom template editor in a new browser tab.
- Clear removes the selected template and restores the built-in default message.
The preview panel substitutes sample values for common placeholders so you can review layout before saving.
Template content is stored on the trigger record when you save. It is not linked back to the template afterward. Editing an existing trigger shows the saved subject and body, not which template (if any) was originally selected.
For creating and managing custom templates, see Email Templates.
Schedule options
Schedule appears when the recipient source is fixed emails or existing lists (not survey-collected email):
| Mode | Behavior |
|---|---|
| Send immediately when triggered | Default. Each matching live response sends right away to the full audience for that mode. |
| Send on a weekly day and time | Matching responses are queued. Quali-Fi sends the queued emails together once per week on the day and time you choose (shown in your local timezone). |
Survey-collected emails always send immediately to the newly collected address only.
How email delivery works
When a matching live response is submitted, Quali-Fi:
- Evaluates the trigger event (and custom conditions, if configured)
- Resolves recipients for the selected recipient source (and optional segments for list-like modes)
- Reuses the trigger's managed list and campaign (creating them on first setup when needed)
- Substitutes trigger placeholders into that campaign's subject and HTML for this send
- Prepares recipients and sends through your organization's email infrastructure (same path as bulk email campaigns)
For weekly batch, fires queue until the scheduled window; a background runner then sends the accumulated audience once for that window.
The visible From email comes from the trigger. The sender display name defaults to QFI, unless your organization has verified custom email settings configured. In that case, Quali-Fi may use your organization's default sender name and from address instead.
Send SMS triggers
Use SMS triggers to send a short text when a survey event occurs.
Configuration
| Field | Description |
|---|---|
| Trigger Name | Internal label |
| Enabled | Turn on or off |
| Send sms if | Same event options as email triggers |
| Conditions | Custom condition builder (when applicable) |
| Recipient phone(s) | Comma-separated numbers in E.164 format (e.g. +15551234567) |
| Select sms list(s) | SMS contact lists from the SMS module |
| Message Body | SMS text (maximum 160 characters). Supports Insert recall / piping for survey answers and embedded data — same caveats as email when a send has no response context. |
| Scheduling window | Optional start and end datetime — SMS only sends if the response occurs within this window |
Recipient requirements
At least one of direct phone numbers or SMS contact lists must be configured.
How SMS delivery works
Matching triggers create a queued SMS campaign that the platform's SMS runner processes. Ensure your organization has SMS configured and sufficient credits.
Send Video Interview Invitation triggers
Use this action to move qualified respondents from a screening survey into a video interview workflow.
Configuration
| Field | Description |
|---|---|
| Trigger Name | Internal label |
| Enabled | Turn on or off |
| Trigger when | Same event options as other trigger types |
| Conditions | Custom condition builder (when applicable) |
| Video Interview Project | Select an existing project from Video Interviews |
| Recipient | Survey Respondent (Member) or a fixed Email Address |
| Include scheduling link in email | When enabled, sends the member_schedule_invitation email template with a unique scheduling URL |
| From Email | Sender address |
| Subject | Email subject (used for custom-body invites; scheduling template has its own subject) |
| Email Content | Custom HTML body — used when scheduling link is off; ignored for the scheduling email body when scheduling link is on |
Recipient: Survey Respondent (Member)
The invitation goes to the email of the member who completed the survey. Quali-Fi resolves the address from:
- The respondent's member ID on the response (typical for portal-distributed surveys), or
- An email field captured in a Contact Form question on the survey
If no valid email can be resolved, the trigger fails for that response.
Scheduling link option
When Include scheduling link in email is enabled:
- Quali-Fi creates a scheduling invite token and sends the member_schedule_invitation template
- Edit that template under Email → Templates (filter by
member_schedule_invitation) - The custom Email Content editor is not used for the scheduling email body
When scheduling link is disabled, the trigger sends your custom HTML content from the form.
For a full end-to-end walkthrough (recruitment survey → portal deployment → scheduling → session), see Sending Video Interview Scheduling Invitations via Survey Triggers.
Manage triggers
From the Triggers dialog:
- Disable — pause a trigger without deleting it
- Edit — change configuration; custom-condition logic rules are updated in place when possible
- Delete — permanently remove the trigger
Changes take effect on the next matching live response.
Best practices
- Name triggers clearly (for example, "Notify PM on complete" or "VI invite - passes screener")
- Use Custom condition for screening workflows (for example, send a video interview invite only when specific answers are selected)
- Pick the right recipient source - fixed addresses for a small stakeholder set, existing lists for broad notifications, survey field when each respondent should receive their own follow-up
- Test with live-like data - because test-mode responses do not fire triggers, validate with a small live pilot or Rhoxi AI simulation followed by a manual check of trigger configuration. Use the trigger's test send to preview trigger-level placeholders; expect survey answer recalls to be blank on that preview.
- Set up lists and templates first - email lists, SMS lists, custom email templates under Email → Templates, and video interview projects should exist before you configure triggers
- Review default trigger copy - new email triggers start with placeholder text; confirm placeholders resolve the way you expect, or replace them with static copy before going live
Known limitations
- Triggers do not run in Survey Builder test/preview mode
- Recipient source modes are mutually exclusive; you cannot mix typed addresses, existing lists, and a survey email field on the same trigger
- Survey-collected recipient mode cannot use weekly batch scheduling
- Recipient contact variables (
{{first_name}},{{last_name}},{{full_name}},{{email}}) are substituted per recipient when that contact data exists on the resolved email list; direct typed addresses usually have no name fields - The org system Email Trigger Template under Email → Templates is separate from the trigger form's Email Template dropdown (which uses custom templates). Customizing the system template does not change the trigger form's built-in default message
- Trigger Email Content uses the trigger form's Preview / Edit editor. Campaigns and custom templates use Visual / HTML / Preview. Applying a custom template copies HTML into the trigger; it does not open the campaign canvas
- SMS messages are limited to 160 characters
- Email trigger sender display name defaults to QFI when organization custom email settings are not active (the trigger From email field is always configurable on the form)
- Trigger execution history is stored internally but is not yet exposed in the Survey Builder UI
- Survey builder triggers are separate from Zapier integrations and REST API webhooks