Go-live

Checklist before partner embed traffic. Platform engineers keep detailed matrices in the repo under Chat-bot/docs/rollout/; this page is the public partner view.

Ops

  • GET /api/healthdb and redis are ok (otherwise 503).
  • TENANT_SECRET set on Mimmo (≥32 chars).
  • Production uses prisma migrate deploy (not destructive db push).
  • Partner BOT_TENANT_TOKEN from ChatAdmin only — no hardcoded fallbacks.

Per system (ChatAdmin)

For each of TRAVELMATIC, SimpleCRS, DotRed, TravelPlus (as needed):

  • Tenant active + valid widget token
  • System row with exact systemName partners will send
  • Companies / scopes; companyCode as string
  • Knowledge uploaded or explicit “identity-only” sign-off
  • Channel toggles match intent
  • One UCT test user with mail/mobile filled for channel tests

Web UAT (TravelMatic + SimpleCRS first)

  • Authenticated mint + widget
  • Anonymous mint without userCode
  • No cross-system knowledge leak
  • Host gates on userCode; company passed as string

Links for Mimmo engineers

  • In-repo rollout index: Chat-bot/docs/rollout/README.md
  • Identity acceptance cases: Chat-bot/docs/MIMMO_IDENTITY_REQUIREMENTS_CLARIFICATION.md
  • PHP deep dive (repo): Chat-bot/PARTNER_INTEGRATION_GUIDE.md — public surface is this /docs site

Stuck on mint? Start at Quickstart or Errors.