“The developer install is complete when a real visitor message reaches the inbox and every downstream automation is signed, logged, and reversible.”
Developers
Ship the support install with a clear path from snippet to production
Install Ochre live chat, verify signed webhooks, connect BYOK model keys, and run integration QA without expanding the security boundary or turning launch into a platform project.
Install path
Snippet
Embed one workspace snippet, allow the production domain, and confirm a test visitor reaches the shared inbox.
Trust boundary
Signed
Verify webhook signatures, separate environment secrets, and keep API keys scoped to the automation they power.
Production readiness checklist
Developer launch path
Production readiness checklist
Developer launch path
HANDL.
3
RESOL.
14
AVG C.
99%
SPEND
$0.19
Install check
nowWidget install verified
Install check / #TKT-c_58babc0a02
Subject Widget install verified · Channel API
Can we confirm the widget, webhooks, and API key are working?
Widget loaded, API key scoped, webhook test delivered, and BYOK key available.
ok conversation.opened 202
ok signature verified
ok event replay safe
Operating model
Scroll through the actual operating path.
Each card locks into place as you move down the page, updating the product scene above and keeping the current workflow step in focus.
Proof points
Built from the work support actually does.
“Support should be able to tune the widget and review AI, while engineering keeps ownership of secrets, signatures, and production boundaries.”
Start with one clear support path, then add the depth your team needs.
Ochre keeps the workflow concrete: one inbox, one customer story, one visible AI review path, and a practical route into the rest of the platform.