- Shipped
- September 6, 2026 at 12:21 AM UTC
- Author
- Kamo
- Commit
- 8520ff0
A web-chat integration had no support topic. The visitor's browser sent a hardcoded topic title instead, so an org whose topics aren't named "General Inquiry" — nearly all of them — had every website chat filed under whichever topic happened to sort first, with nothing in the settings UI even hinting at the choice. Adds **************** (nullable) and surfaces it on the DTO. A plain org-scoped id rather than a relation, matching SALES_AGENT_ID next to it: ownership is enforced at the write, not by an FK. Nullable so the seven existing integrations keep exactly today's behavior until someone picks one. findByIdAndOrganizationId is that write-time check — an unchecked id would let one org file its chats into another org's queue.