Watch an Item
Follow one record and get told when something changes on it.
What it adds
Per-record change subscriptions, with automatic watching when a user comments or is assigned, and one-click unwatch.
What your agent is told to do
5
What your agent is told to do
5-
1
Add a watch subscription joining a user to a single record, with a control on the record itself showing current state and the watcher count.
-
2
Auto-watch a user when they comment on, are assigned to, or create a record — then tell them you did it, and make the unwatch obvious.
-
3
Define the exact list of events that notify watchers, and let a watcher mute event types they do not care about while staying subscribed.
-
4
Put an unwatch action inside every notification the subscription generates, so the user can stop it at the moment it annoys them rather than hunting for the record.
-
5
Do NOT reuse or duplicate Favorites. Favorites is a personal bookmark for finding things again; a watch is a subscription that sends messages. Keep them as separate state with separate controls.
Edge cases it handles
6
Edge cases it handles
6- One user action that fires several internal events must produce one notification, not four.
- A user must never be notified about their own change to a record they watch.
- Losing access to the record must stop delivery immediately, including for anything already queued.
- Deleting, archiving, or merging a record needs a defined outcome for its watchers — silently dropping them loses the notification they were waiting for.
- Watch state belongs to a workspace. The same user in two workspaces must not leak subscriptions between them.
- A record with many watchers must fan out asynchronously; do not send during the request that made the change.
Definition of done
8
Definition of done
8- Any record can be watched and unwatched, with the current state visible on the record.
- Commenting on or being assigned to a record starts a watch and tells the user.
- Watchers can mute specific event types without unwatching.
- Every generated notification carries a working unwatch action.
- Users are not notified about their own changes and duplicate events collapse into one.
- Revoked access stops delivery immediately, including queued messages.
- 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.