Actions
Actions define what happens when an automation trigger fires. Each automation has three phases: First, Then, and Finally.
First Actions#
First actions happen before the main response is shown to the respondent. You can enable none, one, or both of these options.
Ask for Email#
The AI asks the respondent for an email address conversationally before continuing to the main action.
When to use: Use this when an automation creates a follow-up need, such as a churn-risk escalation, discount offer, hot lead, or meeting invite.
Important limitation: This is not a validated email input field. It is an AI prompt inside the conversation, so the respondent can answer in free text. Review the response before relying on the email.
Send Slack Message#
Sends a notification to the connected Slack channel.
When to use: Use this when your team needs real-time awareness, such as angry customers, urgent buying intent, feature requests, or support issues.
Slack messages include the trigger, relevant conversation quote, respondent email when available, the configured action, and a link back to responses.
The Slack option is available after Slack is connected in the project's Integrations tab.
Then Actions#
Every automation needs one main action. Choose one of these:
Offer Discount Code#
Shows a card with a discount code the respondent can copy.
Fields:
- Discount code: Required
- Context message: Optional supporting text
Use for: Price objections, discount requests, win-back flows, or conversion incentives.
Invite to Book Meeting#
Shows a card with a booking URL.
Fields:
- Booking URL: Required
- Context message: Optional supporting text
Use for: Churn-risk respondents, support escalation, hot leads, partnerships, or research calls.
Redirect to URL#
Shows a card linking to an external page.
Fields:
- Target URL: Required
- Context message: Optional supporting text
Use for: Signup pages, review sites, help docs, waitlists, or landing pages.
Finally#
After showing the main action, choose what happens next.
End Conversation#
The interview ends after the action is shown. Use this when the action is the final step, such as sending the respondent to a booking page, checkout flow, or external review page.
Continue Conversation#
The action card includes a continue option. When the respondent continues, the interview resumes from where it paused.
Use this when the automation is helpful but you still want to collect the remaining interview answers.
Example Combinations#
Win-back offer
- First: Ask for email and send Slack
- Then: Offer discount code
- Finally: Continue conversation
Escalate to human
- First: Ask for email and send Slack
- Then: Invite to book meeting
- Finally: End conversation
Capture hot lead
- First: Ask for email and send Slack
- Then: Redirect to demo signup
- Finally: End conversation
Route feature request
- First: Send Slack
- Then: Redirect to a roadmap, feedback board, or help page
- Finally: Continue conversation
Building Effective Automations#
- Match the action to the trigger: A meeting invite fits angry customers or hot leads better than a generic discount.
- Keep context messages short: One sentence is usually enough.
- Test URLs before publishing: Booking and redirect links should work before respondents see them.
- Use email prompts carefully: If email is essential, also add a required email question to your interview.
- Decide whether to continue: End the conversation only when the action should replace the rest of the interview.
Next Steps#
Ready to put it all together? Check out Examples & Recipes for complete automation setups.
Or learn more about Triggers to understand when automations fire.