Stop guessing who is on your site.

Ninety-eight people read your pricing page. Two filled in the form.

One first-party script shows you who is on your site right now, draws a map of where they click and where they quit, and records the sessions that went wrong — with every keystroke masked in the browser before a single byte is uploaded.

Start 30 days free $0 today · no contract · cancel any time

Unlimited calls, texts, emails and contacts

Everything else in Chirply comes with it

The problem is not that it is hard.

It is that nobody has the hours, and the cost of skipping it never shows up as a line on any invoice.

Traffic is not a person

A pageview count cannot be called, emailed or put in a pipeline. The most interested visitor you had this week left without ever becoming a name.

You redesign on opinion

With no picture of where people click and where they stop scrolling, the page changes reflect whoever argued hardest in the meeting — and the next version fails in a brand new way.

The bug only ever happens to other people

Something breaks for a slice of your visitors, they leave, and nobody files a ticket. It works on your machine, so it stays broken for months.

Set up once. It runs from then on.

Install

One snippet, three views

A lightweight first-party tracker goes on the site once. Heat maps and session replay run off that same script, so turning one on never adds a second snippet to your pages.

Identify

Watch live, and keep the history

A live visitor board with page and session context, UTM, referrer, click-id, device and geography — plus anonymous history that merges into the known person the moment they identify themselves.

Diagnose

See the page the way they saw it

Click density with a ranked list of the elements taking the most hits, rage clicks flagged when someone jabs the same small area three times in quick succession, and a scroll curve with a fold line marking where half your visitors stop reading. Separate maps for mobile, tablet and desktop.

Recover

Answer while they are still on the page

A branded chat widget catches the question in the moment, AI handles the routine turns, and a human takes over with the visitor's identity and click path already on screen.

Every piece of this is already live.

These are not roadmap items. Each one is running in production today, described here in the same words the full product catalog uses.

Website visitor intelligence

See buying intent before the form arrives.

Install a lightweight first-party tracker and watch live visitors, sessions, pages, traffic sources, campaigns, and returning people across every connected site. The same tracker feeds the heat maps and session replay below — one script, three views of the same behaviour.

Live visitor board with page and session context
Anonymous visitor history that merges into a known person later
UTM, referrer, click-id, device, and geography context
Per-person and per-site activity timelines

Heat maps

See where people actually click, and where they give up.

Click and scroll maps for any tracked page, aggregated as visits happen rather than reconstructed one session at a time — so a thousand visits fit in a single picture and you can still tell which button people are hammering.

Click density plus a ranked list of the elements taking the most hits, each with its share of the total
Rage clicks flagged when someone jabs the same 30-pixel area three times, each click within 700ms of the last — usually something that looks clickable and isn't
A scroll-depth curve with a fold line marking where half your visitors stop reading
Separate maps for mobile, tablet and desktop, because the layout they saw was not the same one

Session replay

Watch the session that went wrong, without recording anything private.

Turn it on for a site and Chirply records visits as a replayable document. Every input is masked in the browser before a single byte is uploaded, so what comes back is behaviour — never keystrokes.

Off by default and enabled per site; a site not using it never even downloads the recorder
Retention you choose from 1 to 365 days — 30 by default — with expired recordings purged automatically
Player at 1x, 2x, 4x and 8x with inactivity skipped, so a nine-minute session watches in about one
Every keystroke masked in the browser before upload; add data-redact or the block class to exclude whole regions

Live chat & AI handoff

Capture the question while the buyer is still on the page.

Embed a branded chat widget, answer from the Chirply inbox, let AI handle routine turns, and take over with the full visitor and conversation context intact.

Multiple widgets with their own branding and status
Shared human inbox with close and takeover controls
AI-to-human and human-to-AI handoff
Visitor identity and click-path context beside the conversation

This is the part of Chirply that solves visitor intelligence. See the other 14 areas — CRM, scheduling, messaging, automations, funnels, commerce, reputation and the rest — all included in the same workspace.

Try it on your own business for 30 days.

You do not have to migrate anything to find out whether this works. Start the trial, set up the one thing you came here for, and judge it on that.

$0 charged today. A card holds the workspace; nothing moves until day 30.

Unlimited usage. Calls, texts, emails and contacts are uncapped on every plan.

Your providers, your rates. Bring your own Twilio, Mailgun and AI keys and pay them directly — we do not mark usage up.

No contract. Cancel before day 30 and you are never billed.

Your trial runs on Scale, the top plan, so nothing is locked while you evaluate. If visitor intelligence is all you need afterwards, Scale at $97/mo carries it — switch down before the trial ends and keep the lower price.

The questions everyone asks.

Which plan do I need?

Scale, at $97 a month, because session replay is a Scale feature — and Scale is what your 30-day trial runs on. If you can live without replay, visitor intelligence, heat maps and live chat all start on Grow at $77.

Is recording sessions a privacy problem?

Every input is masked in the browser before a byte is uploaded, so what comes back is behaviour and never keystrokes. Replay is off by default and enabled per site — a site not using it never even downloads the recorder — retention is yours to set from 1 to 365 days with 30 as the default and expired recordings purged automatically, and a data-redact attribute or the block class excludes whole regions.

How is this different from Hotjar?

The visitor is a contact. An anonymous session merges into the person it turns out to be, so a replay sits beside their calls, texts, deals and invoices instead of in a separate analytics tool somebody opens on Fridays.

Do I need thousands of visits before it is useful?

Heat maps aggregate as visits happen rather than being reconstructed one session at a time, so a thousand visits fit in one picture. Below about 30 views you get a plain warning, because nobody should redesign a page off the back of four visitors.

Do I have to watch a nine-minute session for nine minutes?

No. The player runs at 1x, 2x, 4x and 8x with inactivity skipped, so a nine-minute session watches back in about one.

Weighing it against something specific?

Ninety-eight people read your pricing page. Two filled in the form.