Live Chat Widget
Let visitors ask a question from any page and get a real answer from your team.
What it adds
A corner chat bubble that opens a persistent conversation between a visitor and staffed agents, with an agent-side inbox.
What your agent is told to do
5
What your agent is told to do
5-
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.
-
4
Reuse the app's existing Rate Limiting and Notification Center rather than inventing per-widget throttles and a parallel alert channel. Anonymous visitors need a stricter limit than signed-in users.
-
5
Do not open the socket on every page load for every visitor. Load the bubble, and only connect when the visitor opens it, so an idle marketing page does not hold a live connection.
Edge cases it handles
8
Edge cases it handles
8- The socket will drop on flaky mobile connections. Queue messages typed while it is down, show them as pending, and replay them in order once it reconnects rather than dropping them or reordering them.
- Outside staffed hours the widget must say so honestly and set an expectation for a reply, plus collect an email address. A widget that looks live at 3am and never answers is worse than no widget.
- A double-click on send, or an automatic retry after a timeout, must not post the message twice. Give each outgoing message a client-side identifier the server treats as idempotent.
- The conversation must survive a page navigation and a full reload. A visitor who clicks a link mid-question and loses the transcript will not start again.
- Anonymous visitors are the spam surface. Rate-limit by session and by address, cap message length and frequency, and make a flood cheap to shut off without taking the widget down for everyone.
- A visitor who starts anonymously and then signs in must have the conversation merged onto their account, not left orphaned under a session identifier.
- The widget must be reachable and dismissible by keyboard, and must not cover a page's primary action or a cookie banner on a small screen.
- Transcripts contain whatever a visitor types, including card numbers and passwords. Decide retention, restrict who can read a transcript back, and support deleting one on request.
Definition of done
9
Definition of done
9- A visitor can open the widget, send a message, and see a reply without leaving the page they are on.
- The conversation persists across navigation, reload, and a return visit in the same browser.
- Messages sent while disconnected are queued and delivered in order once the connection returns.
- Duplicate sends from double-clicks or retries are rejected server-side.
- Away hours are stated explicitly and the widget collects an email address when nobody is available.
- Anonymous visitors are rate-limited and a flood can be stopped without disabling the widget entirely.
- The widget is fully operable by keyboard and never obscures the page's primary action.
- 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
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
Announcement Bar
Announcement Bar
Put a timed message across the top of the site without shipping a deploy.
What it does
An operator-configured, dismissible strip at the top of public pages, with scheduling and a link.
How it works
- 1 Extend the existing Service Incident Banner rather than adding a second bar. It already handles scheduling, targeting, dismissal, and severity; this is a marketing-styled variant of the same component, and two independent bars will eventually stack on top of each other.
- 2 Let an operator set the message, an optional link, background and text colours, and a start and end time from an admin screen. Requiring a deploy to run a weekend promotion means it goes live late.
- 3 Insert the bar into the document flow so it pushes fixed headers and sticky navigation down. Overlaying it on top of the header hides navigation on exactly the pages people arrived on.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/announcement-bar
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.