kvCORE Integrations: Get Every Lead In With Source and Routing Intact.

kvCORE integrations work three ways: native connectors for platforms like Facebook Lead Ads and your IDX website, a lead parsing email address that turns forwarded lead notifications into contacts, and Zapier or webhooks for everything else. The goal is not just getting the contact into the database but getting it in with the source recorded, the routing rule fired and the Smart Campaign started, inside five minutes of the inquiry. This piece walks through each entry path, how routing and campaigns depend on the source field, the setup steps we use, and the failures that quietly cost brokerages leads every month.

A kvCORE integration is any connection that creates or updates a contact in kvCORE (now sold under the BoldTrail name) without an agent typing it in. That matters because once a human types a lead in, the source, the timestamp and every automation downstream depend on that human.

How leads enter kvCORE.

There are exactly three doors into kvCORE, and every lead source you run uses one of them. Native connectors are built into the platform: your kvCORE IDX website, the open house app and the Facebook Lead Ads connection all write contacts directly with the source already set. The lead parsing address is a unique email address assigned to your account; any lead notification email forwarded to it, from a portal, a third-party landing page or a sign-call service, gets read and turned into a contact. Zapier and webhooks cover everything else: any tool that can fire a webhook or has a Zapier trigger can create a contact with whatever fields you map.

• Native connectors: source set automatically, routing fires, Smart Campaign trigger works from the arrival tag.
• Lead parsing address: source usually set from the sender, phone sometimes missing, duplicates common when a portal sends a second notification for the same person.
• Zapier or webhook: you set source, tags and agent explicitly, so routing and campaigns work only if the field map is right.
• Manual entry or CSV import: no reliable source, no routing, and campaigns start only if someone remembers to add the tag.

Map every lead source before you connect anything.

Before touching a single integration, we build a one-page source map: every place a consumer can raise a hand, which door it uses, what the source value will be, which routing rule should catch it and which Smart Campaign should start. A typical brokerage has more sources than the broker thinks: the IDX site, portals, Facebook and Instagram lead forms, Google Ads landing pages, the open house app, sign calls, and a mortgage partner who sends names by email.

The map forces two decisions. First, a fixed vocabulary for the source field. If Facebook leads arrive as Facebook, FB Lead Ad and Meta depending on who set up the connection, no routing rule matches all three and no report groups them. Second, which sources deserve a human first touch versus an automated one. Portal leads and paid social leads need a phone call. A newsletter signup does not.

Step by step: wiring the common sources.

Routing rules by source, price and zip.

kvCORE lead routing assigns new contacts to agents based on conditions you set: the source, the price range of the property or saved search, and the zip code or area. Rules are evaluated in order, so the sequence matters. We put the narrow rules first (a specific source plus a specific zip going to the team lead who farms that area) and the broad catch-all last.

Two routing patterns work well. Round robin spreads volume evenly, but it hands a lead to whoever is next even if that agent is sitting in a closing. First to claim pushes the lead to a group and gives it to the first agent who accepts, which rewards responsiveness and routes around agents who are busy. For paid leads, first to claim wins because it turns the five-minute window into a competition inside the team.

Smart Campaigns start on a tag.

Smart Campaigns are kvCORE's behavioral drip sequences: a series of texts and emails that adjust based on what the contact does, such as viewing listings or saving a search. The cleanest trigger is a tag applied on arrival. That is why the source map assigns an arrival tag to every source: the tag is what connects this lead came from a Facebook buyer campaign to send the buyer sequence, not the seller sequence.

Keep the arrival tags coarse. A handful (buyer-paid, seller-paid, buyer-organic, sphere, open-house) is enough to pick the right campaign, and coarse tags survive staff turnover. Never start a Smart Campaign from a manual step, because manual steps are exactly what gets skipped on a busy Saturday.

Speed to lead is the whole game.

Every integration above exists to shorten one interval: the time between a consumer submitting a form and a human agent reaching them. Our standard is first response inside five minutes, by phone call and by text at the same time, during any hour the brokerage advertises. Online leads go cold within minutes because the consumer usually submitted to several sites at once, and the first agent who calls gets the conversation.

The wiring supports this in three ways. Native and Zapier entry means the contact exists seconds after the form is submitted, not after someone checks an inbox. Routing means a specific person is notified, not a shared pool. And the arrival tag fires the first text before the agent has picked up the phone. We covered the operating side in our speed to lead guide, and it is the backbone of what we build for real estate brokerages.

Call tracking on listing sites and signs.

Most of the lead flow above is form-based, but a large share of listing interest arrives as a phone call: the number on the yard sign, the listing page, the open house flyer. If those calls ring a cell phone directly, kvCORE never learns they happened, the source is lost, and the contact exists only if the agent types it in later.

The fix is a call tracking layer such as CallRail in front of every published number. Each source gets its own tracking number, calls are recorded and logged, and a Zapier step creates or updates the kvCORE contact with the caller's number and the source of the line they dialed.

What usually goes wrong.

• Spreadsheet imports that wipe the source. An agent imports a portal or event list as a CSV; every row lands with a blank or generic source, no routing fires.
• Duplicate contacts from phone-versus-email mismatch. The Facebook form captured an email, the sign call captured a phone, and kvCORE now has two records for one person.
• Facebook lead forms with no phone field. The lead exists but cannot be dialed or texted, so speed to lead is impossible.
• No call tracking on listing sites. Sign calls and listing-page calls go straight to cell phones and never appear as leads, so the highest-intent inquiries are the least measured.
• Routing rules in the wrong order. A broad catch-all sits above a narrow rule, so the team lead who farms a zip never receives leads from it.
• Expired connections. A Facebook page token or a portal email template changes, the connector stops silently, and the gap is found weeks later.

kvCORE vs Follow Up Boss.

The alternative we are asked about most is Follow Up Boss. kvCORE bundles the IDX website, the CRM and the campaigns in one platform. Follow Up Boss is a CRM only, but it has a stronger open API, a large set of native integrations, and a lead email parsing system that many portals and lead vendors support directly. The table compares the entry paths, because the path decides what survives.

Whichever platform you run, the discipline is the same: one door per source, a fixed source vocabulary, routing built before campaigns, and a quarterly test lead through every path. That discipline is most of what we deliver when we build lead systems for brokerages.