investigation

A desk check, not a chatbot.

Tickets come in by email, Slack, or inside your app. Hinto names what to read, fetches that evidence, states a cause with honest confidence, and drafts a reply your team still sends.

Get an invite

case file · checkout

ticket

I picked monthly at checkout and got charged the yearly price.

the desk

Watch one brief fill in.

Same checkout ticket throughout. Each step adds one field to the case file. Scroll to see what lands on your desk.

case file · checkout

ticket

I picked monthly at checkout and got charged the yearly price.

Start with what the customer actually said.

  1. the ticket

    The ticket is not the repro.

    An email, a Slack thread, or an in-app message names the pain. It rarely says which session, which errors fired, or which commit was live.

    Start with what the customer actually said.

  2. context selection

    First it names what to read.

    This is the hard part. Hinto decides which session, which errors, and which files belong on this ticket before it fetches anything.

    Name the evidence before you open a tab.

  3. evidence

    It fetches only those sources.

    The customer's timeline from Hinto Signal, errors from Sentry, code from GitHub at the commit that was live. Nothing else.

    Read what you named. Skip the rest.

  4. honesty

    It writes down what it could not check.

    Every investigation records coverage gaps. A missing connector is a fact on the case file, not a silent guess.

    Say what you did not have.

  5. cause

    It names a cause and how sure it is.

    Probably is a real answer. Hinto states the likely cause and its confidence honestly instead of dressing up a guess.

    Tie the cause to evidence you fetched.

  6. reply

    It drafts a reply. You send it.

    A person on your team reviews the draft, edits it if needed, and presses Send. The reply goes back where the customer wrote.

    Draft for a human. Never auto-send.

  7. handoff

    Engineers get the same brief.

    When the fix needs engineering, your coding agent can pull the investigation over MCP. Linear is a person hitting Escalate, not an automatic file on every run.

    Hand off evidence, not vibes.

who investigates

Hinto's agent or yours.

Same inbox either way. The fork is who runs the desk check when a ticket opens.

Who runs investigations

Wade stays at the board.

15 investigation runs included each month, then usage-based pricing. Set a cap in Settings. At the cap, new investigations pause. Tickets still open.

case file · checkout

ticket

I picked monthly at checkout and got charged the yearly price.

chosen to read

  • Priya's checkout session
  • Sentry errors in the ticket window
  • plan-options.ts at the commit that was live

checked

  • Session timeline through Pay and Billing
  • Sentry issue checkout-price-mismatch
  • plan-options.ts maps monthly UI to yearly price id

could not check

  • Stripe charge metadata (not connected)

probable cause

The checkout form maps the monthly selection to the yearly Stripe price id.

probably · 68%

drafted reply

You picked monthly at checkout and were charged the yearly price. That is our bug, not anything you did. We are refunding the difference today.

engineering handoff

Engineers can pull the same brief over MCP or file a Linear issue when someone hits Escalate.

Wade at the evidence board

people mix these up

Straight answers.

  • The investigation agent is the Inbox chat assistant.

    The investigator runs on the ticket once. The Inbox side chat helps your team draft or explain after the brief lands.

  • MCP, bring your own agent, and the investigator are the same thing.

    Hinto's investigator fills the brief. MCP lets your coding agent pull it. Bring your own agent (BYOA) replaces the investigator with your own worker.

  • Hinto auto-replies to customers.

    Hinto drafts. A person on your team presses Send in Inbox, and the reply goes back by email, Slack, or in-app.

  • Every investigation files a Linear issue.

    Linear is an Escalate action someone chooses. MCP pull is separate from filing an issue.

  • Bring your own agent means connect Cursor over MCP.

    Cursor over MCP is engineering handoff. OpenClaw and Grok Bot are bring-your-own-agent workers Hinto wakes when a ticket opens, not MCP handoff.

  • With bring your own agent you still get Hinto's desk check.

    While your agent is connected, Hinto's investigator does not run. Inbox, intake, and human send stay.

  • Low confidence means the run failed.

    An honest I could not determine the cause is a successful outcome. Bluffing is the failure mode we refuse.

get started

Start investigating tickets

Private beta. Invite only.

Get an invite