Bug Report Triage

Gleap collects bug reports directly from a mobile app or website, often with a screenshot and device details attached. A Beam agent reads a new report and checks it against the approved rule, for example a keyword in the description or a specific device type, and applies the agreed action, such as tagging it as high priority or notifying the engineer who owns that part of the product. It works only from the fields Gleap captured at submission. Anything involving a report with unclear reproduction steps, or one that could affect many users at once, is routed to a human engineer to look into.

In-App Feedback Widgets

Gleap's widget lets a user leave feedback or a feature request without leaving the app. A Beam agent reads new feedback entries and applies the approved rule, for example grouping requests that mention the same feature or adding a tag when a rating falls below a set threshold, then updates the feedback board accordingly. It only sorts what has already been submitted, it does not respond to the user directly. Anything involving a message that sounds like a formal complaint, or a request tied to a paying customer's contract, is routed to a human on the product or support team.

Session Replay Context

Alongside a bug report, Gleap can attach a session replay showing what the user did before the issue occurred. A Beam agent checks whether a replay is attached to a report named in the approved rule and, if so, adds a note pointing the assigned engineer to it, or flags reports missing a replay as needing more information. It only checks for the replay's presence, it does not watch or interpret the recording itself. Anything involving a report where the replay looks incomplete or the issue still isn't clear from it is routed to a human to look at directly.