Launch Chatbot or Reach already signed in

How the handoff works when someone opens an external product from Formbot.

When to use this. Someone is being asked to sign in again when they open Chatbot or Reach.

What you’ll need. The product switched on for the account, and a Formbot sign-in.

Know which products this covers
Chatbot and Reach are separate products, not screens inside Formbot. Opening one from the app switcher hands your identity across so you are not asked to sign in twice.
What happens on the way out
Formbot mints a single-use, short-lived credential for that specific product and sends the person onward. It is minted for one module, so a credential for one product will not open the other.
What the receiving product does
The product exchanges that credential for the launching user's identity, account context, entitlements, and branding. The exchange is a POST carrying the credential in a header rather than in the URL, so it does not end up in access logs, and it can be redeemed only once.
If the handoff fails
The usual causes are a credential already redeemed, one that has aged out, or a product switched off for the account. Check Products under Manage Account first, then have the person return to Formbot and launch again to mint a fresh one.
If you are building against it
Do not cache or replay the credential — it is single-use by design. Exchange it immediately on arrival and hold your own session from there.

How to know it worked

Opening Chatbot or Reach from Formbot lands the person signed in, in the right account.