- Shipped
- October 4, 2026 at 6:06 PM UTC
- Author
- Kamo
- Commit
- 051bd4d
POST /api/media/public-chat/contact, reached through the gateway's site-key gate like every other public-chat call, so the key names the org and its allowed origins name the website. The platform's own contact form could not do this: it files into the platform org, whatever site posted it. A contact form is a chat opened and typed into once, so it is built from exactly those two steps: createSupportSession (the integration's topic, attribution, geo, the topic's assignment strategy after commit) and sendSupportMessage (the visitor's first message). Only the title and description differ, and both lead with a card of name, email and phone, because the visitor has left the page and email is the way back to them. The queue is told once the message is in the thread, as with the AI handoff. A filled honeypot answers success and files nothing.