Dock + Salesforce Real Estate Cloud: brokerage workflows with attributed sales-lead review

Salesforce Real Estate Cloud is where commercial brokerages keep accounts, listings, tour history, and pipeline. When an agent reads those records to draft a tenant brief or qualify a lead, the interpretation needs to live somewhere reviewable. A note pasted into a Salesforce activity is not reviewable. A Dock row with a pointer back to the Salesforce account, the agent's name, the broker who signed off, and a timestamp is. This post covers the platform pattern for Salesforce-anchored brokerages, and the workflow pattern for sales-lead sign-off on agent-drafted account briefs. It sits under Dock for real estate.

Salesforce Real Estate Cloud stays 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.

Account Brief Queue

Each row links back to the Salesforce account ID. The brief is the agent's read of activity history, recent tours, and tour notes. The decision is the broker's, not the agent's.

Workflow: account brief to sales-lead sign-off

The agent re-reads the Salesforce account each morning, drafts a brief into Dock, and tags the assigned sales lead. The sales lead reviews in Dock and writes Approve, Hold, or Reject with a one-line reason. On approve, Dock writes a structured activity back to Salesforce with the agent identity, brief link, and reviewer name attached. The Salesforce record stays canonical. The interpretation and the sign-off live in Dock, where they can be queried later by account, by reviewer, or by agent. This is the same two-party pattern covered in two-key handshakes for irreversible operations, applied to a softer but still consequential action: deciding which accounts get human outreach time. Procurement-side spend approvals through Coupa follow the same shape when a brokerage runs vendor reviews against the same agent.

Why it matters

Brokerages run on attribution. A deal credit, a referral split, an outreach decision: each one needs a name on it. NAR's commercial research notes that practitioner sentiment and account-level intent signals are the inputs brokers actually use to allocate time, and those inputs degrade fast without a written read.¹ Salesforce industry clouds, including the Real Estate Cloud configuration, are built to hold the canonical account and listing data for this kind of work.² What they do not hold is the agent's reasoning or the broker's sign-off on that reasoning. Without agent audit and compliance for the interpretation layer, the brokerage cannot answer "who decided to chase this account, and why" six months later. Dock answers it by row.

Sales leads who want the full account-brief workflow with named agent identity on every row should read Dock for sales, then route their brokerage agents through the same review queue documented under Dock for sales.

Set up a brokerage workspace.

FAQ

Does Dock replace Salesforce Real Estate Cloud? No. Salesforce keeps accounts, listings, tours, and pipeline. Dock keeps the agent's brief and the broker's sign-off, with a pointer back to the Salesforce record.

Can the agent write back to Salesforce? Yes, after sales-lead approval. The write-back is a structured activity carrying the agent identity, the Dock brief link, and the reviewer name.

What happens if the Salesforce account changes after the brief is written? The agent re-fetches on the next review cycle. Old briefs stay in Dock as a record of what was true at decision time, with the timestamp preserved.

Why route Coupa through the same workflow? Brokerages run vendor reviews and tenant improvement spend through procurement. The same sign-off pattern keeps the named reviewer on both the account decision and the spend decision.