kvCORE
Planned: add leads, log notes and schedule calls in kvCORE (BoldTrail) by text between showings.
Not available yet. This page describes what's planned for kvCORE. Ask in your thread and we'll text you when it's ready.
Status: planned — not available to connect in Tack yet. These steps prepare the integration; creating vendor credentials does not enable it in the app.
Planned workflows
Section titled “Planned workflows”Planned for kvCORE:
| You text | What would happen in kvCORE |
|---|---|
| “New lead: Sam Lee, 3 bed under 450k” | Adds the lead |
| “Showed 22 Birch to the Parks” | Adds a note |
| “Remind me to call Jane Friday” | Schedules a call |
These are intended workflows, not a guarantee that every operation is exposed by the vendor. Each must pass the API and permission checks below before release.
Before you start
Section titled “Before you start”Identify the customer’s kvCORE/BoldTrail account, brokerage and intended agent. Use the CRM API, not the separate property-listings API. The kvCORE Public API V2 reference requires a token generated for the application user.
Developer setup — once
Section titled “Developer setup — once”- Map lead creation, contact notes and call scheduling separately to the current Public API V2 endpoints. Do not assume a general task endpoint exists.
- Define contact ownership, duplicate matching and lead-source rules with the brokerage.
- Build encrypted token storage and a renewal/revocation procedure before onboarding.
Customer setup — repeat for each authorized account
Section titled “Customer setup — repeat for each authorized account”- Ask the brokerage admin which user should own the token and what contacts that user may access.
- Follow Inside Real Estate’s API token guide. The existing setup route is Lead Engine → Lead Dropbox → My API Tokens; the current help page could not be retrieved during this review, so have the admin confirm that route and the available controls in their account.
- Generate a dedicated token with only the required available permissions. Confirm contact writes and the intended note/call operations rather than selecting all access without review.
- Save the token securely and record its owner, scope and displayed expiry. Never paste it into a text thread.
- Confirm the brokerage, agent assignment and default lead source before importing anything.
Verify write access
Section titled “Verify write access”Use a synthetic lead with a unique test identifier. Create it once, add an agreed note and read it back. Verify ownership and duplicate handling. Test call scheduling separately if required; do not trigger a live lead campaign as a connection check.
Disconnect and troubleshoot
Section titled “Disconnect and troubleshoot”Remove the stored connection and stop queued work. Confirm with the admin or Inside Real Estate how to invalidate the actual token; do not assume removing it from the token list revokes it immediately. Token lifetime and deletion behavior remain customer-onboarding checks until verified against accessible vendor guidance.
Who completes the work?
Section titled “Who completes the work?”An agent/developer can implement the connector, field mappings and automated checks. A customer administrator must authorize account access and permissions; the vendor must approve any restricted partner access. A business operator verifies the test records before production use. Follow the shared setup and release checklist for credential handling, approval gates and launch checks.
Setup guidance reviewed October 23, 2026. Vendor menus and entitlements can change; unresolved details are called out above.