Reminder Scheduling
Let users ask the app to bring something back to their attention later.
What it adds
A reminder a user sets on a specific record, delivered at a chosen time through the notification channels the app already has.
What your agent is told to do
5
What your agent is told to do
5-
1
Add a reminder action to the records users actually revisit, and store each reminder against both the user and the record.
-
2
Offer quick presets (tomorrow morning, next week) alongside an exact date and time.
-
3
Schedule against the user's time zone and show the resolved absolute time back to them before saving, so there is no ambiguity about what they picked.
-
4
Deliver through the existing notification center rather than adding a new inbox.
-
5
Do NOT fire a reminder without re-checking that the user can still see the record. Access changes between scheduling and delivery, and a reminder is a leak vector.
Edge cases it handles
6
Edge cases it handles
6- Deleting, archiving, or completing the record must cancel its pending reminders.
- Saving the same reminder twice, or a retried job, must not produce two deliveries — key the schedule so it is idempotent.
- A reminder set for a time already in the past should be rejected at the form, not silently fired immediately.
- If the user changes time zone after scheduling, decide and document whether the reminder moves with them or stays at the original instant.
- A failed delivery (bounced email, revoked push permission) must be visible to the user, not silently discarded.
- Reminders on a record the user has lost access to are cancelled, not delivered with the title redacted.
Definition of done
8
Definition of done
8- Users can set, edit, and cancel a reminder on a record.
- The resolved delivery time is shown before saving, in the user's time zone.
- Deleting or completing the record cancels its reminders.
- Duplicate saves and job retries produce exactly one delivery.
- Access is re-checked at delivery time.
- Delivery failures are surfaced to the user.
- 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.