Email Preference Center
Let people choose which emails they get without cutting off account-critical mail.
What it adds
A preference page covering delivery channels and message categories, with unsubscribe links that work without signing in.
What your agent is told to do
5
What your agent is told to do
5-
1
Extend the existing notification preference model rather than forking a second one — this feature adds channels and consent on top of the per-type preferences already there, and two competing sources of truth will drift.
-
2
Split messages into required transactional, optional product notifications, and marketing. Only the last two may be switched off, and the page must say plainly which mail keeps arriving regardless.
-
3
Give every optional email a one-click unsubscribe link that is signed, works with no session, and needs no confirmation step.
-
4
Send List-Unsubscribe and List-Unsubscribe-Post headers on optional mail so mailbox providers can honour a single click, and process those requests the same way as the link.
-
5
Do NOT build the digest schedule here. This owns whether and how a message is delivered; frequency and batching belong to Notification Digests.
Edge cases it handles
6
Edge cases it handles
6- Messages already queued when someone opts out must be re-checked against preferences at send time, not at enqueue time.
- An unsubscribe link that is forwarded still works. Scope its token to one recipient and one category so it cannot mute someone else's mail.
- Turning off every optional channel must not silently disable password resets, receipts, or security alerts.
- Users in more than one workspace need per-workspace settings plus a global off switch, and the global one wins.
- Record consent changes with a timestamp, source, and IP where regulations require proof.
- The preference page must render correctly for a signed-out visitor arriving from an email link.
Definition of done
8
Definition of done
8- Preferences extend the existing notification preference model rather than a parallel one.
- Required transactional mail is clearly separated and cannot be disabled.
- Every optional email has a signed one-click unsubscribe that works without a session.
- List-Unsubscribe headers are sent and honoured identically to the link.
- Preferences are evaluated at send time, so queued mail respects a recent opt-out.
- Consent changes are recorded with timestamp and source.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Poll Widget
Poll Widget
Ask a one-question poll anywhere in the app and show the results as soon as someone votes.
What it does
An embeddable single-question poll with a vote control and a results view revealed after voting.
How it works
- 1 Keep it to one question with a small set of options. The moment it grows a second question it is a survey and belongs in the survey feature instead.
- 2 Record the vote on the server and return the updated tallies in the same response, so the results the voter sees are the real counts rather than an optimistic local guess that may disagree after a refresh.
- 3 Hold voting open to signed-out visitors if the poll is public, and identify them well enough to prevent casual repeat voting without demanding an account for a single click.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/poll-widget
Discussion Forum
Discussion Forum
Give users a public place to ask questions and answer each other.
What it does
Topic boards containing user-created threads with replies, moderation controls, and permalinks.
How it works
- 1 Ship boards, threads, replies, and a single level of nesting. Resist arbitrary-depth reply trees, reputation scores, badges, and private subforums until people are actually posting; each of those is a feature in its own right.
- 2 Reuse Comments and Mentions for the reply composer, mention parsing, and content rendering rather than writing a second editor with its own escaping rules.
- 3 Route reported and held posts into the existing Moderation Queue and reuse AI Text Content Moderation and Content Reporting if present. Do not build a forum-specific moderation inbox alongside the one the app already has.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/discussion-forum
Live Chat Widget
Live Chat Widget
Let visitors ask a question from any page and get a real answer from your team.
What it does
A corner chat bubble that opens a persistent conversation between a visitor and staffed agents, with an agent-side inbox.
How it works
- 1 Build the visitor side first: a bubble, a transcript, a composer, and a clear statement of whether anyone is currently available. An agent inbox that reuses the app's existing list and detail patterns is enough for version one; do not build a full helpdesk with routing rules, tags, and SLAs before a single conversation has happened.
- 2 Keep the conversation attached to the visitor, not the page. Store a conversation identifier that survives navigation, reload, and moving between pages, and reattach the transcript when the widget reopens.
- 3 If the app already has Knowledge Base Chat or an AI Chat Assistant, put them in the same widget rather than adding a second bubble. Answer from the knowledge base first and hand off to a human when the visitor asks or the answer is not found.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/live-chat-widget
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.