Hotjar Alternative With Tasks and Voice Recording

Hotjar merged into Contentsquare, and new Hotjar accounts can no longer be created. If you are choosing a tool now, this page compares what Contentsquare session replay records with what UserTold records, and says when each one fits. Facts about Contentsquare are taken from its own site in November 2026.

What each tool records

Contentsquare (formerly Hotjar)UserTold
Who is recordedA sample of all visitorsUsers who agree to take a test
What the user is doingWhatever they came to doA task you wrote
What is capturedMouse movement, clicks, taps and scrolls, shown as a replayScreen, clicks and the user's voice
Does the user speakNoYes, they think aloud, and a voice conversation follows the task
How problems are foundHeatmaps, AI summaries of replays, flags for frustrated or lost usersEach moment where the user had trouble is marked with their words, the page and the time
Access for coding agentsAn MCP server that reads dataAn MCP server and a CLI that read each marked moment and create the next test
PriceFree plan; paid plans from $39 a month; Pro and Enterprise on request$0.25 per recorded minute, no subscription

When session replay is the right tool

Session replay and heatmaps answer questions about your traffic as a whole. Replays are kept for a share of sessions that depends on the plan. Use them when you need to know:

  • how far people scroll on a landing page;
  • which element on a page gets the clicks;
  • what a user did before they reported a bug, when that session was captured;
  • how often an error appears across thousands of visits.

It needs no cooperation from the user and works on every page you track. Contentsquare has a free plan, and Microsoft Clarity is free.

What a replay does not tell you

A replay shows a cursor moving. It does not say what the person came to do, so you cannot tell a user who failed from a user who was looking around. It has no sound, so a pause on the pricing table could be reading, doubt, or a phone call.

What a recorded task adds

In UserTold you write the task, for example “Choose the plan you would buy for a team of five”. A widget on your site offers the test to your users. A user who accepts sees the task, does it in your real product and says what they are thinking. The screen and the voice are recorded together. When the task ends, the voice model asks about the pauses and wrong turns it captured.

You know what the user was trying to do because you wrote it. You hear the reason because they said it. The full recording is kept, and the moments where the user had trouble are marked in it so you do not have to watch every minute.

A coding agent can read those moments over MCP or the CLI: the quote, the page and the time. That is enough for it to find the screen in your code and propose a change.

What UserTold does not do

  • It does not record visitors who have not agreed to a test.
  • It has no heatmaps and no traffic statistics.
  • It does not recruit testers. The people in the recordings are users you can already reach.
  • Screen recording works in supported desktop browsers.

You can run both: replay to see where people leave across all traffic, and a recorded task to learn why at that step.

Try it on one page

Pick the page where your replays leave you guessing. Copy the usability test script and task examples, write one task for that page, and run it with five users. The comparison with tester panels is in UserTesting alternative.

Sign in and choose New study, or read the Quickstart first. Prices are on the pricing page.