Poll Widget
Ask a one-question poll anywhere in the app and show the results as soon as someone votes.
What it adds
An embeddable single-question poll with a vote control and a results view revealed after voting.
What your agent is told to do
5
What your agent is told to do
5-
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.
-
4
Show the total response count next to the percentages. A split of sixty and forty means something very different across ten votes and ten thousand.
-
5
Do not let a vote be silently changeable. Either allow a vote to be changed and say so plainly with the previous choice shown, or lock it after submission, but do not let a second click quietly move the count.
Edge cases it handles
8
Edge cases it handles
8- Preventing repeat votes without an account means combining signals such as a persistent cookie and coarse network identification, and accepting that neither is authoritative. Apply the app's existing Rate Limiting per poll so a determined script cannot flood the tallies.
- A poll can close between the moment the page rendered and the moment the vote arrives. Reject the late vote on the server, tell the voter the poll has closed, and show them the final results rather than pretending the vote counted.
- Showing the current results before someone votes anchors their answer toward the leading option. Keep results hidden until a vote is cast or the poll closes, and make that behaviour visible so it does not read as a bug.
- Rounded percentages frequently sum to ninety-nine or a hundred and one. Use a rounding approach that forces the displayed figures to total one hundred, and show raw counts alongside so the arithmetic can be checked.
- Adding an option after voting has started makes earlier results incomparable, because nobody who voted first was offered the new choice. Either forbid it once the first vote lands, or record when each option was added and mark the results as affected.
- A poll with zero votes must render its options and an honest empty state, not percentages derived from a division by zero.
- Results are usually drawn as bars. Give every option its percentage and count as text so the outcome is readable without seeing the bars, and do not rely on colour alone to mark the option the viewer chose.
- A poll is written by one person and rendered to everyone who loads the page, which makes the question and its options a publishing surface rather than a form input. Screen them when the poll is saved and escape them when it renders, or an embedded poll becomes a way to put arbitrary markup in front of every visitor.
Definition of done
9
Definition of done
9- A visitor votes once and sees results immediately, with counts computed on the server.
- Repeat voting from the same visitor is prevented without requiring an account.
- Votes arriving after a poll closes are rejected with a clear message and the final results.
- Results stay hidden until the viewer votes or the poll closes.
- Displayed percentages always sum to one hundred and raw counts are shown alongside.
- Options cannot be added mid-poll without the results being marked as affected.
- Results are readable as text without relying on bar length or colour.
- 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.