"We replaced three tools with Yaplet and our response time dropped from 4 hours to 2 minutes. The AI gets it right almost every single time."
MK
Maya K.
Head of Support, SaaS company
Bug reporting from your users
Every bug, with the context your devs need.
Stop asking "what browser?" and "what did you click?" Yaplet's widget grabs the screenshot, the console error, the network call, the replay and the device, all attached to one ticket. Your team reproduces on the first try.
- One-click bug reporting from inside your product
- Screenshot, screen recording and session replay, all attached
- Console, network and event logs captured for you
- Lands as a ticket linked to the customer's chat
4.9 average rating
|
on G2 & Capterra| Captured in seconds Live capture · demo9 sources Captured per ticket
What's captured
One click, a complete bug report.
Your user clicks the bug button. Yaplet grabs everything your engineers would have asked for and packages it into a single ticket.
The screenshot
The exact screen the user was on, with annotations they can draw on top.
A short screen recording
Optional video so your team sees the bug happen instead of hearing about it.
A session replay
Every click, scroll and input the user made before the report, in order.
Logs and metadata
Console errors, failed requests, browser, OS, viewport and the exact URL.
Bug report #482
From: [email protected] · just now
Screenshot
1
checkout.png · annotated
Console
[error] Uncaught TypeError: Cannot read properties of undefined
[warn] Stripe.js loaded twice
[info] POST /api/checkout 500 — 824msBrowser
Chrome 134
OS
macOS 15.4
URL
/checkout
Linked to chat #2317Priority · Medium
Inside every report
Everything your team needs to reproduce and ship a fix.
The same capture you'd pay Marker or Userback for, built into the widget your users already see. No second subscription, no new tab.
Screenshot capture
The exact pixels the user saw when things broke. They can annotate on top before sending.
Screen recording
When a still image isn't enough, users record a short video of the bug happening.
Session replay
Watch the last 30 seconds before the report, every click, scroll and input, in order.
Console logs
Every error, warning and log from the user's browser, bundled with the ticket.
Network logs
Failed requests, slow API calls, status codes and response sizes, ready for triage.
Browser & device info
Browser, version, OS, viewport, URL and any custom metadata you push, captured for you.
Triage in one place
From inbox to fixed, without the hunt
Bug reports land on a kanban board next to your chats. Drag, prioritise, assign, no jumping between Jira, email and Slack threads.
- All reports on a kanban-style board with custom columns
- Filter by priority, customer, browser or page
- Open the screen recording, replay or console with one click
Close the loop
When it's fixed, your customer hears it from you
Send a personal, branded reply the moment you ship the fix. The reporter feels heard, churn drops, and a bug becomes a reason to stay.
- Branded one-click email replies from inside the ticket
- Customer's chat history stays linked to the ticket
- Auto-tags so the same bug doesn't get reported twice
Live in minutes
Three steps from snippet to first report
Already running Yaplet? Bug reporting is one extra line. Starting fresh? You'll have your first report before your coffee cools.
1
Create your widget
Sign up free, set up a board for bug reports, and pick what fields you want users to fill in.
2
Add one line of code
Paste the snippet on your site (or use the WordPress, Shopify or WooCommerce plugin). Bug reporting is one extra call.
3
Triage from your inbox
When a user reports, the ticket lands on your board with everything attached. Open, fix, reply.
Install snippethtml
<!-- Add this once, anywhere on your site -->
<script src="https://yaplet.com/api/sdk/loader?widgetId=YOUR_WIDGET_ID" async></script>
<script>
Yaplet.initialize("YOUR_WIDGET_ID");
</script>Stop guessing what your users meant
Capture the bug, the context and the conversation in one ticket. Free plan forever, installed in minutes.
No credit card Free plan forever Cancel anytime
Common questions
Bug reporting, demystified
Short, honest answers. Still unsure? Open a chat and we'll reply ourselves.
Talk to a real person
We use Yaplet for bug reports too. Try it on us.
On a kanban board inside the same dashboard you use for chats. Each report is a ticket with the screenshot, recording, replay, logs and metadata attached. Drag it across columns the way you would in Trello or Linear.
No. The reporting button lives inside the Yaplet widget that's already on your site. If they can use the chat, they can report a bug.
It's opt-in per widget and rules-based, so you choose which visitors get recorded. When enabled, the widget captures lightly in the background and only the relevant window is attached to the report. No performance hit your users will notice.
Yes. You can add the fields you want (steps to reproduce, priority, custom dropdowns) so users hand over exactly what your team needs to triage.
Yes. Bug reporting works on the web widget on phones and tablets too. The capture adjusts to what the browser allows.
Yes. Push your own product events and metadata (user ID, plan, feature flags, internal trace IDs) through Yaplet so the report carries the context only you have.
Yes. It's part of the forever-free plan. You get the widget, bug reporting and the inbox without paying a cent. Paid plans add AI triage, automation and larger teams.
Reviews
People love us
Loved by people and teams that care about making every customer interaction more insightful and efficient.
G24.9/ 5
Excellent
Capterra4.9/ 5
Excellent