Skip to main content

Customer handoff

Handoff is when your client takes day-to-day ownership of their branded workspace. Define what they control and what you retain as operator.

Before handoff

ItemOperator action
BrandProduct name, logo, support email verified on client URL
DomainDNS verified; canonical host set if using custom domain
KeysClient BYOK keys in vault, or documented key rotation plan
PacksVertical bundles installed and tested with sample prompts
UsersClient owner account created; your test accounts removed or demoted
BillingClient knows who invoices them (you vs platform)

Handoff checklist (client-facing)

Send your client this list:

  1. Sign in at your branded URL (not app.carinaai.uk if you use a custom domain).
  2. Add API keys under Settings if they own model spend (BYOK).
  3. Open Skill packs and confirm the vertical bundle you sold is enabled.
  4. Start chat with a realistic task from their industry.
  5. Bookmark your support email from the login footer or brand settings.

Support boundaries

TopicClient contactsOperator handles
Forgot passwordYour support or app reset flowAuth config
Model errors / quotaTheir provider dashboardKey hints only, not raw keys
Wrong brand on loginYouDNS, brand JSON, cache
Agent quality / packsYou firstPack install, prompts
Platform outageYou escalate to CarinaVERLOX hosted status
Scout security alertsYou or client per contractScout console pairing

What clients should not expect

  • Direct access to core.carinaai.uk unless you explicitly grant operator training
  • Kernel source changes without a change request to you
  • Shared sender email with other tenants on hosted cloud

Documentation to share

Point clients to your branded docs build or these user guides:

Hide internal runbooks (deploy scripts, ops tokens, docker compose paths).

After handoff

  • Schedule a 30-day check-in for usage and pack fit.
  • Review audit log if the client has compliance requirements.
  • Keep OPS_DOCKER_PROJECTS scoped if you host multiple brands on one VPS.