All posts

HOW WE USE HUMAN BEHAVIOR

How we use Human Behavior

The SDK runs on our dashboard and on this site, so the sessions being recorded are ours. Here is what it actually found, and what changed because of it.

Engineering

Nobody files a ticket for a button that quietly does nothing. They click it twice, decide the product is broken, and leave. Every defect below was caught the other way: in our own recorded sessions, on our own dashboard. Not one of them arrived as a bug report.

Clicking an insight card did nothing

The KPI cards on the overview changed the cursor on hover, so people clicked them expecting to drill in. Nothing happened. Most tried two or three times and moved on.

Insight cards looked clickable but went nowhere
human-behaviorbotflagged this in a session replay
+1−1
@@ -14,3 +14,3 @@ function CardBody({ item }) {
1414 <div className="card cursor-pointer">
15− <CardBody item={item} />
15+ <Link href={href}><CardBody item={item} /></Link>
lowcursor-pointer with no navigation

The card advertised interactivity with `cursor-pointer` but had no link behind it, so clicks did nothing and people left the page. Wrap the body in the real destination.

These aren't illustrations. Every one is a real commit in the Human Behavior product: the agent found the defect in our own sessions, wrote the patch, and opened the branch with the replay link attached — one of us read it and merged.

None of that reaches a person by hand. A long-running agent watches the issues filed from Human Behavior and assigns them in Linear by signal type — session-replay bugs to one person, exceptions to another, vitals and funnel drops to the rest — with the replay already attached. It was set up by describing it in a sentence.

humanbehavior.co/agents/new
BackNew chat
Route the issues we file from Human Behavior in Linear by signal type, and tell the team in Slack when you assign one.
Human Behavior

Set up. It watches new issues, assigns by signal type, and attaches the replay link. Slack is added as a channel so it replies in #eng-signals, and Linear and GitHub are connected. Check the setup on the right before you create it.

Message your agent…

New agent
CreateAutomationsPreview

Agent setup

Name your agent and tell it what to do — that's it.

Appearance
Agent name*
Issue triage

You'll @mention your agent by this name wherever you chat with it.

Channels
Always on

Human Behavior

Chat with your agent.

#eng-signals

Replies to mentions

Instructions

Open each new issue filed from Human Behavior in Linear and assign by signal type: session-replay and rage-click bugs to Riley, JS exceptions and error groups to Jordan, web-vitals and layout-shift issues to Casey, funnel drop-offs to Avery. Always attach the replay link, and cross-link the fix branch from GitHub when it opens. Keep priority as you scored it unless a human changes it.

3 connectors connectedConnectorsMemory

The builder that created the router. It assigns and attaches evidence; it does not close tickets on its own.

Design

2025 used the same design system as today, but put a long company questionnaire in front of the product — industry, role, phone, a 120-character essay, and a pedantic https:// check — before anyone saw value. Replays showed people stalling and bouncing. Today is three light fields about you, then in.

humanbehavior.co/get-started

Welcome to Human Behavior

About you
Job title*
e.g. Product Manager
Company name*
e.g. Human Behavior
Company size*
Select company size
Next
1Company Details
2Connect SDK
3Payment

Tell us about your company

Complete every required field so we can provision your workspace. This usually takes 3–5 minutes.

Company name*
Acme Inc.
Industry*
Select industry
Website URL*
acme.com

Must include https://

What does your company do?*47 / 120
We build tools that help developers ship faster — session replay, product analytics, and error monitoring in one place, so teams can see why users drop off without watching hours of footage…

Min. 120 characters. Be specific about your product, buyers, and use case.

Company size*
Select company size
Your role*
Select role
Work email*
you@acme.com
Phone
+1 (555) 000-0000
How did you hear about us?*
Select one…
6 of 8 required · 47 / 120 charsContinue
2025Today

Left and right share the same tokens and controls. The difference is field count and copy before the product — not a different brand.

Customer success

We find out someone hit a bug before they tell us, which means we get to apologise first.

# customer-signals
Tuesday, June 16
Human BehaviorApp2:14 PM

Aliyan (Assemble) hit the same 403 five times in the last 40 minutes on Team → Permissions. He reloaded twice, then closed the tab.

Renews in 9 days. No ticket filed.

Replay · 4m 12s · Chrome 141 · macOS

  • • 3 rage-click clusters on “Invite member”
  • • GET /api/projects/assemble/members → 403 ×5
  • • Scoped to this org — no other account affected
Sam2:18 PM

I'd rather he hear it from us than hit it again tomorrow. Reaching out now.

Sent: “Hey Aliyan — we saw you run into a permissions error on the Team page a couple of hours ago, and we're sorry. That one's on us: a change we shipped last week stopped admins invited after the migration from loading the members list. Fix is in review and goes out this afternoon. Nothing for you to do.”

Human BehaviorApp5:02 PM

Deployed. Aliyan has loaded Team → Permissions twice since with no errors. Marking resolved.

Lightly edited for length. We stopped asking “can you reproduce it?” — the replay is already in the thread.

Delivery

Every evening I get one SMS — a daily usage summary in bullet points. Sessions vs yesterday, conversion, new issues, loudest rage-click. Anything that isn't urgent waits for the seven-day email on Monday, and only something that genuinely needs a person that day earns a Slack alert.

Text Message · Monday · 8:01 PM

Hey — here's your Human Behavior summary from today: • 1,642 sessions (+4% vs yesterday) • Checkout conversion 68% (−1 pt) • 1 new issue · top rage-click: Export CSV

Text Message · Tuesday · 8:01 PM

Hey — here's your Human Behavior summary from today: • 1,842 sessions (+12% vs yesterday) • Checkout conversion 71% (+3 pts) • 3 new issues · top rage-click: Team → Invite member

Text Message · Wednesday · 8:01 PM

Hey — here's your Human Behavior summary from today: • 1,910 sessions (+4% vs yesterday) • Checkout conversion 72% (+1 pt) • 0 new issues · loudest funnel drop: Billing → Confirm

Three consecutive evenings. No threshold alerts — just the digest, so I know how the product did without opening a dashboard.

Colophon

This page is built out of the product. The carousel, the progress pager, the drag handle, the tooltips, and the two screens above all use the same components the dashboard renders — the marketing site is an extension of the app, not a copy of it. It is also instrumented: rage-click something here and it lands in the same queue as everything in Engineering.