Getting started

From invitation to your first chat inside your own application. Your users keep signing in to your application; workspace invitations are for your operators.

1. Accept your invitation

Open the invitation with the email it names. It lasts 72 hours and can be accepted once. Ask your owner or support team to resend it if it has expired.

2. Sign in

Open /admin/ on the supplied chat host. Use your invited email, Google, an emailed link, or configured SSO. Members see Overview and Open the chat; Owners and Admins manage workspace settings.

3. Create a server key

Open Seats & licence → API keys. Copy the secret once into your backend secret manager. Console sign-in keys are hidden. Revocation takes effect on the next request; switch your backend to a replacement first.

4. Allowed sites

Open Integrations → Allowed sites and publish each exact HTTPS origin, including the mobile WebView page. No paths, trailing slashes or wildcards. The tenant administrator can also GET or PUT /api/v1/admin/embed/origins.

5. Backend token mint

Authenticate your application user on your backend and derive the user ID there. Mint an origin-bound token, issue a frame ticket, and return a ticket envelope. Follow the backend contract; server keys stay on your backend.

6. First embedded chat

Follow the module-loader example. Use your console snippet and independent key ring. The loader creates the user-owned thread. Check an answer, Stop, receipt and renewal from your approved HTTPS site.

7. React Native

Load the same authenticated hosted page in a restricted WebView. Establish its application session, renew on foreground and discard access on logout. See React Native. Test real iOS and Android devices before a store release.

8. Billing and low balance

Confirm your billing arrangement and check user entitlement on your backend before issuing access. Minting does not guarantee a paid turn. Use the settled receipt and stop automatic retries on low balance. Review Usage and Seats & licence → Limits. Your app remains responsible for its own user billing. Tenant-wide and per-user limits, typed host refusals and spend holds are described in Limits and host errors.

9. Support

Open the signed-in console Support/intake page; it reaches the SUP queue. Include workspace/request IDs, time, platform and a short reproduction. Keep keys and private conversation content out of notes. Owners and Admins configure user destinations under Settings → Support. Ask us about response times and any SLA.