How is this different from a support inbox like Intercom?

A support inbox is built for conversation and knows nothing about the browser. This is built for the handoff to engineering: every bug report carries the stack trace, the browser and the steps, so no one has to ask.

Does it replace our error monitoring?

No, and it should not. Sentry catches exceptions nobody reports; this catches the problem a person noticed and describes what they were trying to do. Most teams that can afford both run both.

How does pricing scale with our team?

It does not scale with the team at all. One flat plan covers unlimited projects, widgets and submissions, so adding support agents or engineers to the inbox has no effect on the bill.

For small saas teams

Your users already know what is broken. Most of them are not telling you.

A team of three to fifteen has the worst version of this problem: enough users that things break in ways you cannot reproduce, and not enough people to run a support operation. The gap gets filled by whoever answers the shared inbox, and it gets filled badly.

Start freeNo credit card required.

The situation

What this usually looks like

Support and engineering speak different languages
Support forwards "customer says dashboard is blank". Engineering asks which dashboard, which browser and which account. Three days pass, and the customer has already emailed twice more.
Half the tickets close as not reproducible
Usually because nobody recorded the window size, the time zone or the route the person took. The bug was real; the context was not captured.
Feature requests live in someone else notes
They arrive in calls, in support threads and in Slack, and there is no single list that survives the person who took them leaving.
Per-seat pricing punishes involving the team
The moment support, design and two engineers all need access, tools that charge per seat make it cheaper to keep people out of the loop.

Why this fits

What changes for small saas teams

The report arrives triaged: Browser, operating system, screen size, time zone, load time, up to ten JavaScript errors with stack frames, and the last fifty actions the person took. Support forwards nothing; engineering asks nothing.
Signed-in users are identified automatically: Call identify with the user id you already have and every report arrives attached to a real account, so nobody is asked for an email and nobody has to match a report to a customer by hand.
One inbox for bugs and requests: Both come through the same widget, with a type the person picks, and move through the same five statuses. Marking something shipped emails whoever asked, in their language.
Your agent reads the inbox over MCP: Three tools over OAuth: list what is open, read one report in full, mark it done. For a team where engineers work with Claude Code or Cursor, that removes the copy-paste step entirely.

Who this is not for

Save yourself the trial

If you need integrations that push reports into Jira or Linear automatically, this does not have them yet, and Usersnap or Marker.io will fit your workflow better. If you need session replay to understand behaviour rather than to fix a specific bug, this is the wrong category of tool. The comparison pages say which tool we would send you to instead.

FAQ

Questions

How is this different from a support inbox like Intercom?: A support inbox is built for conversation and knows nothing about the browser. This is built for the handoff to engineering: every bug report carries the stack trace, the browser and the steps, so no one has to ask.
Does it replace our error monitoring?: No, and it should not. Sentry catches exceptions nobody reports; this catches the problem a person noticed and describes what they were trying to do. Most teams that can afford both run both.
How does pricing scale with our team?: It does not scale with the team at all. One flat plan covers unlimited projects, widgets and submissions, so adding support agents or engineers to the inbox has no effect on the bill.

Put it on your site today.

One script tag. Unlimited projects, widgets and reports on one plan, and your users never make an account.

Start free Read the docs