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
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.