Join the waitlist
Capture & fix · Bug capture

Every bug reportarrives already reproduced.

Your customer clicks what broke. Tore pins it, attaches the replay, console and network, strips out their secrets and hands engineering a ticket they can act on.

Join the waitlistSee it work

Tore opens soon. Join the waitlist and we'll email you the day you can start.

app.tore.ai/beacon-data/inbox
Example data
Report · via widget · Beacon Data
BUG-219 · engineering · Beacon Data

"My export stops at 500 rows"

CSV export stops at 500 rows

Priya R. signed in · Growth plan
New report Element pinned Evidence attached Secrets stripped 5 reports, 1 ticket Ticket ready
00:00elapsed · example time
I clicked Export CSV and the file stops at 500 rows. I have 912 contacts.
Priya R. · via widget · 09:14
priya@beacondata.io Chrome 141 · macOS 15 /contacts
replaylast 30 s
console1 error · 2 warn
network14 calls
browser, OSChrome 141 · macOS
Removed 3 secrets before uploadin Priya's browser
AuthorizationBearer removed Cookiesession=removed URL query/api/export?key=removed
Priya saw what was removed and reviewed the report before sending.
Priya R. · export stops at 50009:14
Dan K. · CSV is missing contacts09:31
Hana S. · only half my list10:02
Tomas V. · export cut off10:40
Lena M. · download incomplete11:05
BUG-219 · one ticket CSV export stops at 500 rows 5reports, 5 customers waiting
matched by page, element and error
CSV export stops at 500 rowsBUG-219 · 5 reports · pinned: button#export-csv · /contacts
replay 0:30 console · 1 error network · 14 calls linked error event
Handed to an investigation · 5 customers will hear when it's fixed
Tore knows who is reportingTore pinned the element Priya clickedTore attached replay, console and networkTore stripped secrets in the browserTore grouped 4 matching reportsTore handed the ticket to engineering
Gemini Flash · lowGemini Flash · lowGemini Flash · lowGemini Flash · lowClaude Sonnet · mediumClaude Sonnet · medium

Every tool your customer needs,inside the chat widget.

Your customer reports the bug right where it happened. They point at it, mark it up, record it and send, without leaving your app or installing anything.

app.beaconanalytics.com/revenue
Example data

Example: a customer of Beacon Analytics opens the Tore chat widget on their revenue page. They pin the blank chart, circle it on a screenshot, record the screen while changing the date range, keep the last 30 seconds included and send. The sent report lists the replay, recording, screenshot, pinned element, console, network, browser and operating system, and says two secrets were removed before sending.

  • Pin the element

    They click what broke. No describing it.

  • Mark up a screenshot

    They circle the problem themselves, with an arrow or a note.

  • Record the screen

    One click, right in your page. Nothing to install.

  • Last 30 seconds

    What happened before they clicked "report" comes too.

  • Details attached

    Console, network, browser and OS, without a single question.

  • Secrets stripped

    Removed before sending, and the customer is told.

Stop chasing the details.The report already has them.

The back and forth that used to come before any real work is gone. Engineering starts from the evidence.

No more "which browser?"

Console, network, browser and operating system are attached without the customer doing anything.

three emails to learn their setup

No guessing which button

They click the broken element to pin it, so you know exactly which control failed.

"the button doesn't work"

No failing to reproduce

The last 30 seconds arrive as a replay, and they can record the screen in one click with nothing to install.

"works on my machine", closed

No customer tokens in your tickets

Secrets are stripped before upload, and the customer is told what was removed.

API keys pasted into a ticket

One report.Everything engineering asks for.

Switch between what arrives with a single report. Nobody had to ask for any of it.

app.tore.ai/beacon-data/BUG-219/evidence
Example data
0:00replay of the last 30 s0:30
  1. 0:04Opened Contacts, 912 rows
  2. 0:12Clicked Export CSV
  3. 0:19Console error: export wrote 500 rows
  4. 0:27Opened the widget and pinned Export CSV
  5. 0:30Report sent with everything attached

From the customer's clickto work engineering can start.

Who and where

It already knows who is reporting, and on which plan.

The widget knows the signed-in customer, their account and the page they were on, so the report arrives with a name and a place instead of a mystery.

  • Nobody asks "who are you, what plan are you on?"
  • The page, browser and operating system filled in for them
report · BUG-219
Example data
Priya R.Beacon Data · Growth plan · signed in
page/contactspinnedbutton#export-csvbrowserChrome 141 · macOS 15
reported viachat widget · in the pageaccountBeacon Data · admin

Repeats

Five reports of one bug are one ticket, with a count.

Matching reports are grouped onto the ticket that already exists, so engineering sees one piece of work and how many people it hits. Known issues are answered before a new report is even filed.

  • One ticket, every reporter attached to it
  • The count shows how many customers are waiting
  • Known issues answered before a ticket exists
BUG-219 · reports
Example data
Dan K. · CSV is missing contactsgrouped
Hana S. · only half my listgrouped
Tomas V. · export cut offgrouped
5
CSV export stops at 500 rowsBUG-219 · 5 reports · 1 ticket
Maya opened the widget on /contacts: "This is a known issue and we're on it. Want an update when it's fixed?"

In the loop

A conversation becomes a ticket in one action, and the customer hears back.

When a bug shows up in a chat or email, turn it into a ticket without retyping a word. Everyone who reported it is told when the fix is live.

  • A bug moves to engineering without retyping it
  • Reporters told automatically when their fix is live
  • Wording fixes arrive as a suggested edit, ready to apply
inbox · Dan K.
Example data
My CSV export is missing about half my contacts.
Dan K. · email · 09:31
ReplyNoteConvert to ticket
  1. Linked to BUG-219, thread attached09:32
  2. Fix approved by your engineer11:48
  3. Dan, Priya and 3 others told it's fixed12:05

Hand-off

It goes straight into an investigation.

The customer's report is linked to the matching error event from your error tracker, so the replay and the stack trace meet on their own. Tore's investigation starts from both.

  • The report and the stack trace meet automatically
  • The investigation reads your code with the evidence in hand
  • By default the change it proposes waits for your engineer's approval
BUG-219 · linked
Example data
Customer reportPriya R. · /contacts
pinned button#export-csv
replay 0:30
Error eventexport wrote 500 rows
paginate.ts:57
38 events · 1h
Investigation started
Next: see how Tore reads the codeAI investigations →

Tune it

Screen recording onAuto-group repeats 3 reportsStrip secrets always
All AI controls →
30 sof replay from before they clicked report
1 clickto record the screen, with nothing to install
4things attached on their own: console, network, browser, OS
2 modesreport a bug, or suggest an edit to your wording

Keep exploring.

Capture & fixAI investigationsThe report meets your code, commits and stack trace.See how → Capture & fixError monitoringCatch the bug before anyone has to report it.See how → SupportChat widgetWhere your customers report it, signed in and known.See how →

Make the next bug reportthe easiest one to fix.

Add the widget, and every report arrives with the replay, console and network already attached.

You're on the list. We'll email you the day you can start.

Get early access when Tore opens. No spam.