Reschedule and Cancel Links
Give every booking confirmation a link the person can use to move or cancel it.
What it adds
Tokenised self-service links in booking confirmations and reminders that let the attendee change or cancel without signing in.
What your agent is told to do
5
What your agent is told to do
5-
1
Put the two links in the booking confirmation, in every reminder, and on the confirmation screen itself. A person looking for the link is usually looking in the last message they received.
-
2
Land the link on a page that restates the booking in plain terms before offering any action, so someone who opened it by accident can see what they are about to change and back out.
-
3
Reuse the app's existing Signed Share Links mechanism for token generation, expiry, and revocation rather than inventing a second token scheme. If the app has Magic Link Sign-In, note that this link grants access to one booking only and must never establish a full session.
-
4
Give the owner a configurable cutoff, expressed as a period before the start time, after which the links explain that changes must go through the host instead of failing with an error.
-
5
Do not build the link from the booking's own identifier or a sequential value. A guessable link lets anyone walk the range and cancel other people's bookings.
Edge cases it handles
8
Edge cases it handles
8- Once the booking has started or passed, the link must stop working and say why. A link that still cancels a finished appointment corrupts the record and the reporting built on it.
- Inside the cutoff window the links must explain that self-service changes have closed and offer a way to contact the host, rather than presenting controls that then fail on submit.
- Tokens must be long, random, and unguessable, and stored so they cannot be read back from a database dump in usable form. Sequential or derived tokens let anyone enumerate and cancel other bookings.
- A slot chosen for a reschedule can be taken by someone else between the page loading and the confirmation. Re-check availability at the moment of commit and return the user to the picker with the slot marked gone rather than double-booking it.
- Both the attendee and the host are notified once per change. A retried delivery or a double submit must not send two cancellation notices for the same event.
- Cancelling must release the slot back to availability, and should trigger the Cancellation Waitlist if one exists, in the same transaction as the cancellation.
- A link that has already been used to cancel must show the cancelled state, not a fresh reschedule form.
- Reminders sent after a reschedule must carry the new time and a link that still works, not the payload frozen at booking time.
Definition of done
8
Definition of done
8- Confirmations and reminders both carry working reschedule and cancel links.
- Links use unguessable tokens issued through the app's existing signed-link mechanism.
- The link grants access to one booking and never creates a signed-in session.
- Links expire after the booking passes and respect a configurable change cutoff with an explanatory message.
- A reschedule into a slot taken mid-flow fails safely and returns the user to the picker.
- Each change notifies both sides exactly once, and cancellation releases the slot.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Feedback Widget
Feedback Widget
Let anyone report a bug or send a comment from the page they are looking at.
What it does
An always-available launcher that opens a short feedback form and submits it with page context attached.
How it works
- 1 Put a single persistent launcher in one corner of the app and open a compact form in place. Do not route the user to a separate feedback page and lose the context they were about to describe.
- 2 Attach the current URL, the app version, the viewport size, the signed-in account, and a short trail of recent client errors automatically, so the reporter does not have to describe where they were.
- 3 Show the captured context to the user before they send it, in a collapsible section, and let them remove it. Silent collection of screen state is a trust problem.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/feedback-widget
Interactive Transcript
Interactive Transcript
Put the transcript next to the player so clicking any line jumps playback to that moment.
What it does
A time-aligned transcript panel beside the audio or video player, with click-to-seek, a moving highlight, and in-transcript search.
How it works
- 1 Render the transcript from the timestamps the app already stores. If Voice Transcription exists, extend its output and its data model rather than producing a second transcript with its own timings.
- 2 Make every line a real seek target: clicking or pressing enter on a line moves playback to that time and keeps focus where the user left it.
- 3 Highlight the line currently being spoken and keep it in view as playback advances, using the player's own time updates rather than a separate timer.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/interactive-transcript
Permission-Aware Action
Permission-Aware Action
Decide once how a control behaves when the user is not allowed to use it.
What it does
A shared wrapper for buttons, menu items, and links that resolves visibility, disabled state, and the reason a user cannot proceed.
How it works
- 1 Inventory every action in the app that any role can be denied, and give each one a named capability rather than scattering role comparisons through the components that render it.
- 2 Pick one of three treatments per action and record the choice: hide it, show it disabled with a reason, or show it enabled and let the attempt fail into an upgrade or request-access path. Defaulting everything to hidden makes the product look smaller than it is.
- 3 Whenever an action is disabled, say why in words the user can act on — the role that is required, the prerequisite that is missing, the plan limit that has been reached — and where possible offer the next step.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/permission-aware-action
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.