Where it is: Design → Widgets → Attachments. Off by default.
With it on, the composer grows a paperclip and visitors can attach a file to a message. It is a support feature: the point of it is the screenshot of the error, or the PDF of the quote, that a person needs to see.
What each setting does
| Setting | What it does | Default |
|---|---|---|
| Attachments | The on/off switch on the card. | Off |
| Maximum file size | Per file, from 1 to 10 MB. Enforced on the server as well as in the widget. | 5 MB |
What can be sent
Images (JPG, PNG, GIF, WebP) and PDF, and nothing else. The list is fixed and deliberately not a setting — a public upload form is no place for a configurable file-type list. Files are checked by their real content, not by their name or the type the browser claims.
The AI does not read the file
A message that is only an attachment gets a short acknowledgement and an offer to fetch a human. Attachments are for your agents: they appear inline in the transcript in the inbox.
Where files go, and when they leave
- Into
uploads/chatflint-attachments/, under a name derived from the chat session rather than from the visitor’s own filename. - They count as visitor data: an approved erasure request deletes them, and so does the retention sweep when the conversation ages out.
- Uploads are capped per visitor — ten per chat session and thirty per IP address an hour — so the feature cannot be turned into a way to fill your disk.