Workflow

Prospect Showcase Conversion

Follow the sequence below, then use API Reference for payload schema and response details.

Steps

  1. Create a public prospect showcase request from the try form:

    Operation IDs: prospectShowcases.create

  2. Poll the prospect showcase status until the demo is ready or failed:

    Operation IDs: prospectShowcases.status

  3. Restore a saved permanent-link page from its durable portal credential:

    Operation IDs: prospectShowcases.portalStatus

  4. Subscribe to live prospect showcase status updates while the demo is provisioning:

    Operation IDs: prospectShowcases.stream

  5. Attach an email to an anonymous run at a value moment (waiting card, ready card, or portal) to receive the links and unlock the demo dashboard:

    Operation IDs: prospectShowcases.attachEmail

  6. Request a fresh access link from the expired-link recovery screen:

    Operation IDs: prospectShowcases.accessLinkResend

  7. Open the demo workspace with the emailed or in-flow claim token:

    Operation IDs: prospectShowcases.claim

  8. Claim the exact demo workspace into a customer-owned free account after the user provides the

    Operation IDs: prospectShowcases.convert

  9. Existing verified users explicitly select an empty customer workspace they currently own or

    Operation IDs: prospectShowcases.claimWorkspace

Notes

destination email. Access continues through the generated Supabase invite. The account and

rehomed site remain read-only while the user signs in and chooses a plan; only a

provider-confirmed active Starter or Pro subscription clears the managed-demo lock:

request another workspace with `targetAccountId: null`; no second email or invite is required:

The database revalidates ownership, emptiness, source readiness, and claim-token eligibility

under locks. The same site and history are rehomed atomically; existing workspaces/users are

never deleted as compensation. Replays must preserve the exact token and target choice.

workspaces remain locked pending paid activation. Retry the exact request after an uncertain

response so route caches can recover without repeating the database transition.

Related Docs