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
Prize Wheel Giveaway
Prize Wheel Giveaway
Run a spin-the-wheel giveaway where each entrant gets one spin and a recorded prize.
What it does
A giveaway with a wheel interface, one server-decided spin per entrant, and a durable record of every result.
How it works
- 1 Decide the outcome on the server before the wheel starts turning. The request returns a prize, the animation lands on it, and the client is only ever playing back a result it was given.
- 2 Model prizes with explicit weights and optional stock counts, and let an operator edit them without a deploy. A giveaway whose odds live in code cannot be corrected once it is live.
- 3 Tie an entry to an account where the app has one, and where it does not, combine the strongest identifiers available and treat a single spin as the hard limit across all of them.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/prize-wheel-giveaway
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
Quiet Hours
Quiet Hours
Hold non-urgent notifications until the user actually wants to hear from you.
What it does
A per-user window during which outbound notifications are suppressed, with an explicit rule for what happens to anything that arrives inside it.
How it works
- 1 Extend the existing notification pipeline with a suppression check at send time. Do not build a second notification system.
- 2 Let the user set a start and end time and store the time zone the window was defined in.
- 3 Decide per notification type whether it is deferred to the end of the window, dropped entirely, or allowed through as urgent — and record that decision in the notification's definition, not in scattered call sites.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/quiet-hours
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.