feat(webchat): customizable CSAT rating in chat widget

[rgrjnr]

Summary

Adds a Customer Satisfaction (CSAT) rating to the webchat widget. When a conversation ends, visitors are shown a 1–5 emoji scale under a prompt that defaults to "How would you rate the support you received today?". Both the prompt text and an enable/disable toggle are configurable per‑organization from the dashboard webchat settings page.

What changed

Backend

• webchat_settings: new csat_enabled (bool, default true) and csat_question (text, default copy) columns.
• conversations: new csat_rating (smallint, nullable) and csat_rated_at (timestamptz, nullable) columns — one rating per conversation, no new table.
• Migration 1781300000000-AddCsatToWebchat.
• publicConversations.submitCsat mutation — DPoP‑verified like sendMessage, with NONCE_EXPIRED retry support.
• webchat.getPublicConfig now returns the CSAT config; getMessages returns the existing csatRating.
• webchat.updateSettings accepts the new fields.

Widget

• New CsatRating.vue (emoji scale + thank‑you state), rendered in the existing closed‑conversation footer when CSAT is enabled.
• useChat.submitCsat posts the rating via DPoP; already‑rated conversations restore the thank‑you state on load/refresh.
• CSAT strings (csat.defaultQuestion, csat.thankYou) added across all 13 widget locales.

Dashboard

• New "Customer Satisfaction (CSAT)" card on the webchat settings page (enable toggle + question textarea), wired through load/save.
• en and pt-BR settings strings.

How it works

The rating is shown only when the conversation is closed/resolved (reusing existing closure detection) and CSAT is enabled. The default question lives in the DB and is served to the widget via the public config endpoint, so changes in settings take effect without re‑embedding.

Verification

• npm run typecheck:server — ✅ pass
• npm run typecheck:dashboard — ✅ pass (exit 0)
• webchat build — ✅ pass; typecheck clean (only the pre‑existing, unrelated fake-indexeddb test‑setup error remains)

Note

A DB migration is included — run npm run migration:run before deploying.

🤖 Generated with Claude Code

---

Generated by Claude Code

[rgrjnr]

Status check (2026-07-14 branch audit): Feature is complete and coherent (~550 insertions across 29 files: CsatRating.vue, conversation entity + migration 1781300000000-AddCsatToWebchat, public-conversations endpoints, dashboard settings, 13 locales). Zero trace of CSAT in master — not superseded, just parked since 2026-06-17.

Next steps:

• Rebase onto current master (customer-identity and conversation-view changes landed since)
• Verify the migration timestamp still sorts after the latest master migrations
• Review + un-draft, or close if CSAT is off the roadmap