Coach — act feedback + signal periods
Closes the Coach's feedback loop: 'I acted on this' on every insight (the engine learns which advice lands) alongside Dismiss, and the signal view gets a working 7d/30d/90d period selector over the live signals endpoint instead of a fixed 30-day pill.
If you are building a front end
Your front end calls this over the same-origin `/api/v1` proxy — no backend code to write, no schema to design. Endpoints: POST /api/v1/coach/insights/:id/act, GET /api/v1/coach/signals?period=7d|30d|90d.
Bring any front end — hand-written, or generated with Lovable, v0, Bolt, Claude, or Cursor. You get auth, a multi-tenant database, payments through your own Stripe, and email/SMS without writing or hosting a backend.
- How to turn it on
- Part of the 'ai-insight' module.
- Who can use it
- RBAC: ai_insight.insights.read / ai_insight.insights.write.
- The API behind it
POST /api/v1/coach/insights/:id/act, GET /api/v1/coach/signals?period=7d|30d|90d- Where it lives
- /ai-insight
See it in context
AI Coach & deep insights — the full walkthrough, step by step: An AI that reads YOUR live business — flags risks, answers questions, suggests moves.
Machine-readable
This page is generated from our published capability catalog. Point your AI assistant at /features.json (or /llms.txt) and it can read every feature, how to enable it, and the endpoints behind it — then build against them.