Choosing a Use Case
During onboarding
The setup assistant asks what you want to build first:- Exit interview — win back churning customers
- Customer survey — collect product feedback
In Settings
Settings → Use Case picks the default flow — what the bare link runs. Both flows always stay live: the Magic Links card shows two copyable links, one per use case. The non-default link carries an explicit?case= parameter so it stays pinned to its flow even if you change the default later.
Sharing the Survey
Surveys run on the same public route — there is no separate URL. Whichever flow is not the workspace default is reached by adding?case= to the link:
modeis ignored for surveys. Surveys are always non-blocking: no skip link, no decision screen, no pre-cancel gate.?mode=preon a survey link has no effect.
save_url is unused in survey mode — surveys never present save offers.
What the Customer Sees
- A greeting asking for honest feedback (“We’d love your honest feedback on your experience…”), top bar labeled “Feedback survey with ”
- A short conversation probing your configured focus areas (or general product experience if none are set)
- A thank-you screen with an optional “Return to ” link (
cancel_url)
What You Get
- The session appears in your dashboard interview list like any other session
metadata.themeis classified into the same taxonomy:pricing,missing_feature,ux_complexity,bugs_reliability,support,competitor,business_change,otherarchetypestaysnull— churn archetypes only apply to exit interviews- A completed survey fires the same
interview.completedwebhook and is billed the same way ($0.99 per completed session, minimum 3 turns) - All transcripts are PII-scrubbed before storage, exactly like exit interviews