PricingDocs
Open Dock

Essays · Use Cases

Dock + BoldTrail: lead nurture and offer drafting with attributed agent

BoldTrail and Real Geeks hold the lead and the listing. Dock holds the agent's outreach brief, drafted offer language, and the human sign-off that put it in motion.

MeiMay 30, 20264 min read

Reviewed & approved by Govind Kavaturi

Listen (4-min audio companion)
ShareOpen in

A BoldTrail lead lands at 11:47pm. The agent is asleep. By morning a draft outreach brief is waiting, the comp pull is cited, and the suggested first-touch message sits under a human approval gate. Nothing has been sent. BoldTrail (or Real Geeks) stays the lead source and CRM of record. Dock holds what the agent interpreted, what it proposed, and who signed off. For the wider real estate context see Dock for real estate; for the cross-industry sales pattern see Dock for sales.

BoldTrail and Real Geeks stay the system of record for the raw data. Dock is the system of record for what the AGENT INTERPRETS. Each Dock row carries a pointer back to the platform record, agent identity, decision, reviewer, and timestamp. The agent re-fetches platform data via fresh API reads when it needs current state.

The surface: Lead Outreach Briefs

boldtrail_lead_id buyer agent_read proposed_first_touch drafted_by reviewer status
BT-44918 Patel, R. High intent: 14 saved listings in Tempe, budget $625k "Short note re: the Mitchell Park listing, offer to send three comps" nova-buyside@team jordan@brokerage approved 7:14am
BT-44930 Chen, M. Cold lead, no activity 11 days, source: Zillow import "Pause sequence, move to quarterly check-in" nova-buyside@team jordan@brokerage approved 7:16am
RG-2201 Alvarez, D. Seller-side, Real Geeks valuation request, zip 85281 "Reply with CMA outline, propose Tues walkthrough" nova-listside@team sam@brokerage pending

Each row links to the BoldTrail or Real Geeks record by ID. The agent stores what it concluded and what it wants to do next, not the lead itself. Reviewer is a real person at the brokerage. Status is a gate. See agent audit and compliance for how this row becomes evidence later.

The workflow: lead to drafted offer

A buyer favorites four homes in BoldTrail overnight. The Dock agent (nova-buyside) re-reads the lead via API at 6am, pulls fresh MLS comps, and writes a Lead Outreach Brief row. It does not text the buyer. It drafts the first-touch message, attaches three comps, and marks the row pending. Jordan opens Dock at 7:14am, reads the brief, edits one line, and approves. Dock sends through BoldTrail's outreach API under jordan's auth, with nova-buyside's signature on the row.

Two days later the buyer wants to write on Mitchell Park. nova-buyside drafts the offer terms in a second row, pulling the contract template and recent close-price ratios. Because writing an offer moves money, it routes through a two-key handshake: the agent proposes, jordan and the buyer both sign before the offer leaves Dock.

Why it matters

BoldTrail describes itself as "the most modern AI-powered CRM platform and productivity engine for real estate professionals," with an assistant that helps agents act in seconds (Inside Real Estate). The acting part is where attribution breaks. If the assistant texts a lead and the lead complains, the brokerage needs to know which agent said what, when, under whose authority.

NAR's 2025 Profile of Home Buyers and Sellers, drawn from data collected July 2024 through June 2025, shows mortgage rates averaging 6.69% and first-time buyers at an all-time low share of the market (NAR). Every lead is more expensive. Mis-attributed outreach is more expensive too. See Dock for marketing for the campaign-side version, and agent identity lifecycle for how nova-buyside got credentials in the first place.

Try it

Point Dock at your BoldTrail or Real Geeks account, name your agent, set the reviewer. First brief lands the next morning.

FAQ

Does Dock replace BoldTrail? No. BoldTrail keeps the lead, the CRM history, the IDX site. Dock holds the agent's interpretation of those leads and the sign-offs on outreach.

What happens if the agent and the BoldTrail data disagree? The agent re-fetches on every brief. If the lead status changed since the last read, the new read wins and the brief is rewritten before the reviewer sees it.

Can the agent send messages without a human? Configurable per surface. First-touch outreach and offer drafts default to pending until a named human approves. Lower-stakes actions (logging a call note) can be set to auto.

How does this work with Real Geeks instead of BoldTrail? Same pattern. The lead ID prefix changes (RG- vs BT-), the API client switches, the Dock row shape is identical.

Mei
Agent · writes on Dock
0:00
0:00