"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 actually need.
Stop chasing screenshots over email. Yaplet's widget captures the bug, the click that caused it, the screen recording, the console, the network — all in one ticket. Your team reproduces in minutes.
- One-click bug reporting from inside your product
- Screenshot, screen recording and session replay — all attached
- Console, network and event logs captured automatically
- Lands as a ticket linked to the customer's chat
5.0 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 a button. Yaplet quietly grabs every piece of evidence your engineers need — and packages it into a single ticket.
The screenshot
The exact screen the user was looking at, with optional annotations.
A short screen recording
An optional short video so your team sees the bug happening in real time.
A session replay
Replay the user's actions before the report — clicks, scrolls and inputs, in order.
Logs and metadata
Console errors, failed network requests, browser, OS and the page they were on.
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.
Yaplet ships with the capture you'd expect from a dedicated bug tool — built right into your support widget. No second subscription, no new tab.
Screenshot capture
A still image of the exact moment the user hit a problem, attached to the ticket and viewable in one click.
Screen recording
Users can record a short video of the bug in action — handy when a screenshot doesn't tell the whole story.
Session replay
Replay what the user did right before they reported — every click, scroll and input, in order.
Console logs
Every console error, warning and log from the user's browser session is bundled with the ticket.
Network logs
Failed requests, slow API calls, status codes and response sizes — all captured for triage.
Browser & device info
Browser, version, OS, viewport, URL and any custom metadata you want to attach — automatically.
Triage in one place
From inbox to fixed, without the hunt
Bug reports show up on a Yaplet board you already know. Drag, prioritise, assign — same place where the rest of your conversations live.
- 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 to the reporter when you ship the fix. They feel heard — and you turn a bug into a positive moment.
- 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
If your site already has Yaplet, bug reporting takes one extra line. If it doesn't, you'll be done before your coffee is.
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, install in minutes.
No credit card Free plan forever Cancel anytime
Common questions
Bug reporting, demystified
Short, honest answers. Still unsure? Open a chat — we'll reply ourselves.
Talk to a real person
We use Yaplet for bug reports too — try it on us.
On a Yaplet board inside the same dashboard you use for chats. Each report is a ticket with the screenshot, recording, replay, logs and metadata attached. You can move it across columns like any kanban tool.
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.
Session replay is opt-in per widget — you decide whether to enable it and which visitors are captured via your replay rules. When enabled, the widget records lightly in the background and the replay is attached to the bug report so your team has the context they need.
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.
It's part of Yaplet's free plan. You get the widget, bug reporting and the inbox without paying. Paid plans add advanced AI, automation and team features on top.
Reviews
People love us
Loved by people and teams that care about making every customer interaction more insightful and efficient.
G25.0/ 5
Excellent
Capterra5.0/ 5
Excellent