Everything a report needs, and a place to finish it

Eight capabilities, one widget and one board. Each one has its own page with the exact behaviour, limits and plan.

Evidence capture

Screenshot, replay, console, network and environment on every report.

  • Annotated screenshot, drawn by the reporter on their own screen
  • Console errors and network calls, with secrets scrubbed
  • Page URL, viewport and browser on every ticket
Learn more about Evidence capture

A render of the console and network log inside a ticket in the panel. One console error and two failed requests landed in the twenty-two seconds before the report, and the nine entries are listed with their timestamps: a warning that the cart totals were stale, two POSTs to /api/cart/discount that returned 500, an uncaught TypeError raised in applyDiscount, and the clicks between them. Errors are red, warnings amber, requests teal until they fail.

Session replay

The minutes before the report, inputs always masked.

  • The DOM as it changed: mutations, pointers, scroll and masked input
  • Rage clicks recorded as their own event — three clicks on one target inside a second
  • Inputs always masked — typed characters are never recorded
Learn more about Session replay

The session behind ticket NT-248, playing: fifty-seven seconds recorded in three segments, with one interval unavailable because the page was hidden. The reporter reaches the checkout, applies the coupon SPRING24, and the discount appears without the total changing. Paying answers 500 twice; they rage-click three times and open a report. Beside the player, the same session as a log of twenty entries — clicks, requests, a stale-totals warning and an uncaught TypeError — with the row under the playhead highlighted as it plays.

Screen recording

The reporter records the bug as it happens. Pro.

  • The reporter presses Record in the composer and Stop on the capture pill
  • Uploaded while it records; the ceiling is 60 seconds and a cut take says so
  • Pro capability — session replay covers the Free plan
Learn more about Screen recording

The widget while it records and after it did: a pill at the top of the page counting the take against its one-minute ceiling with a Stop button, and below it the same composer twice — offering Screenshot, Record and Attach, then holding the recording as an attachment while the Record button is gone.

Board & pipeline

Received → WIP → QA → Done, severity and priority apart.

  • Received → WIP → QA → Done, renameable and reorderable per project
  • Severity and priority as independent fields, with independent filters
  • Public and internal replies, with reply templates
Learn more about Board & pipeline

The board's four stages, left to right: Received with 4, WIP with 3, QA with 2, Done with 6. The newest ticket, NT-248 — a discount code accepted but the total unchanged — sits at the top of Received, high priority, assigned to Ana Ruiz, with a screenshot and a recording attached.

Reporter portal

Status and public replies from a link, no account.

  • A signed per-reporter link — no account, no seat, every ticket that person filed
  • A named client access with its own key: the project's progress, not one reporter's tickets
  • Five languages, set per project, falling back to the reader's browser
Learn more about Reporter portal

A render of the reporter’s portal, branded as the customer’s own product. It shows report NT-248 at stage Received, the team’s public reply, a box to answer back, and a note that three other reports from the same person are on the page. No account is involved.

Widget & theming

JSON theme, custom CSS, whitelabel, Shadow DOM isolation.

  • One <script> tag, rendered inside a Shadow DOM
  • Colours, radii and labels themed from JSON on every plan
  • Custom CSS and whitelabel on Pro
Learn more about Widget & theming

The same widget composer in five host brands' colours — blue, teal, green, purple and red — stacked as a deck that deals the front card to the back, and the 44-pixel launcher pill it opens from.

Surveys

NPS, CSAT, rating, choice and free text, in the same widget.

  • NPS, CSAT, rating, single choice, multiple choice and free text
  • One active campaign per survey project; draft, paused and closed beside it
  • Aggregates: response count, completion rate, NPS, CSAT, rating averages
Learn more about Surveys

A survey open over a shop's checkout page. The campaign “Checkout experience” asks how likely the visitor is to recommend the shop, on a scale of 0 to 10 with 9 chosen, then asks the reason for that score in a free-text box. The feedback launcher stays on the page, dimmed under the backdrop.

Review mode

Pick elements on the live page and file tickets. Pro.

  • Pick an element on the live page and file a ticket against it
  • HMAC-signed sessions, valid for eight hours
  • Pro capability, started by a member or above
Learn more about Review mode

A render of review mode on a staging checkout page. A floating dark bar reads “Ana Ruiz”, then “Choose an element · Escape to cancel”, with the element picker switched on; the picker highlights the page’s Place order button in the box-model colours a browser inspector uses and prints its node line, its spacing and its accessibility role on a card above it.

The ticket goes where the work already happens

Slack and Microsoft Teams take the notification on every plan. The seven trackers take the ticket itself, with its evidence, on Pro.

All integrations
  • Jira
  • Linear
  • GitHub
  • Trello
  • Asana
  • ClickUp
  • monday.com
  • Slack
  • Microsoft Teams

Every one of them is also a tool your agent can call

Notarus ships an MCP server with 100% panel parity. What follows is what the server says when something connects to it — the tool list is the handshake, not a claim on a page.

MCP server & docs

The Notarus MCP server registers nineteen tools, by the panel surface each one drives. Tickets: list_tickets, get_ticket, create_ticket, move_ticket, assign_ticket, comment_ticket. Sessions: list_sessions, get_session, get_recording, search_logs, get_errors. Board: list_ticket_statuses, reorder_ticket_statuses, ticket_stats, get_insights. Reporter portal: create_reporter_portal_link, render_reply_template, get_client_portal, set_client_portal. An agent connected to it lists tickets by status, reads a session recording, searches captured logs and moves a ticket between statuses, without anyone opening the panel.

Try every feature on the Free plan.

One seat, five projects, no credit card.

Start free Free plan · No credit card