Enable bug reporting in your widget

Updated May 22, 2026

Yaplet's bug reporting is the fastest way for a visitor to tell you something is broken. One click from the widget opens the report form, and console logs, network logs, the pages they visited and device metadata travel with it automatically — the visitor can also attach an annotated screenshot and a screen recording. This article shows you how to put the button on your widget's home screen.

1. Open the chat widget

In the sidebar, open Brand → (your brand) → Chat widget. There is no Widgets list page and no "new widget" dialog — a chat widget comes into existence with the brand, so this row is the widget.

2. Add a bug report card to the Home screen

  1. Open the Home screen tab.
  2. Under Home Cards, click Add Card.
  3. Choose the card type Form ("a button that opens one of your forms, such as a bug report").
  4. Give it a Title such as "Report a bug" and, if you like, a short Description.
  5. Pick your bug form under Form to Open.
  6. Set Card Icon to Bug so visitors recognize the button.

Use the arrows on each card to move it up or down — cards appear on the home screen in the order they are listed here.

Whether visitors are offered the screenshot and recording buttons is decided on the form itself: open the form's builder, click Settings, and look under What visitors can attach for the Screenshot and Screen recording switches. Both are already on for the bug form Yaplet created with your account. They are extra buttons in the widget's form and only appear on websites, not in the phone app.

If you do not have a bug board and form yet

The Form to Open dropdown only lists forms that already exist, so make one first:

  1. In the sidebar, under Conversations → Tickets, click + New board at the bottom of the list. It creates a board and opens its Settings tab.
  2. Rename it, set Type to Bug, and save.
  3. Switch to the board's Forms tab and click Add form. A description field is usually all a bug form needs — everything else is captured automatically.

Creating a board needs the Board management right and building the form needs Forms. Both come with the Feedback boards & bug tracker add-on.

3. Save

Click Save changes in the title bar. The button appears on your widget's home screen immediately, on every page where the widget is installed.

What visitors see

Clicking the button opens the form. The visitor answers the questions, and on the last step — if the form has them switched on — an 📸 Add Screenshot and a 🎥 Add Recording button appear. Pressing Add Screenshot captures the page and overlays a small drawing toolbar so they can mark up the problem area, then returns them to the form to submit. Console logs, network logs, the pages they visited and device metadata are collected in the background, with nothing for the visitor to do.

Session replay is not part of this. It is a separate paid add-on and stays off until you switch it on — see Session replay — what it is and how to enable it.

Yaplet can open the form too

You do not need the home-screen card for this. When a visitor tells Yaplet in the chat that something on your website or app is broken — an error, a crash, a page or button that does not work — Yaplet opens your bug form right inside the conversation, picking the default form of your default Bug board first. The report reaches your board only once the visitor submits the form. A visitor who asks for a new feature gets your feature-request form the same way.

Yaplet keeps this for real faults of your site. A problem with an order or a payment, a how-to question or a wish to talk to a person does not get a bug form, and a sales pitch is not a feature request. If the brand has knowledge, Yaplet searches it first.

Without the add-on, or on Facebook, Instagram and email, where forms cannot open, Yaplet notes the report in the conversation and hands it to your team — as long as the Visitor asks Yaplet for a person switch is on (under AI agent → Human hand-off). Otherwise it tells the visitor honestly that it cannot file the report there.

Next steps

Now that the button is live, learn what data is collected with each report — see What gets captured when a user reports a bug.

Did this article answer your question?