kvCORE + ShowingTime: What's Possible
kvCORE and ShowingTime do not natively sync showing data in real time. Keeping kvCORE updated after each showing requires middleware that parses ShowingTime confirmation emails and writes to kvCORE via its API. That's the architecture Showing Signal runs on.
How Agents Usually Use Both Platforms
kvCORE is the CRM and lead engine — it holds your contacts, drives your smart campaigns, and tracks your pipeline. ShowingTime is the scheduling layer that sits between buyer's agents and listing agents, managing confirmation and feedback logistics.
In a world where these two systems talked to each other, a showing confirmation would immediately update the kvCORE contact record, trigger a smart campaign, and kick off your follow-up sequence. In practice, that handoff is manual — and on a showing-heavy day, it doesn't happen.
Why There's No Native Integration
ShowingTime, acquired by Zillow in 2021, was built around MLS coordination and listing-side feedback collection. Its architecture has no outbound webhook, no Zapier trigger, and no API surface designed for buyer-side CRM connectivity. kvCORE's API is well-documented on its own end — the problem is entirely that ShowingTime has nothing to push.
This isn't a configuration issue you can solve in either platform's settings. It's a structural gap that requires an external layer to bridge.
What Showing Signal Writes to kvCORE
When Showing Signal parses a ShowingTime confirmation and writes to kvCORE, the following updates fire immediately:
kvCORE Lead: lead_stage → "Active Buyer" last_showing_dt → "2026-08-06T14:30:00Z" showing_count → 3 last_property → "1402 Elm Street" kvCORE Activity: note logged with address + time Smart Campaign: trigger tag applied → campaign fires
Smart campaign triggers are particularly powerful in kvCORE — Showing Signal can apply a tag at the moment of confirmation, which fires your pre-configured kvCORE drip sequence without any additional setup. Your follow-up automation runs entirely inside kvCORE's familiar campaign builder.
What Showing Signal Also Handles
Beyond the kvCORE update, the same showing confirmation event can also trigger Showing Signal's own email sequences — a 3-hour feedback request and a 24-hour nurture if there's no response. These run in parallel to whatever kvCORE campaign fired from the tag.
Cancellations and reschedules are handled automatically — Showing Signal detects the event from the same email stream and suppresses or re-queues every affected workflow without any action from you.