AI Chat Attachments
Attach files to a conversation and let the assistant use what it is allowed to read.
What it adds
File upload on an AI conversation, with parsing, retrieval of relevant sections, and per-conversation access scoping.
What your agent is told to do
5
What your agent is told to do
5-
1
Reuse the app's existing upload, storage, and virus-scanning path rather than adding a second one, and declare an explicit list of accepted file types and a size ceiling per file and per conversation.
-
2
Parse each attachment into text and structure in a background job, store the result, and show the attachment as pending until parsing succeeds so the user is never told the assistant has read something it has not.
-
3
Retrieve and send only the sections relevant to the current question. Sending whole documents on every turn burns the context window and the budget for no gain.
-
4
Scope attachment access to the conversation and the workspace it belongs to, and re-check that scope on every read, including when an older turn is regenerated.
-
5
Tell the user which attachments and which sections informed each answer, using the app's existing citation surface. This entry owns upload, storage, parsing, scoping, and retrieval; hand image files to Multimodal Image Analysis rather than interpreting them here.
Edge cases it handles
8
Edge cases it handles
8- Accepted types and size limits must be enforced on the server against the real content, not the declared extension, and every upload must pass the app's scanning step before it is readable.
- A file readable in one conversation must not become readable in another, and a user removed from the workspace must lose access immediately, including to answers being regenerated from older turns.
- An answer that does not say which files it used cannot be checked. Cite the specific attachments and sections, and say plainly when none were used.
- Sending whole files on every turn is the tempting shortcut and the wrong one: it exhausts the context window, raises cost per message, and buries the relevant passage. Retrieve the relevant sections instead.
- An attachment deleted, replaced, or failed to parse must degrade the answer honestly. Say the file is unavailable rather than answering from a stale copy or silently ignoring it.
- Encrypted, corrupt, or image-only documents will fail to yield text. Report the specific reason so the user can act, rather than a generic upload error.
- Retention must be defined: how long parsed text and derived indexes live, and whether deleting the attachment removes them too.
- A very large document must be refused with a clear limit rather than accepted and then truncated invisibly mid-way through parsing.
Definition of done
9
Definition of done
9- Uploads reuse the app's existing storage and scanning path, and type and size limits are enforced server-side against real content.
- Parsing runs in the background and attachments are marked pending until they are genuinely readable.
- Only relevant sections are retrieved and sent to the model, not entire files on every turn.
- Attachment access is scoped to the conversation and workspace and re-checked on every read, including regenerations.
- Answers cite which attachments and sections were used, and state when none were.
- Deleted, replaced, and unparseable attachments produce an explicit message rather than a silently degraded answer.
- Retention of parsed text and derived indexes is defined and tied to deletion of the attachment.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
AI Support Triage
AI Support Triage
Summarise each incoming support request and estimate how urgent it really is.
What it does
An automatic summary, urgency estimate, and likely problem area attached to every inbound support request, with the evidence behind each.
How it works
- 1 Run triage as a background job on arrival, using the app's existing queue and retry behaviour. The ticket must be visible and workable in its raw form the moment it lands, whether or not triage has finished.
- 2 Produce three separate outputs — a short summary, an urgency level, and a likely problem area — and store each with the quoted source statements from the ticket that support it, so a human can check the reasoning.
- 3 Define urgency in terms of business impact: who is blocked, how many, whether money or data is at risk. Compute it from what the ticket describes, not from how the writer sounds.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/ai-support-triage
AI Suggested Support Answers
AI Suggested Support Answers
Give support agents a grounded first draft instead of a blank reply box.
What it does
A draft reply composed for the agent from the ticket, the customer's account state, and the approved internal knowledge, with sources attached and no ability to send itself.
How it works
- 1 Ground every draft in retrieved material: the ticket thread, the account's real state, and articles from the approved knowledge set. Attach the sources used to the draft so the agent can open and check each one.
- 2 Load the draft into the agent's normal reply editor, unsent and fully editable. There is no path in this feature that sends a message to a customer without an agent pressing send.
- 3 Define the commitments the app is not allowed to make in a draft — refunds, credits, delivery dates, guarantees of a fix — and strip or refuse any draft containing them, leaving that part for the agent to write.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/ai-suggested-support-answers
AI Ticket Routing
AI Ticket Routing
Send each support request to the queue that can actually resolve it.
What it does
Automatic assignment of an inbound support request to one of the currently configured queues, teams, or specialists, with a recorded reason and a fallback.
How it works
- 1 Read the destination list from the app's live configuration at the moment of routing, and constrain the decision to that set. A destination that is disabled, deleted, or out of hours is not a valid choice.
- 2 Pass the current ownership rules and destination descriptions in with each request rather than relying on anything the model may have absorbed earlier, so a change to team ownership takes effect on the next ticket.
- 3 Record the chosen destination, the confidence, and a one-line reason on the ticket, and give agents a reassign control that logs the correction alongside the original decision.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/ai-ticket-routing
How it works
-
1
Copy the link
Grab the Markdown instruction URL for this feature.
-
2
Give it to your AI
Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.
-
3
It inspects, then implements
Your agent reads your existing app first, then adds the feature to fit it.
Works with your stack
These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.
Need it tighter than that? Customize the feature and tell it exactly what you're running.