Skip to main content
Klipy creates a contact or company record automatically when someone new shows up in a conversation your delegations have already read, then enriches it from public data when available. Enrichment fails silently, leaving fields blank with no error. Deals surface the same way, from a qualification pass or a delegation’s own judgment.

How does a contact or company record appear?

A new person or company record isn’t a separate always-on process — it’s a byproduct of whichever delegation just read the conversation. When Triage & log emails processes a new sender, Triage & log messages processes a new LinkedIn or WhatsApp contact, or Take meeting notes processes a call with someone new, Klipy creates the matching person and, if the domain is new, the matching company record at the same time. Turn that channel’s delegation off, and new people from that channel stop generating records the same way reading itself stops. The one exception, again, is the one-time backfill: connecting an inbox for the first time creates interaction, contact, and company records from your recent email history immediately, without any delegation needing to be on yet. See How does Klipy read my conversations? for exactly which delegation covers which channel. You can also add a person or company yourself — one at a time, or in bulk via CSV import — for cases where you want the record to exist before any conversation happens, like a target account you haven’t emailed yet.

How does enrichment work, and why is it sometimes blank?

Once a contact or company record exists, Klipy tries to enrich it — filling in fields like industry, role, social links, or company size from public data. Enrichment is optional in the literal sense: if it doesn’t find data, the field is simply left blank, with no error message, no warning icon, and no note anywhere on the record that an attempt was made and came up empty. There’s no re-enrich button either — Klipy doesn’t automatically retry a domain or person that previously came back empty, and there’s no control to trigger another attempt yourself. Every field is directly editable regardless of whether it came from enrichment, manual entry, or CSV import, so typing in what you already know is the fastest way to complete a blank field. See Why is a company’s enrichment data empty? for the exact provider order Klipy checks before giving up, and How do I manage companies in Klipy? or How do I manage people in Klipy? for the full field list on each record type.

How does a new deal show up in my pipeline?

A deal can appear in your pipeline two ways, and both are downstream of the same delegations covered above. First, a deterministic qualification check runs right after Klipy processes an email, message, or meeting: if the conversation confirms enough qualification criteria and there’s no open deal yet for that contact, Klipy proposes creating one. Second, a delegation running its own judgment over a conversation can flag a “concrete untracked buying opportunity” the same way. The one-time backfill on first connect also runs its own single deal-discovery pass, independent of any delegation. None of these three paths writes the deal directly by default — they land in your suggestion queue as a create_deal suggestion for you to approve, unless the delegation that produced it is running in Auto mode. See What does Klipy suggest, and when? for the full suggestion taxonomy, including how deal suggestions differ from stage-change suggestions. Moving a deal to a different pipeline stage is a separate matter entirely. That only ever comes from a delegation running in Suggestion mode calling for it explicitly — nothing in the capture-and-CRM-fill flow above moves an existing deal’s stage on its own.

When to contact us

If a person you know emailed a connected inbox, or a company you’ve clearly talked to, never shows up as a record in Klipy, reach out through the Get help option in Klipy’s Help menu — that’s a gap in the delegation pipeline worth checking, not just an enrichment miss. If it’s specifically a field staying blank on a record that does exist, that’s expected enrichment behavior, not something to report. Before reaching out, check that the delegation covering that conversation’s channel is actually Enabled, not stuck on Needs Configuration — a missing record is far more often a disconnected channel than a bug in record creation itself. If you’ve confirmed the delegation is running and a record still hasn’t appeared after a reasonable amount of time, that’s worth a message with the specific contact, company, or conversation you expected it from. The same check applies to a deal that never surfaces as a suggestion: confirm the relevant delegation is enabled and not set to Auto mode (which would apply the write directly instead of queuing it) before assuming something went wrong.
No, there’s no separate switch for it. It happens automatically as a byproduct of Triage & log emails, Triage & log messages, or Take meeting notes processing a conversation with someone new — turning off the relevant delegation stops new records from that channel too.
Enrichment either wasn’t attempted or didn’t find data, and it fails silently with no error shown anywhere on the record. The field stays blank until you type it in yourself.
No. Klipy doesn’t automatically retry enrichment for a record that previously came back empty, and there’s no button to trigger another attempt. Editing the field directly is the fastest fix.
By default it lands as a create_deal suggestion in your suggestion queue for you to approve — Klipy doesn’t write it directly unless the delegation that produced it is set to Auto mode.
The one-time backfill that runs when you first connect an inbox creates contact and company records from your recent email history right away, so you aren’t starting with an empty CRM.
Last modified on July 30, 2026