Buyer Desk

Buyer Desk is an AI-powered buyer’s agent service that enables agents within your brokerage to represent and serve property buyers. Agents create financial briefs for buyers, the system sources off-market opportunities using an AI swarm, and jurisdiction-specific compliance gates ensure regulatory compliance before handoff.

Overview

Traditional buyer representation is reactive — buyers contact agents, agents passively search listings. Buyer Desk inverts this:

Buyer’s Goal → AI-Powered Sourcing → Compliance Gates → Matched Candidates

Key Features

• Goal-Driven Briefs — Agents capture buyer intent (first-home? rental-income?), available cash, target location, timeline
• Multi-Currency Support — local currency/USD (Latin America), CAD (Ontario), USD (USA), and AED (UAE) with automatic normalization
• Off-Market AI Swarm — Temporal workflows hunt internal inventory + external leads matching buyer criteria
• Jurisdiction Compliance — default gates per jurisdiction (Latin America, Canada Ontario, USA, UAE), verified by brokers
• Full Agent Control — Agents create briefs, view candidates, manage compliance verification in-app

Jurisdictions Supported

Latin America (growth market)

• Currency — local + USD (norm for high-value transactions)
• Compliance Gate — aml_kyc (KYC via the country’s FIU)
• Regulation — Lighter; buyer representation is emerging/novel

Canada Ontario (stress test)

• Currency — CAD
• Gates — foreign_buyer, fintrac, bra
• Regulation — Strict; the 3-gate flow ensures regulatory compliance

United States (the largest market)

• Currency — USD
• Gates — state_license, buyer_agency, fincen_aml, firpta
• Regulation — State licensing; written buyer-representation agreement required (post-NAR settlement, 2024)

United Arab Emirates / UAE (foreign investment)

• Currency — AED (pegged to USD)
• Gates — rera_registration, freehold_eligibility, uae_aml
• Regulation — RERA/DLD; foreign ownership only in designated freehold zones

Workflow: Agent Perspective

1. Create a Buyer Brief

Navigate to Dashboard → Buyer Desk → New Brief.

1. Select jurisdiction (Latin America | Canada Ontario | USA | UAE)
2. Enter buyer details (name, contact)
3. Define financial goal:
   - Goal type: First-Home OR Rental-Income
   - Available cash: local currency / USD / CAD / AED
   - Max monthly payment (first-home) OR target monthly cashflow (rental)
   - Horizon: Years to purchase
4. Optionally specify target zone (e.g., "CDMX Polanco", "Toronto Downtown", "Dubai Marina")
5. Submit

System Response: Brief created in draft status. If all compliance gates apply to the jurisdiction, they are seeded as pending. The agent can immediately move to verification, or wait for system matching.

2. System Matches Candidates

Once brief is submitted, an asynchronous AI swarm activates:

brief.submitted event
    ↓
Temporal buyerOutreachWorkflow starts
    ↓
Match internal inventory (up to 500 listings)
    ↓
Score by:
    - Price fit (sweet zone = max monthly payment ÷ 360 months)
    - Zone match (token-based; no substring false positives)
    - Currency compatibility
    ↓
Upsert candidates (status: active, scored 0–100)
    ↓
Brief status: active OR blocked_compliance

If compliance gates are pending, brief stays at blocked_compliance until broker verifies.

3. View & Share Candidates

Once matching completes, agents see:

• Candidate list with score, price, zone, source (internal/off-market/outreach)
• Discard reason (if score < threshold) — agents can override
• Next steps button → handoff to buyer (out-of-system negotiation/viewing)

Workflow: Broker Perspective

Gate Verification

Brokers (only) can verify compliance gates. Navigate to Dashboard → Buyer Desk → select brief.

Gates Panel shows:

[✓ Verified]  [○ Pending]  [✗ Failed]
aml_kyc       fintrac      foreign_buyer
(verified at 2026-07-04 by the broker)

To Verify:

1. Click Verify button on a pending gate
2. System records: broker identity, timestamp, verification
3. If all gates verified: brief resets to active, fresh matching run triggered
4. Agent notified to review new candidates

API: Creating Briefs Programmatically

POST /api/dashboard/buyer/briefs
Authorization: Bearer <agent-jwt>
Content-Type: application/json
 
{
  "buyerName": "María García",
  "buyerContact": "maria@example.com",
  "jurisdiction": "MX",
  "zoneQuery": "CDMX Polanco",
  "goal": {
    "kind": "first_home",
    "currency": "USD",
    "availableCash": 150000,
    "maxMonthlyPayment": 3500,
    "horizonYears": 3
  }
}

Response:

{
  "id": "brief_abc123",
  "status": "active",
  "targetProfile": {
    "priceMin": 850000,
    "priceMax": 1050000,
    "currency": "MXN"  /* normalized to pack primary */
  },
  "complianceChecks": [
    { "type": "aml_kyc", "status": "pending", "jurisdiction": "MX" }
  ]
}

Error Handling:

Data Flow

Agent creates brief
    ↓
buyer_brief.submitted event → Temporal Cloud
    ↓
buyerOutreachWorkflow (idempotent start)
    ↓
Load brief + derive target profile
    ↓
Match internal listings
    ↓
Guardian compliance check (fail-closed)
    ↓
Batch upsert buyer_candidates
    ↓
Brief status updated (active → blocked_compliance or matched)
    ↓
Agent sees candidates in dashboard
    ↓
[Broker verifies gates if pending]
    ↓
[If gates verified: re-trigger matching]
    ↓
Agent hands off to buyer (out-of-system negotiation)

Handoff & Beyond v1

Once candidates are identified and compliance gates verified, the agent provides:

• Candidate list with photos, pricing, key details
• Financing pre-approval (local first-home programs; CMHC in Ontario; FHA in the USA)
• Next steps: buyer scheduling, property viewing, negotiation

Automated offer/negotiation is deferred to v2. Handoff creates a standard real estate deal record in the main Onoots pipeline, where human agents and brokers continue the workflow.

i18n

Buyer Desk is fully localized:

• English — docs.onootsai.com (this page)
• Spanish — docs.onootsai.com/es (guía completa en español)

Form labels, error messages, gate descriptions, and compliance language adapt to jurisdiction locale.

Troubleshooting

Brief stays at draft after submission

• Check that jurisdiction is valid (Latin America | CA-ON | US | AE)
• Verify goal is feasible (availableCash sufficient for down payment floor)
• Ensure buyer name and contact are filled

No candidates found

• Zone token mismatch — try simpler zone names (e.g., “CDMX” instead of “CDMX Polanco”)
• Price band too tight — expand maxMonthlyPayment by 10%
• Insufficient internal inventory for zone — candidates may appear after 24–48 hours as external sources populate

Gate verification fails

• Broker must be logged in with broker role
• Gate must be in pending state; verify only once
• Contact support if gate gets stuck in failed state

Next Steps

• Compliance Gates & Jurisdictions
• Market Validation