CRM & outreachUpdated 26 Aug 2026

Connections: records that join up, end to end

A quiet audit that every lead has a source and a way to reach it, every deal a customer, and every captured lead a place in your pipeline, counted class by class, with a scheduled re-check.

Connections quietly checks that your records join up end to end (every lead has a source and a way to reach it, every deal has a customer, and every captured lead actually reached your pipeline) and counts anything that slipped through, class by class.

Connections health: records that fell out of the journey (desktop view)
Connections health: records that fell out of the journey

What does it check?

  • Deals without a customer: a deal that lost its client link (serious).
  • Form submissions that never became a lead: an enquiry that stalled at the door (serious).
  • Uncontactable leads: no phone, no email, no way to follow up (serious).
  • Captured leads with no deal: arrived but never entered the pipeline.
  • Leads with no source: money you can’t attribute to any campaign.

The three serious classes drive the health flag; the last two are hygiene. The check also runs on a schedule, so drift is caught even when nobody opens the screen. Re-check any time with one tap.

Open Connections healthRecords that fell out of the journey, counted by class

Frequently asked questions

Can I see which records are behind a number?

Yes. Each finding lists the records themselves, by name rather than by id, and each one opens where you can fix it — a deal opens the deal, a lead opens the customer. Two of the findings are form submissions rather than leads, and a submission has no page of its own, so those open the form they came from, which is where submissions are read. Long lists show the first ten with the true total beside them, so a workspace with thousands is told how many there really are rather than being shown ten as though that were all of them.

A finding shows a count but no records underneath. Why?

The count and the records are fetched separately, so that the number stays right even when the list is capped. If the record lookup cannot run — a permissions change, most often — you still get the count, because knowing something is wrong matters more than being able to click straight to it. Re-check usually clears it.

Does Connections change my records?

No, it's read-only. It counts each orphan class so you know where to look; re-check whenever you like, and a scheduled sweep keeps watch in between.

Related articles