Voice Notes
Say it instead of typing it, and attach the recording where the conversation is.
What it adds
In-app recording of short audio notes attached to a record, comment, or message.
What your agent is told to do
5
What your agent is told to do
5-
1
Add recording to the places where people already leave text, most likely alongside Comments and Mentions, so a voice note is another kind of comment rather than a separate feed nobody checks.
-
2
Store the recording through the app's existing file upload path so a voice note inherits the same retention and access rules as any other attachment on the record, and disappears with the record when it is deleted.
-
3
Show a live duration and a simple level meter while recording, and let the user review and discard before it is sent. Nobody should be committed to a recording the instant they stop.
-
4
Run the recording through the app's existing Voice Transcription so every note carries a searchable text version alongside the audio.
-
5
Do not start capturing until the user explicitly presses record. A microphone that opens on page load, even without saving, is the kind of thing that ends a customer relationship.
Edge cases it handles
8
Edge cases it handles
8- Microphone permission may be denied at the browser or operating system level, or revoked mid-session. Detect it and explain how to re-enable it rather than showing a record button that does nothing.
- Enforce a maximum recording length and warn the speaker as the cutoff approaches, then stop cleanly and keep what was captured instead of discarding the take.
- A dropped connection mid-recording must not lose the audio. Buffer locally and upload on reconnect, and tell the user the note is pending rather than pretending it sent.
- Browsers record in different container and codec combinations. Normalise on the server to one format every target browser can play, and keep the original until the conversion succeeds.
- Recipients who cannot play audio, are in a meeting, or use a screen reader need the transcript shown alongside the player, not hidden behind a second click.
- Reserve the player's dimensions in the layout so a list of comments does not jump as audio elements load.
- Voice notes are user-generated content and need the same deletion, retention, and access rules as any other attachment, including removal when the parent record is deleted.
- Recording while another tab is already using the microphone, or while the device is on a call, must fail with a clear message rather than producing a silent file.
Definition of done
9
Definition of done
9- Users can record, review, discard, and attach an audio note from the places they already comment.
- Recording only begins on an explicit user action.
- Denied or revoked microphone permission produces a clear explanation and recovery path.
- A maximum length is enforced with a warning before the cutoff, and the captured audio is kept.
- Audio is normalised server-side and plays in every supported browser.
- Each note carries a transcript displayed alongside the player.
- Notes follow the app's existing storage, retention, and access rules.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Direct Messages
Direct Messages
Let two users hold a private conversation inside the app instead of leaving to email.
What it does
One-to-one private threads with message history, per-conversation unread counts, and blocking.
How it works
- 1 Build the conversation list, the thread view, and the unread badge. Keep the first version to one-to-one threads only and defer group conversations, reactions, threading, and file attachments rather than shipping all of them half-finished.
- 2 Reuse the app's existing Read and Unread State and Notification Center rather than inventing a second unread mechanism and a second alert path. A message notification should sit alongside every other notification the user gets.
- 3 Reuse the composer, mention handling, and rendering rules from Comments and Mentions instead of writing a second message editor with subtly different escaping.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/direct-messages
Internal Notes
Internal Notes
Give staff a place to write things the customer must never see.
What it does
Notes attached to a record that are readable only by internal roles, and that never appear in any export, feed, or API response.
How it works
- 1 Model an internal note as a distinct visibility state on the server, not a flag the client filters on. Every read path — record view, search, digest emails, exports, webhooks, API serializers — must exclude internal notes for anyone without the internal role.
- 2 Give internal notes a visual treatment that cannot be confused with a public comment: different surface, a persistent label, and a warning that survives collapse or truncation. If a user has to remember which box is which, this feature has failed.
- 3 Decide explicitly what an impersonating admin or a support session sees, and state the rule in the UI. Support staff reading internal notes is usually fine; a support session rendering them inside a screen the customer is watching is not.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/internal-notes
Jira Ticket Creation
Jira Ticket Creation
Create Jira work items in the right project and type, with the fields that project requires.
What it does
A server-side path from an in-app record to a Jira work item, with per-project field discovery, mapping, and a stored ticket reference.
How it works
- 1 Discover the destination project's issue types and their required fields at configuration time and again before creating, and present the administrator with a mapping screen. Do not hardcode a field set; every Jira instance is configured differently and a hardcoded schema fails on the second customer.
- 2 Make the deployment type and site part of the connection so hosted and supported self-managed instances are handled deliberately, and keep the credential and site details server-side only.
- 3 Map app users to Jira identities through an explicit, administrator-maintained mapping, and fall back to leaving the field unset with the reporter named in the description rather than guessing an account from an email address.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/jira-ticket-creation
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.