Example context. Preview only. Nothing is submitted.
When to sendAt first setup, when you can use the answers to choose a useful next step.
- 01
Make your product useful for you
Learn the desired outcome and starting point. Avoid invented use-case options that only fit one kind of product.
See the questions
- What would you like to accomplish first?
- Let the customer’s intended outcome lead the setup.
- Where are you starting from?
- Identify a real switch without forcing people who are adding a tool or just exploring to claim they are replacing something.
- 02
Make the switch easier
Only people replacing an existing tool see this step. Ask what must transfer so setup can help them switch.
See the questions
- What do you use today?
- Identify what a migrating user is replacing.
- What do you need to bring with you?
- Learn what must survive the switch: data, a workflow, or a team habit.
- 03
Your first step
Reveal an optional concern only when someone wants help. These answers must inform the next onboarding action.
See the questions
- Would you like help getting started?
- Ask whether the customer wants help before asking about a problem.
- What would help you get started?
- Reveal a concern field only when the customer wants help.
Using the answers
Group responses by desired outcome, then tailor the next setup step. Collect deeper switching stories in an interview rather than extending this intake.
When to choose another form
You cannot act on the answers. An extra questionnaire then only delays activation.
Before you publish
Connect the answers to an actual next step, migration resource, or person who can help. Remove the help question if nobody can respond.
Avoid asking for account or product information the app already knows.