Raised automatically when a conversation involves thoughts of suicide or self-harm, harassment, discrimination, violence, abuse or a serious legal matter. High and medium flags are also emailed to every administrator. People are told in the app that administrators are notified of safety concerns.
What people see at /support: your organisation's contacts, emergency guidance, useful links and FAQs. Edit the JSON and save. Fields: title, intro, emergency, contacts and links (each label, detail, value, url) and faqs (q, a).
What people read at /privacy and /terms. The default text is a plain-language starting point: have your legal and privacy teams review it, edit the JSON, then set "reviewed": true to remove the draft banner. Use {org} and {coach} as placeholders. Each document has title, intro and sections (each with h and p and/or ul).
Add people who may sign in. You can invite anyone, from any email domain, including people outside your own company: the allowed-domain rule only limits self sign-up. Admins can manage webhooks and the knowledge library.
| Name | Role | Last sign-in | Welcome | Status |
|---|
Events are POSTed as JSON and signed with the Standard Webhooks scheme
(webhook-id, webhook-timestamp, webhook-signature). Failed deliveries are retried with backoff.
| Endpoint | Events | Last delivery | Status |
|---|
Let a Slack or Teams bot, WhatsApp bridge, n8n/Zapier flow or another system hold a coaching conversation on a user's behalf.
| Name | Key | Created | Last used |
|---|
Evidence the coach draws on: an Amazon Bedrock Managed Knowledge Base over the S3 library. Add files to knowledge/library/<topic>/ and run
scripts/kb_sync.py, or upload straight to the bucket's library/ prefix (sync starts automatically).
| Source | Type | Licence | Topics |
|---|