The chat widget — The third door into a table

A form takes a submission and stops. An email address takes a message and can carry on. The widget is the third way in and is deliberately the same shape as both: an unguessable token is the address, the table it files into is fixed when the view is created, and it starts switched off so minting one never silently opens an anonymous write endpoint on somebody's data. What makes it different is that the conversation keeps going. One chat is one record, and that record's thread holds the chat, any email about it, and your team's internal notes together.