Notification schedule
My notification time resets after I save.
Install one lightweight feedback widget, keep the useful page context, triage the signal, and show users what shipped.
Free signup is open to everyone. The 100-member programme adds guided onboarding and up to 12 earned Pro months.
The customer stays inside your product. The useful context arrives automatically, and the next action lands where your team already works.
A short message, without leaving your product.
Notification schedule
My notification time resets after I save.
Message, page, device, time, and screenshot together.
“My notification time resets after I save.”
Bug · just now
Route it to GitHub, Slack, email, or a webhook.
GitHub issue #184
Created with the original context
#product alert
The team sees it immediately
Or send it anywhere
Email, Discord, or your own webhook
The evidence arrives beside the message, so your team can reproduce the problem and respond without interrogating the customer.
Captured automatically, with screenshots always optional.
ACME APP · NOTIFICATIONS
Resets to 8:00 AM after save
The screenshot shows the problem before anyone asks for reproduction steps.
New feedback is obvious, the important context is already attached, and a clear next action is always within reach.
Inbox
Review new messages and move the useful signal forward.
3
messages
My notification time resets after I save.
I expected 9:00 AM, but the page shows 8:00 AM when I return.
Keyboard shortcuts would make capture much faster.
A quick command menu would help us file ideas without leaving the keyboard.
The new editor feels much faster.
Everything opens immediately now. Really nice improvement.
Publish a shipped update inside your product, or keep the decision visible on a public feedback board.
A concise update appears inside the product they already use.
Notifications
Your chosen time now stays exactly where you put it, on every device.
Thanks to everyone who reported this.
Ideas, status, and official replies stay together in public.
Ideas and decisions
Submit ideaAdd a weekly review view
Planned · Official reply
Notification schedules
Shipped · 4 replies
From zero to a real report
Create a project, copy the exact snippet, and send one test message from your own page. Advanced customization can wait until the feedback is already flowing.
Install once
Copy the dashboard-generated embed yourself, or hand the bounded instruction to your coding agent. Either path ends with a real test report.
1. Create a project
Your browser-safe project key is generated for you.
2. Paste once
Put the stable embed in the shared app shell.
3. Send one test
Verify the real page and browser arrive in the inbox.
No private key belongs in the browser.
<div data-feedbacks-host="your-project-key"></div>
<script
src="https://app.feedbacks.dev/widget/latest.js"
data-project="your-project-key"
defer
></script>Keep the stable embed unchanged. Form fields, placement, copy, and styling update remotely after you save them in feedbacks.dev.
Under 20KB
The production widget has a CI-enforced gzip budget.
Browser-safe
The public project key cannot read your private inbox.
One feedback loop
Collect, triage, route, and publish updates from one place.
No trial clock and no card. Upgrade when more projects, unlimited volume, and deeper routing are worth paying for.
Free forever
$0
no card neededFor side projects, launches, and growing products collecting their first useful signals.
No card. No trial clock. No tiny asterisk plotting backstage.
Pro, when you need it
$19
/ monthFor products with steady feedback, more destinations, and more automation. Cancel without losing your work.
The Free plan stays available if you downgrade.
Straight answers
The production widget is under 20KB gzip, loads asynchronously, and has a CI size budget.
No. Publishable project keys are rejected by private REST and MCP endpoints.
No. Save the form in the dashboard and the existing widget loads the change.
A short note, optional rating and screenshot, plus the page and browser context needed to understand it.