1
Send PostHog events in
Usercall's SDK takes in events PostHog already captured, including autocapture and events you capture yourself.
Integrations · PostHog
Talk to PostHog users when behavior changes
PostHog shows the page, the click, and the error. It does not ask why. Usercall's SDK takes in the PostHog events you already capture. You use one as a research trigger, and that person gets a short AI-moderated voice interview right then.
The interview uses a PostHog event you already capture.
2 to 5 minute interviewsWorks from events you already trackTranscripts and analysis
Trusted by research, product and CX teams at
How it works
Capture the event. Ask the person. Read the transcript.
You keep the PostHog project you already run.
2
Create the research trigger
Pick the moment: usage dropped, a skipped step, a feature left behind, or a cancel visit. Choose who to ask, and set the limits.
3
Read the transcript and the analysis
The interview is a short AI-moderated voice conversation. The PostHog event stays attached to the answer.
Example triggers
Moments worth asking about
Each row is a moment. The note names the PostHog event when PostHog already has one.
Drop in usage
Use the usage event you already capture. Ask what changed.
Fewer logins
Use the login event you already capture. Ask why they came back less.
Skipped onboarding step
$pageleave on a setup page. They left the step. Ask what confused them.
Feature abandoned
$dead_click, or $pageleave on the feature. Ask what they were trying to do.
Downgrade
Use the downgrade event you already capture. Ask what the larger plan was not doing.
Cancel page visit
$pageview when $current_url is the cancel URL. Ask why.
Failed payment
Use the payment event you already capture. Ask what happened.