Native support that knows what they did and finds out why.
Hinto Signal records what each customer did, and every ticket arrives with the likely cause, how sure Hinto is, and a drafted reply. By email, Slack, or right inside your product.
Maya exports a CSV from Acme, a sample app with Hinto Signal.
three ways in
Three ways in. One Inbox.
Every ticket lands in the same place, however it came in.
Your Hinto mailbox is ready at sign-up. Forward support@ to it. Replies go out from Hinto.
on every ticket
What lands on every ticket
An answer is only as good as what it looked at.
Hinto picks the session, the errors, and the code each ticket needs. Then it answers.
One plain sentence. A confidence word with its percent, so you know how sure it is.
hinto signal
See what they tried
Hinto Signal records a text timeline of what signed-in customers did. It is not a video of their screen.
Mark your key flows with hinto.journey(key). The ticket shows how far the customer got and where it failed.
who investigates
Your agent or ours
Hinto's investigator runs on every new ticket. Already run an agent? Hinto can wake yours instead.
Either way, your coding agent can pull any investigation over MCP.
How investigation worksHinto's investigator
15 runs a month included, then priced per run.
Grok Bot
A Cursor automation. Hinto wakes your routine and the findings come back to the ticket.
Claude Code routine
A routine in Claude. Hinto wakes it through its API trigger and the findings come back to the ticket.
Any HTTPS worker
Hinto sends a signed webhook. Your worker posts its findings back.
why we are building this
Deflection is not an answer.
Support did not get harder because customers got needier. It got harder because products got deeper, and the ticket never says what actually happened.
The industry's answer has been deflection: a bot that stands between your customer and an answer, hoping they give up. We think that is backwards.
Every ticket deserves an investigation. No human should have to run one by hand. You stay the human who replies. Wade does the digging.
pricing
One plan. You set the cap.
$59
- Unlimited tickets and seats.
- 15 investigation runs included each month.
- Bring your own agent and 50 runs are included.
After that, per run
- 16–50 runs: $3 each
- 51–200 runs: $2 each
- 201+ runs: $1 each
Questions
Does Hinto reply on its own?
No. Hinto drafts the reply. A person on your team reads it and presses Send.
What does it read?
Only what you connect. The ticket, the customer's Signal timeline, Sentry errors, and your GitHub code, read-only.
What happens when it is wrong?
It says how sure it is and what it could not check. A low-confidence answer reads as a lead to check. You decide what to send.
Does it record my users' screens?
No. Hinto Signal records a text timeline of pages, clicks, and failed requests. No video, and never what people type.
Where do replies go?
Back where the customer wrote. Email goes out from your Hinto mailbox. In-app replies land in your product. In a customer Slack channel the reply posts in the thread. In an internal channel you copy it and mark it sent.
Start with your next ticket
Hinto is in private beta. Invite codes go out one at a time.
Get an invite