AI Onboarding Concierge
Answer setup questions and point new users at the next step that actually matters.
What it adds
A guided setup assistant that reads the account's real completion state, answers questions about the product, and links the user into the interface where each remaining step is done.
What your agent is told to do
5
What your agent is told to do
5-
1
Find the existing source of truth for setup progress — the onboarding checklist, activation flags, or whatever the app already uses — and read from it. Do not have the assistant infer completion from conversation history.
-
2
Filter candidate next steps by the user's plan and role before anything is suggested, so the assistant never recommends an action the account cannot take or the person is not permitted to perform.
-
3
Make every recommendation end in a link or control that opens the real screen for that step. The assistant explains and directs; the app's own interface does the work.
-
4
Recompute progress from the app after the user returns, and only then acknowledge a step as done. Confirm nothing on the strength of the user having said they did it.
-
5
Do not let the assistant become the only path through setup. The existing onboarding checklist and empty states remain fully usable with the assistant closed, and this brief extends them rather than replacing them.
Edge cases it handles
8
Edge cases it handles
8- A user who completed a step in another tab, or before the assistant opened, must not be told to do it again. Refresh the completion state on every turn, not once per session.
- When the assistant cannot answer with confidence, it must say so and hand off to the app's normal help — documentation, support, or a human — rather than producing a plausible-sounding invented instruction.
- Recommending an upgrade-only or admin-only action to someone who cannot take it turns setup into a dead end. Restrict the candidate set up front instead of apologising afterwards.
- Claiming setup succeeded when the app's state says otherwise destroys trust in everything else the assistant says. Verified state always wins over the model's account of what happened.
- Trapping the user in a chat window when a two-field form would finish the job is worse than no assistant. Prefer sending them to the interface over collecting values conversationally.
- When the model is unavailable, the assistant must degrade to the static checklist and documentation links rather than showing an error that blocks onboarding.
- The account context sent to the provider must be limited to setup state and plan level. Customer records, uploaded content, and credentials never leave the app as part of an onboarding question.
- A long back-and-forth must have a token and turn ceiling per session, after which the assistant summarises and hands off rather than growing the conversation indefinitely.
Definition of done
9
Definition of done
9- Setup progress is read from the app's own completion state and refreshed on every turn.
- Recommended actions are filtered by the user's plan and role before being offered.
- Each recommendation links into the real interface where the step is completed.
- A step is only reported complete after the app verifies it.
- Low confidence produces an explicit handoff to normal help rather than a guess.
- The existing onboarding checklist remains fully usable when the assistant is closed or the model is unavailable.
- Per-session token and turn ceilings are enforced.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
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
AI Conversation Branching
AI Conversation Branching
Explore an alternate path from an earlier message without losing the original.
What it does
A message graph that lets a conversation fork at any point, with each branch keeping its own history and active state.
How it works
- 1 Change the conversation's storage from an ordered list to a graph where every message names its parent, and migrate existing conversations into that shape as single-path graphs.
- 2 Define the active branch as a stored pointer to a leaf message, and derive everything rendered from the path between the root and that pointer.
- 3 Give each branch its own summary, memory, and derived context. Carrying one summary across siblings leaks the abandoned path back into the new one.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/ai-conversation-branching
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.