In-app bug reporting
Turn “it’s broken” into a bug report you can investigate.
Give users a bug reporting widget inside your app. Collect support messages and on-demand reproductions with session replay, console output, and network context.
Let customers show you the problem.
A customer says the save button does nothing. Your developer tries it locally and it works. The next step is usually another email asking for the page, browser, screenshots, and steps to reproduce.
With Clairvio installed in your app, the customer can open your support widget and choose to record the affected steps. Your team can follow their actions and inspect the captured console and network activity in the same diagnostic session.
Example: a setting won’t save. Ask the customer to start recording and try saving again. If the problem happens during capture, inspect the request status and console output alongside the replay. Use that evidence to decide what to investigate next.
From the first report to a recorded reproduction
- Add the widget to your app. Install the script and connect a support button. The customer can send a message without making a recording.
- Capture the affected steps. The customer chooses to start recording through the widget. If they contacted you elsewhere, send a diagnostic magic link instead. They don’t need an extension or a Clairvio account.
- Investigate with your team. Watch the session live or review the completed recording. Follow the navigation path, console output, and captured network requests to understand the reproduction.
Recording is on demand. It starts when a diagnostic session is activated. Clairvio cannot recover a failure that happened before recording started, so ask the customer to repeat the affected steps.
Browser context developers can use
What the customer did
Session replay and navigation events help you follow the sequence of actions during capture, including the page transitions leading up to the reported issue.
What the browser reported
Captured console messages help surface warnings and errors the customer may never see. Network details include URLs, status codes, timing, and captured payloads to help investigate failed requests.
A reproduction you can revisit
Review the recording with another developer or share its link through your existing support and issue-tracking workflow. The evidence helps your team investigate; it does not guarantee a root cause or a fix.
Keep everyday support close by.
Not every question needs a recording. The support widget lets customers send a short message, and the Help Center lets you publish reusable articles and troubleshooting instructions in your app.
This workflow suits SaaS teams where developers also handle support: offer a common answer, hear the customer’s question, then request a reproduction when you need more evidence.
Questions before you install
Can we keep our current support inbox?
Yes. Send a diagnostic link in an existing email or support conversation and investigate the session in Clairvio. You can use the widget when you want customers to reach you directly from the app.
Is the widget a full issue tracker?
Its job is to collect support messages and diagnostic recordings. Use the resulting context in your existing process for prioritizing, assigning, and shipping fixes.
How does this compare with Gleap?
Both products address customer support and bug reporting. Read our Clairvio and Gleap comparison to weigh a focused support-and-diagnostics workflow against Gleap’s broader platform.