Skip to content

docs(business-app): expand AI onboarding experience with verified behavior [WOW-2591][WOW-2566]#799

Merged
David-of-Growth merged 2 commits into
masterfrom
docs/ai-onboarding-experience-update
Jul 23, 2026
Merged

docs(business-app): expand AI onboarding experience with verified behavior [WOW-2591][WOW-2566]#799
David-of-Growth merged 2 commits into
masterfrom
docs/ai-onboarding-experience-update

Conversation

@David-of-Growth

Copy link
Copy Markdown
Contributor

Updates the existing AI onboarding experience page (business-app/ai-onboarding-experience) — same slug/URL, not a new page — to match the shipped code, and adds the detail partners have been asking for.

What changed

  • New "What the work summary shows" kitchen-sink table — every line the "We already got to work" summary can contain, the exact condition for it to appear, and the link offered. Addresses partner concern about what will actually show to their clients.
  • Rewrote "How a Vibe website is kicked off" (WOW-2566) — the precise trigger (send onboarding email + Early Access + Vibe active + no live site), the one-per-account behavior, and a dedicated "Making sure a Vibe site is not created" section.
  • Clarified that the "AI has done the work" Customize toggle controls display only and does not stop Vibe generation.

Accuracy fixes (verified against origin/master)

  • Onboarding email is single-user create + per-user resend action — the bulk-import flow has no onboarding-email handling (removed the bulk claim).
  • Upgrade cards dismiss per-product, not the whole section at once.
  • Dismissals are stored in per-browser localStorage, not a server-side per-user setting.
  • Aligned all checklist copy with the shipped email template (WOW-2646) and galaxy AI-work card.

Sources traced: business-center internal/onboarding/workflow/*, internal/user/service/onboarding*, mail/business-app-onboarding/en.html; galaxy apps/business-center-client/src/app/home/* and apps/partner-center-client create-user + customize-business-app.

Screenshots reuse the existing img/ai-onboarding-*.png assets (unchanged).

🤖 Generated with Claude Code

David-of-Growth and others added 2 commits July 22, 2026 17:58
…avior [WOW-2591][WOW-2566]

Reworks the AI onboarding experience page against the shipped code
(business-center onboarding workflow + galaxy home cards):

- Add a "What the work summary shows" kitchen-sink table listing every
  line the AI-work summary can contain, the exact condition for each,
  and the link offered — the detail partners keep asking about.
- Rewrite "How a Vibe website is kicked off": the exact trigger
  conditions (send email + Early Access + Vibe active + no live site)
  and a dedicated "how to make sure a site is NOT created" section.
- Clarify that the "AI has done the work" toggle controls display only
  and does not stop Vibe generation.
- Fix inaccuracies: onboarding email is single-create + per-user resend
  (no bulk handling); upgrade cards dismiss per-product; dismissals are
  per-browser localStorage.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…ls to FAQ

Review feedback from PM:
- Lead with the email being optional/opt-out (default-on but partner's choice).
- Demote the "how to prevent a Vibe site" detail from a mainline section to
  a one-liner under the kickoff section + a "Can I control whether a Vibe
  site is created?" FAQ entry.
- Drop the Customize card-toggle warning callout (kept the point as an FAQ note).
- Add explicit steps for sending the onboarding email to an existing user
  via the user options menu.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

@haleyserrano haleyserrano left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great to me!

@David-of-Growth
David-of-Growth merged commit faaac8e into master Jul 23, 2026
1 check passed
@David-of-Growth
David-of-Growth deleted the docs/ai-onboarding-experience-update branch July 23, 2026 14:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants