Our own support: bug reports first, then chat
Customers report a bug with a marked-up screenshot, or ask the AI assistant, which answers from the help centre. Everything real lands in Slack, where Hermes investigates and Zare or Luka fix and reply. Replies reach the customer in the widget, or by email.
Bug report states 1 to 7 (menu, form, annotate, submitted, needs info, fixing, fixed) and question states a to h. Light, dark, mobile, restylable.
#dotsy-support: the bug report card and Hermes's thread (reproduced, verdict, drafted reply, fix shipped), a chat escalation, a knowledge gap and the daily digest.
Both flows in plain words, the help-centre loop for SEO and AI search, and the ground rules.
Their visitors' reports in their dashboard, and their AI agent reading and answering them over MCP.
Notes
- Mockups only. Self-contained HTML, no network requests. Screenshots live in
png/. - Widget states have deep links:
widget.html?state=4(bug) or?state=e(question),&visitor=anon,&theme=dark,&instant=1. - Restyle: the widget reads only
--dw-*CSS variables, so a customer site can re-skin it without touching markup.