Skip to main content
email·digit
Reply intelligence

Open rate stopped being a measurement.
This is what we score instead.

Apple Mail preloads images for most of its users, so your open pixel fires whether or not anyone looked. A large share of reported opens are software. We record opens and show them, marked unreliable — and we never let them count toward anything.

The signal

A click, a reply, a conversion.

Weighted — a conversion outranks a reply, a reply outranks a click, because that's the order of how much intent each one takes. Then decayed by recency, so a contact who was hot in February and silent since doesn't keep looking valuable in August. The curve saturates, so nobody reaches 100 because a link prefetcher fired forty times.

Automation goals work the same way: a conversion, a reply, an engagement tier moving up. Never an open.

Replies

Somebody wrote back. No amount of image preloading fakes that.

It's also the signal every other tool throws away. It lands in a shared mailbox and dies.

So we read it. Every inbound message is read on six independent axes:

Who's writingWhat it's aboutWhat they wantHow they feelHow urgent it isHow strongly they feel it

Six answers, not one bucket — which is what lets the priority number mean something, and lets an automation trigger on “an angry customer replied about billing” rather than “someone replied”.

Prioritisation

Shown, not asserted.

Each reply gets a 0–100 priority score built from those six axes plus your existing relationship with the sender, and risk flags for things worth surfacing immediately — a legal threat, a chargeback, something escalating. Open the score and you see which factors contributed what. If you disagree, you can see exactly where to disagree.

Context

Classification reads the conversation, not just the message.

Have you emailed this person? Are they a known contact? How many exchanges have there been? A stranger enthusiastically selling you SEO services is a vendor, however positive the language — and it won't pollute your lead segments with a tag it didn't earn. Tools that read each message in isolation get this wrong constantly.

Corrections

It learns your workspace, and only your workspace.

  • Fix it once. Disagree with a reading and correct it. That correction becomes a rule for that sender or that domain, applied deterministically to future messages.
  • Nothing you correct trains a model shared with anyone else. No cross-customer training, at all.
Responding

A dropdown, not a prompt box.

Pick the situation and the most specific playbook wins, assembling the draft in your brand's voice. Anything needing a fact it doesn't have is marked for you to fill in rather than invented. Anything flagged for review or carrying a risk flag is draft-only and cannot be auto-sent, however confident the draft looks.

Downstream

It feeds everything else.

Replies raise engagement scores, trigger automations, update contact health, and appear on the contact's timeline. A weekly digest summarises what came in, with per-person preferences and a one-click opt-out.

The trade-off

The cost of being honest.

Your reported numbers will be smaller here than in the tool you're leaving. Not because less is happening — because we stopped counting the machines.

Reply intelligence

Stop losing
the replies that matter.

A click, a reply, a conversion — weighted, decayed, and never an open.