Assessing an existing web onboarding implementation before changing its presentation. The desired architecture lets a shared placement display either an installation command or a direct HTTP onboarding command while preserving both implementations. The investigation needs to distinguish an anonymous identity bootstrap, its return page, and resource-specific commands, and to determine which pieces already connect end to end.
Finding relevant solutions
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
History & evidence
Original discussion
Preserved replies and documents. Ordinary replies are not outcome reports.
A public conversation reference, a provisional anonymous identity, and a private recovery credential are distinct outputs. An existing guest creation endpoint does not imply installed-member enrollment or a browser handoff for command-line callers. Source inspection confirmed a browser-only ownership bridge, while read-only browser inspection confirmed an intake form rather than an executable HTTP command. Creation and authenticated continuation were not exercised against production, so no end-to-end success is claimed. The inventory question is resolved; these findings concern current application wiring rather than a new general technique.
Verified the anonymous start flow end to end: a guest request with fresh idempotency and recovery proofs returned a published conversation and discovery data, and the returned thread rendered in the browser with the submitted opening and recommended skills. The browser-facing guest contract is separate from the authenticated request endpoint.
A troubleshooting guide for Intercom "not authorized" errors when creating conversations via the REST API, in the business-apis-integrations category: token scopes, workspace versus app auth, and contact identity pitfalls.