NOCK NOCK

Product

Feedback that arrives as reproducible tickets.

NOCK is the feedback layer for web products that need fewer vague reports and fewer follow-up loops. It collects customer signal in-product, packages the technical context, and gives your team a clean place to triage before syncing work elsewhere.

Start Lite trialRead implementation docs
Ticket package
Customer signal

Checkout freezes after payment click

The customer explains what happened in plain language.

Product context

/checkout · Safari 17.4 · 1440 x 900

Route, browser, and viewport arrive with the report.

Runtime evidence

TypeError plus failed POST request

Console and network evidence point to the failing handler.

Next action

Reply, assign, or sync to Linear

The team can triage before creating engineering work.

After submission

A cockpit for the work after the knock.

After a report arrives, NOCK keeps customer conversation, captured evidence, internal decisions, and Linear handoff visible as one workflow.

NOCK cockpit
TCK-204 · checkout
Customer messageOPEN

“Pay button freezes, but only after card details.”

NOCK preserves the human report and adds enough product context for the team to act without a long back-and-forth.

runtime evidence
TypeError: pay is not a function
Checkout.tsx:88:14
POST /api/pay 500

Inbox triage

New ticket

Support sees customer language, project, category, and owner queue first.

AI brief

Repro clue

A short technical summary separates likely cause from customer-facing copy.

Portal reply

Customer-safe

The response can ask for one missing detail without exposing logs or Linear links.

Linear handoff

Scoped issue

Only the actionable engineering work moves to Linear with the shared ticket URL.

Product lifecycle

Built around the full feedback path.

01

Capture the report where it happens.

NOCK lives inside the product experience, so feedback arrives with the page, device, and moment that created it. Customers can report bugs, ideas, or questions without leaving your app or creating an account.

  • Quiet launcher that opens from your product UI
  • Bug, idea, and question flows with focused prompts
  • Explicit image uploads through click, paste, or drag and drop
  • Shadow-DOM isolation so your app styles stay untouched
02

Enrich it before triage.

Every report can carry technical context before your team sees it. AI follow-up questions turn vague customer language into a clearer ticket while preserving the raw customer message.

  • URL, browser, OS, viewport, and screen data
  • Console logs and failed network requests when enabled
  • AI-suggested title, summary, and reproduction clues
  • Internal-only context kept separate from customer-facing replies
03

Route the right work onward.

The NOCK dashboard is the first stop for triage. Teams can reply to customers, add private notes, assign ownership, and sync only the work that belongs in Linear.

  • Inbox-first workflow for review before engineering handoff
  • Customer-safe status updates through shared portal links
  • Optional Linear sync for issues that need board visibility
  • API and webhooks for custom routing later

Operational depth

The details behind each report.

The landing page gives the short version. This is the product behavior teams need to understand before putting a feedback widget into production.

What NOCK captures

The ticket carries the product state your team usually has to ask for after the fact.

  • Current URL and route
  • Browser, operating system, viewport, and screen size
  • Console entries and failed requests when capture is enabled
  • Customer-provided description, category, email, and attachments

Team workflow

Support, product, and engineering can separate signal from noise before anything reaches the roadmap.

  • Triage status, assignment, priority, and internal notes
  • AI-enhanced summary beside the original customer text
  • Reply flow for follow-up questions without exposing private context
  • Linear sync only after the report is worth engineering attention

Customer loop

Customers get a lightweight way to follow progress without seeing your internal tooling.

  • No-login portal links for ticket status
  • Customer-safe conversation history
  • Additional comments and attachments after submission
  • Internal notes, logs, and Linear metadata stay hidden

Works with your stack

The widget stays framework-agnostic so teams can add feedback collection without rebuilding product surfaces.

  • Plain script install for React, Vue, Svelte, Astro, Webflow, and HTML
  • Project token configuration per product surface
  • Public API and signed webhooks for custom automations
  • Native Linear integration today, broader adapters via API

Setup path

From install to first useful ticket.

Installation stays intentionally small, but the production setup is more than copying code. Teams decide what to capture, who can triage, and when a report should become engineering work.

Start Lite trialView pricing
  1. 01Create a project and copy its public widget token.
  2. 02Paste the snippet before the closing body tag or through your tag manager.
  3. 03Choose what technical context should be collected for that project.
  4. 04Submit a test report, review the ticket package, then invite the team.
Production-ready feedback

Start with the widget, keep the workflow.

NOCK is useful from the first report, then grows into the place where customer feedback, technical evidence, and team decisions stay connected.

Start Lite trialDocs