Discount code accepted but total unchanged
/checkout?step=payment
Eight capabilities, one widget and one board. Each one has its own page with the exact behaviour, limits and plan.
Screenshot, replay, console, network and environment on every report.
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.
The minutes before the report, inputs always masked.
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.
The reporter records the bug as it happens. Pro.
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.
Received → WIP → QA → Done, severity and priority apart.
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.
Status and public replies from a link, no account.
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.
JSON theme, custom CSS, whitelabel, Shadow DOM isolation.
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.
NPS, CSAT, rating, choice and free text, in the same widget.
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.
Pick elements on the live page and file tickets. Pro.
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.
Slack and Microsoft Teams take the notification on every plan. The seven trackers take the ticket itself, with its evidence, on Pro.
All integrationsNotarus 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.
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.
One seat, five projects, no credit card.