AI Chat Assistant
Give users a conversation that answers questions and helps them finish work in the app.
What it adds
A persistent chat surface with streamed responses, stored conversation history, and a defined set of actions it may take on the user's behalf.
What your agent is told to do
5
What your agent is told to do
5-
1
Store conversations as records owned by a user and a workspace, and load every message through the same authorization path the rest of the app uses. Do not trust a conversation identifier supplied by the client as proof of access.
-
2
Stream tokens to the interface as they arrive, but persist a message only once the generation finishes cleanly. A stream that is cancelled, truncated, or errored must be marked incomplete rather than saved as an answer.
-
3
Set a token ceiling and a wall-clock timeout for every request, and trim old turns from the context with a summary of what was dropped rather than sending the entire history each time.
-
4
If the assistant can perform actions, let it only propose them and require the user to confirm before anything is written. Report success from the result of the action, never from what the model said it did.
-
5
Page-specific context — the record being viewed, the current route, the actions available on that screen — is owned by Contextual Page Copilot. This feature owns the conversation, its storage, and its streaming; do not build a second context assembler here.
Edge cases it handles
8
Edge cases it handles
8- Every conversation and message must be scoped to one user and one workspace. A user who switches workspaces must not see the previous workspace's threads, and an identifier guessed or replayed from another account must resolve to nothing.
- A partial stream is not an answer. If the connection drops mid-generation or the user navigates away, the interface must show the turn as unfinished and offer to retry rather than leaving a half sentence in the transcript.
- Timeouts, provider errors, safety refusals, and user cancellation are four different outcomes and need four different messages. A refusal is not a bug and must not be retried automatically.
- Long conversations grow expensive and lose relevance. Cap the context window, and make the trimming visible enough that the user understands why the assistant no longer remembers something from an hour ago.
- The assistant must never claim an action succeeded unless the app confirmed it. If the confirmation call fails after the model announced the result, correct the transcript rather than leaving the false claim in place.
- The provider being unavailable must degrade the feature, not the page. The chat surface shows an unavailable state and the rest of the app keeps working.
- Enforce a per-user and per-workspace spend or request ceiling, and tell the user plainly when they have reached it instead of failing with a generic error.
- Pasted content the user does not realise is sensitive still leaves the app. State in the interface what is sent to the provider, and exclude fields the workspace has marked restricted.
Definition of done
8
Definition of done
8- Conversations and messages are readable only by the owning user within the owning workspace.
- Cancelled, timed-out, and truncated generations are stored as incomplete and are never presented as finished answers.
- Every request carries a token ceiling and a timeout, and context is trimmed rather than allowed to grow without bound.
- Actions are proposed for approval, and reported outcomes come from the app rather than from the model's own claim.
- Refusals, provider outages, and rate limits each produce a distinct, non-technical message.
- The app remains fully usable when the model is unavailable.
- 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 Chat Attachments
AI Chat Attachments
Attach files to a conversation and let the assistant use what it is allowed to read.
What it does
File upload on an AI conversation, with parsing, retrieval of relevant sections, and per-conversation access scoping.
How it works
- 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.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/ai-chat-attachments
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
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.