Why your kvCORE database is full of dead leads

The import that goes nowhere

Say a team of 12 agents joins a brokerage. Each agent brings a contact list — past clients, open house registrations, old portal leads, business cards from two years of networking. The broker imports everything into kvCORE in a batch. Two weeks later, nobody is touching those records.

This is not a motivation problem. It is a data problem. The contacts arrived without pipeline stages, without source tags, without lead scores, and without any activity history. kvCORE has no way to tell an agent which of those 800 contacts is a serious buyer from six months ago and which is someone who clicked a Facebook ad in 2023 and never responded. When the system cannot prioritize, agents default to working the new leads coming in from active campaigns and leaving the imported database untouched.

Over time, that imported database becomes dead weight — it occupies space, skews reporting, and occasionally generates awkward automated emails to people who sold their home two years ago.

What actually makes a contact workable

For an agent to confidently work a contact in kvCORE, three things need to be true. First, the contact needs a stage — something that tells the agent where this person is in the buying or selling process. Second, it needs a source tag so the agent understands the context of the relationship. A past client requires a different approach than a cold portal lead. Third, it needs a next action, which in kvCORE means an active Smart Campaign or a manually set follow-up task.

When contacts arrive in bulk, none of those three things exist by default. The import wizard does not assign stages automatically. Source tags require a field that was either blank in the import file or mapped incorrectly. And Smart Campaigns do not attach themselves — someone has to trigger them.

The result is a database that looks large and healthy in the contact count but is functionally unusable.

The cleanup layer most brokerages skip

Before attaching any automation to a CRM, the data has to be in a state where automation produces useful output. Running a Smart Campaign on 3,000 untagged, unstaged contacts does not warm up cold leads — it generates unsubscribes and spam complaints.

The cleanup process for a kvCORE database typically has three passes. The first pass is deduplication: identifying contacts that appear more than once under different email addresses or phone numbers. kvCORE has a built-in duplicate finder, but it only catches exact matches. A contact imported as "Mike" and another as "Michael" with the same phone number will both survive the automated pass.

The second pass is segmentation. This is the one that takes the most judgment. Contacts need to be sorted into broad buckets — past clients, active pipeline, dormant leads, vendor contacts, and so on — before any stage or campaign logic applies. A rule-of-thumb approach works at scale: if the last activity date is more than 18 months ago and there is no closed transaction in the record, the contact moves to a long-term nurture bucket rather than an active pipeline stage.

The third pass is source tagging. Even if you cannot reconstruct exactly where every contact came from, you can usually make reasonable inferences. Contacts with a Zillow or Realtor.com email domain in the notes field came from portal leads. Contacts with no notes and no activity date at all likely came from a business card import or a prior brokerage roster.

Once those three passes are complete, the database is in a state where Smart Campaigns, lead scoring, and automated follow-up sequences will produce meaningful results instead of noise.

What AI can do after the cleanup

Once contacts are tagged and staged, there is a clear role for AI-assisted workflows inside kvCORE. Lead scoring can be applied to segment contacts by engagement signals — email opens, portal searches, property saves — and surface the ones that have shown recent intent. Follow-up sequences can be differentiated by stage, so a dormant 2023 lead gets a low-frequency nurture drip while an active buyer pipeline contact gets a high-frequency sequence.

For bilingual brokerages, an AI layer can also route contacts to Spanish-language sequences based on the contact's preferred language field, without requiring agents to manually sort their pipelines.

The point is not to replace the agent's judgment. It is to make 800 imported contacts manageable for an agent who has 20 active deals and cannot manually review every record.

Where to start

Run a kvCORE report filtered to contacts with no stage assigned and no activity in the past 12 months. Export that list and sort it by last activity date. The goal is not to delete those contacts — it is to make a deliberate decision about each segment. Contacts with a closed transaction in their history go to a past-client nurture campaign. Contacts with portal lead history but no response after three touches go to a 90-day re-engagement sequence. Everything else moves to a long-term low-frequency drip. That decision logic, once documented, becomes the foundation for a data audit before any AI layer is added. Real Estate AI Group's standard starting point on any CRM engagement is exactly this audit — you cannot automate your way out of disorganized data.