Two halves of the same thing: getting people into the conversation, and letting them leave it.
In. When the flag is on, a new signup lands in onboarding after team creation. No question about whether they want it, no choice screen first. It just starts, with the Expert already talking.
Out. A control that's always available and says something like "I'd rather set it up myself". Pressing it calls the on-demand provisioning endpoint and drops them on the classic team home with the application and instance a classic signup would have given them.
The out control stays visible the whole way through, but goes quieter once the user engages with the conversation. Present, not competing.
Done when
- A flagged signup ends up in onboarding without being asked.
- A non-flagged signup goes exactly where it goes today.
- The way out produces the same result as a classic signup and never leaves a team with nothing in it.
- The control is reachable at any point in the conversation, and recedes visually after the user engages.
Worth knowing
Where onboarding sits in the routing is worth thinking about rather than assuming. A dedicated route gives it a URL, which makes it returnable and makes the PostHog funnel cleaner to instrument. A modal over the team home is less structural but means the user is nowhere in particular. Either works, and the surface direction being chosen on the parent might decide it.
Billing won't get in the way. requiresBilling is false while isTrialAccount is true and the trial hasn't ended, so team/index.vue won't bounce a fresh trial signup to the billing page before onboarding can render.
The current path after email verification sets a flag that triggers the welcome tour, which is being suppressed on this path in a sibling task. Worth coordinating so the two don't fight over what happens on arrival.
"Recedes after engagement" needs defining. Probably first answer submitted, or first message sent, rather than something time-based. Worth picking something observable rather than a timer.
Two halves of the same thing: getting people into the conversation, and letting them leave it.
In. When the flag is on, a new signup lands in onboarding after team creation. No question about whether they want it, no choice screen first. It just starts, with the Expert already talking.
Out. A control that's always available and says something like "I'd rather set it up myself". Pressing it calls the on-demand provisioning endpoint and drops them on the classic team home with the application and instance a classic signup would have given them.
The out control stays visible the whole way through, but goes quieter once the user engages with the conversation. Present, not competing.
Done when
Worth knowing
Where onboarding sits in the routing is worth thinking about rather than assuming. A dedicated route gives it a URL, which makes it returnable and makes the PostHog funnel cleaner to instrument. A modal over the team home is less structural but means the user is nowhere in particular. Either works, and the surface direction being chosen on the parent might decide it.
Billing won't get in the way.
requiresBillingis false whileisTrialAccountis true and the trial hasn't ended, soteam/index.vuewon't bounce a fresh trial signup to the billing page before onboarding can render.The current path after email verification sets a flag that triggers the welcome tour, which is being suppressed on this path in a sibling task. Worth coordinating so the two don't fight over what happens on arrival.
"Recedes after engagement" needs defining. Probably first answer submitted, or first message sent, rather than something time-based. Worth picking something observable rather than a timer.