The End-User Experience
What your users see - passwordless sign-in, the anonymous funnel, pricing, credits, and top-ups.
The end-user experience
Beta
The sign-in and monetization surfaces described here ship with Storefronts, currently in beta.
This page walks the journey from your end user's side, so you know exactly what you're putting in front of customers.
Signing in
Sign-in is passwordless: the user enters their email on your branded login screen and receives a 6-digit one-time code (from your Storefront's branded sender). Entering the code signs them in - first time creates the account, every later time returns them to their history, plans, and credits. One identity per email across your organization.
The anonymous funnel
When a Storefront allows anonymous access, visitors can start immediately - and convert in stages:
- Anonymous - auto-enrolled on the free default plan, capped by its anonymous credit limit.
- Hit the cap - asked to verify their email to continue.
- Verified - unlocked to the plan's full allowance, usage carried over (verifying never resets what they've used - and their conversations and settings move with them).
- Paid - upgrading to a paid plan requires the signed-in identity.
That's a built-in email-capture funnel: generous enough to hook, capped enough to convert.
Pricing and checkout
When a user needs a plan (or picks one), they see the pricing screen - your attached plans with names, prices, trials, and credit allowances. Paid checkout opens Stripe Checkout in a new tab (checkout can't run inside an embedded iframe); when payment completes, access activates automatically.
Living with credits
Signed-in users see a subscription bar in the experience:
- Current plan, renewal or cancellation state, and a credit meter.
- A soft warning at roughly 70% consumed; a hard stop at exhaustion with an upgrade path.
- Credit packs (when you offer them) - one-time top-ups whose credits survive the monthly reset and burn only after the allowance is used.
- Manage subscription - plan changes and cancellation through the Stripe-hosted portal.
- Their own API key (BYOK plans) - users on a BYOK-enabled plan can add their own OpenAI key so those runs don't consume credits.
Their data
Conversation history, personalization answers, and any private notebook content belong to the end-user identity and follow it across the Storefronts and Suites you've given them access to - scoped to your organization only.