Announcement Bar
Put a timed message across the top of the site without shipping a deploy.
What it adds
An operator-configured, dismissible strip at the top of public pages, with scheduling and a link.
What your agent is told to do
5
What your agent is told to do
5-
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.
-
4
Define precedence when an announcement and an incident banner are both active. Show the incident and suppress the promotion; a sale strip above an outage notice looks negligent.
-
5
Do not make the bar a full-width interstitial or an auto-expanding panel. A strip a visitor can read in one line and dismiss in one click is the whole point.
Edge cases it handles
8
Edge cases it handles
8- A dismissal must be remembered per visitor and per announcement, so closing one message does not suppress the next one, and editing the message brings the bar back for people who dismissed the old text.
- The bar must push fixed and sticky headers down rather than sitting over them, and must release that space cleanly when dismissed without leaving a gap or shifting the page under a scrolling reader.
- Scheduled start and end times must be entered in a stated zone and evaluated against real time, so a sale that ends at midnight ends at midnight for the audience it was set for, not for the server.
- Operators will choose colours that make the text unreadable. Compute contrast against the configured background and either warn in the admin screen or force a legible text colour.
- The bar must be announced to assistive technology as it appears without stealing focus from whatever the visitor is doing, and its close control must be reachable and labelled by keyboard.
- An anonymous visitor with no account still needs their dismissal remembered. Store it locally and key it to the announcement identifier, and accept that clearing site data brings it back.
- On a narrow screen a long message wraps to three lines and eats the viewport. Cap the length in the admin screen and truncate gracefully rather than letting it grow.
- An expired announcement must disappear on its own. A promotion still showing a week after the sale ended damages more than it ever earned.
Definition of done
9
Definition of done
9- Operators can publish, schedule, edit, and expire an announcement without a deploy.
- The bar shares the existing banner component rather than being a second independent strip.
- Fixed and sticky headers are pushed down, not covered, and no layout shift occurs on dismissal.
- Dismissal is remembered per visitor and per announcement, and resets when the message is edited.
- Text contrast against any configured background meets the accessible minimum.
- The bar is announced to screen readers without moving focus, and its close control is keyboard-reachable.
- An active incident banner takes precedence over a promotional announcement.
- 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.