CRM · Leads

Follow-ups that
go overdue loudly.

A follow-up with a date is only useful if something notices when the date passes. Due and overdue are queries here, not a state of mind — and the whole timeline of a lead, including every engagement event, is readable in one place.

Most CRMs record what you typed. This records what happened: transitions, dispositions, engagement events and who the lead moved between.

Where it is

Journey status, with allowed transitions.

Transitions are constrainedA lead cannot jump from new to won without the steps between, so the funnel means something when you report on it.
DispositionsWhat actually happened on the call — recorded as a value rather than a note somebody may or may not have written.
Journey metadataThe statuses and transitions themselves are configuration, so the process can match your business rather than the other way round.
The chase

Due, and overdue.

Follow-ups with datesCreated against the lead, completed explicitly, and removable when they stop mattering.
Due todayThe list that decides the morning.
OverdueSeparated deliberately, because a follow-up two weeks late is a different problem from one due this afternoon.
Changing hands

Transfers, requested and approved.

Transfer requestsA rep asks for a lead to move rather than taking it, and someone approves or rejects.
Both outcomes recordedA rejected transfer stays visible, which is what stops the same argument happening twice.
The record

A timeline you can read.

Full timelineEvery status change, call, follow-up and transfer in sequence.
Engagement eventsWhat the lead did — opens, clicks, replies — alongside what your team did.
Assignment historyEvery owner this lead has had, with dates.
Nearby

Related capabilities.

Lead management · Calls and dialler · Sequences

The whole story, in order.

Not a notes field somebody remembered to fill in.

Get started → See pricing