Support attachments need controlled upload, processing, access, and retention paths. Treat extracted content as untrusted evidence and avoid letting a document or image redefine the assistant’s authority.
Attachment handling has several boundaries
An attachment enters storage, may pass through scanning or parsing, becomes evidence for a support task, and can be viewed or downloaded by staff. Each stage needs a defined scope and failure policy.
OWASP’s file-upload guidance covers layered validation, storage, permissions, and limits. Apply controls appropriate to the supported formats rather than trusting the filename extension or browser-supplied content type alone.
For a proposed intake, define allowed formats, size and count limits, processing isolation, safe filenames, access rules, and retention owner. Preserve a stable attachment reference without copying unrestricted content into every ticket event.
Test a fictional diagnostic screenshot
A customer uploads a screenshot of an export error. It also contains personal information in another window. The support workflow should use the relevant error evidence and avoid broad redistribution of the whole image when a minimised summary suffices.
A second attachment contains instructions telling the AI to export account records. Parsing the document should not grant those instructions authority. The execution service still enforces trusted account and action scope.
| Attachment fixture | Required handling |
|---|---|
| Supported valid file | Protected storage and scoped processing |
| Mismatched type declaration | Validation according to the approved policy |
| Oversized or excessive upload | Controlled rejection without resource exhaustion |
| Restricted customer content | Role-appropriate access |
| Embedded behavioural instruction | Evidence stays separate from execution policy |
Use safe synthetic files and isolated parsers for tests. Do not introduce live malicious material merely to make a demonstration appear realistic.
Explain processing limits to staff
A parser failure should not become an invented summary. Mark the artifact unreadable or partially processed and offer the supported review route. If only some pages were extracted, preserve that limit with the generated claims.
More accepted formats increase convenience and operational complexity. Start with the formats actually needed for the pilot and a tested failure path. Review downstream exports, notifications, and deletion so attachments do not become forgotten copies outside the ticket’s main controls.
This attachment design is proposed. The voice integration case study describes related backend work without claiming this support upload pipeline. Pair it with hostile support instruction tests.
Support attachment FAQ
Is a PDF extension proof that the file is safe?
No. Apply the approved layered validation and processing controls.
Can extracted text be trusted as system policy?
No. It remains untrusted task evidence unless independently established as an approved authority for the question.
What should happen after partial extraction?
State the processing limit and avoid claims about content the workflow did not actually inspect.