Quiet Hours
Hold non-urgent notifications until the user actually wants to hear from you.
What it adds
A per-user window during which outbound notifications are suppressed, with an explicit rule for what happens to anything that arrives inside it.
What your agent is told to do
5
What your agent is told to do
5-
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.
-
4
Deliver deferred messages as a single digest when the window ends, not as a burst of twenty separate pushes.
-
5
Do NOT let quiet hours suppress security messages — password changes, new sign-ins, billing failures. A user who cannot be reached about account compromise is worse off than one who was woken up.
Edge cases it handles
6
Edge cases it handles
6- Evaluate the window against the user's current time zone, not the server's and not the one they signed up in.
- A window that crosses midnight (22:00 to 07:00) is the common case, not the exception. Handle it first.
- Daylight-saving shifts can make a window an hour shorter or longer, and can make a deferred send time occur twice or not at all.
- A deferred notification about a record that was since deleted or resolved must be dropped, not delivered stale.
- Ten deferred notifications about the same record must collapse into one on release.
- Turning quiet hours off mid-window should release the queue immediately, not wait for the original end time.
Definition of done
8
Definition of done
8- Non-urgent notifications sent inside the window are not delivered during it.
- Windows crossing midnight behave correctly.
- The window is evaluated in the user's current time zone and survives daylight-saving changes.
- Each notification type has a declared behaviour: defer, drop, or bypass.
- Deferred messages arrive as one digest, with stale entries removed.
- Security and billing notifications always bypass the window.
- 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.