> ## Documentation Index
> Fetch the complete documentation index at: https://docs.apollospace.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Real Estate

> Brokerages and developers: qualify leads, schedule viewings, and follow up on offers across many simultaneous interested parties — with the negotiation always staying with the broker.

It's 7pm on a Tuesday. A listing blew up: fifteen people messaged on WhatsApp
asking the same thing; three want to view it tomorrow but nobody has confirmed
a time; a couple asked for an offer on Friday and still has no reply; and a
two-month-old list of interested buyers went cold because there was never time
to circle back. It isn't a lack of demand — it's too much demand for one
calendar.

**What leaves your plate:** the first reply to every prospect, lead
qualification, scheduling and reminding for viewings, listing questions, and
offer follow-up all start happening on their own — with context, within
budget, and with the negotiation always waiting on the broker.

## How it works, in one line

In real estate the bottleneck isn't finding a property — it's **keeping up
with many interested parties at once without letting any of them go cold.**
The agent doesn't replace the broker: it makes sure every lead is answered,
qualified, and followed up, and hands the person what truly needs judgment —
price, offer, and contract.

```mermaid theme={null}
flowchart LR
    A[Trigger<br/>new lead, viewing,<br/>offer sent] --> B[Agent pulls context<br/>from Company Brain + CRM]
    B --> C[Decides + uses tools<br/>CRM, Outbound, Routines, Docs]
    C --> D{Sensitive?<br/>price, offer,<br/>contract}
    D -->|No| E[Replies / qualifies /<br/>schedules / reminds]
    D -->|Yes| F[Proposes + calls the broker<br/>with full context]
    E --> G[Becomes memory<br/>the next step already knows]
    F --> G
```

## Concrete flows

### 1. Qualify the lead that came in — and capture preferences into the CRM

**Trigger:** a prospect arrives by [WhatsApp](/en/integrations/whatsapp),
email, or the listing form.

The agent replies on the spot and runs a short qualification, one question at
a time: what they're after (buy or rent, neighborhood, number of bedrooms),
price range, timeline, whether financing is already in motion. As answers come
in, it creates the [lead in the CRM](/en/features/crm), fills the preference
fields, and logs the conversation as activity — nothing gets lost in a
WhatsApp screenshot. If the profile matches a property in the book that's
already in the [Company Brain](/en/features/brain), it notes the suggestion on
the card.

The result: when the broker opens the [pipeline](/en/features/crm) in the
morning, every new lead arrives **qualified and sorted by stage** — not as a
queue of unread messages to triage from scratch.

<Note>
  Qualification pulls from the Brain what's worth asking for *this* kind of
  property — an off-plan launch raises different questions than a
  ready-to-move rental. The script lives in the Brain, not in a fixed form.
</Note>

### 2. Schedule the viewing — and the reminder that cuts no-shows

**Trigger:** the lead wants to see a property.

The agent matches the agreed availability against the calendar and proposes
viewing times. Once confirmed, it logs the viewing as activity in the
[CRM](/en/features/crm), creates the [task](/en/features/boards) on the
responsible broker's board, and **schedules an automatic reminder** on the
client's channel ([WhatsApp or email](/en/features/outbound)) — the day before
and a few hours ahead. If you want to keep a hand on the messaging, each send
can wait for **your approval before it goes out**.

```mermaid theme={null}
flowchart TD
    A[Wants to view] --> B[Agent proposes times]
    B --> C{Client confirms?}
    C -->|Yes| D[Logs viewing + creates task<br/>+ schedules reminder]
    C -->|No reply| E[Routine re-engages the lead<br/>in a few days]
    D --> F[Reminder day-before + day-of]
    F --> G[Becomes memory]
    E --> G
```

The win isn't "a bot that books slots." It's that **the agreed viewing
doesn't vanish** among fifteen parallel conversations, and the right reminder
the day before knocks down the number of people who don't show.

### 3. Answer listing questions — straight from the Brain

**Trigger:** the prospect asks about the property — HOA fees, property tax,
square footage, parking, pets allowed, paperwork, construction status.

The agent looks for the answer in the [Company Brain](/en/features/brain) —
the property sheets, the spec documents, the building rules, and the files the
brokerage already ingested — and replies on the spot, in the right language.
When the information **isn't there**, it **doesn't make it up**: it logs the
question and escalates to the broker with the history of what's been
discussed. For a market question beyond the book — "what's price per square
meter in that neighborhood?" — [Scout](/en/agents/scout) runs the public web
research and returns a summary with sources, no guessed numbers.

<Info>
  **Why this matters:** most messages are the same question asked fifteen
  times. Answering them on the spot, with the correct info from the sheet,
  frees the broker for what only they do — read the person and run the
  negotiation.
</Info>

### 4. Follow up on the sent offer — and re-warm the lead that went cold

**Trigger:** an offer was sent and is sitting unanswered, or a
[routine](/en/features/rotinas) sweeps the cold-lead book.

For the **open offer**, the agent tracks the deadline and, at the right
moment, drafts a polite follow-up — "checking in to see if any questions came
up about the offer on property X." The draft and the stage update in the
[CRM](/en/features/crm) are ready, but any message that touches **price,
terms, or a counter-offer** is **proposed for the broker to approve** — it
never goes out on its own.

For **cold leads**, a routine the agent schedules for itself periodically
revisits everyone who showed interest and went quiet, pulls from the
[CRM](/en/features/crm) who's due for a fresh touch, and fires — via
[Marcus](/en/agents/marcus) — a re-engagement by [email or
WhatsApp](/en/features/outbound): a new property that fits the profile, a price
change. Anyone who replies returns to the pipeline as a warm opportunity and
becomes a [proactive notification](/en/features/rotinas) in the broker's bell.

<Info>
  **The cold-lead book is a brokerage's most forgotten asset.** A routine has
  no hectic week — it circles back to whoever went quiet on the right day,
  every time, and turns a stalled list into opportunity.
</Info>

## What stays human

<Warning>
  The agent **proposes**, never decides alone, whenever the subject is:

  * **Price negotiation** — discount, counter-offer, payment terms, any value
    conversation with the client.
  * **The commercial offer** — the document that becomes a formal offer to the
    buyer or tenant.
  * **Contract and signature** — reservation, purchase agreement, lease, any
    commitment that creates an obligation.
  * **Money** — deposit, refund, commission, any adjustment to amounts.
  * **Heavy external, legal, or regulatory communication**, governance
    decisions, and destructive actions.

  In those cases the agent prepares everything — the draft, the lead's
  context, the negotiation history — and **waits for the broker to approve.**
  Every action lands in the auditable trail, with author and justification.
</Warning>

## Where to start

<Steps>
  <Step title="Upload the book and the sheets to the Brain">
    Ingest your property sheets, spec documents, and the questions you answer
    every week into the [Company Brain](/en/features/brain). That's where the
    agent pulls its first response and its qualification from — without it,
    there's nothing to consult.
  </Step>

  <Step title="Wire a channel and let the agent take first line">
    Connect [WhatsApp](/en/integrations/whatsapp) and let the agent qualify and
    log every lead in the [CRM](/en/features/crm). Start with human approval
    before each external message and loosen it as it earns trust.
  </Step>

  <Step title="Schedule the cold-book re-engagement">
    Create a [routine](/en/features/rotinas) that revisits stalled leads and
    proposes a fresh touch. One agent, one cadence, one channel — and autonomy
    grows like a ratchet, not a leap.
  </Step>
</Steps>

## Next steps

<CardGroup cols={2}>
  <Card title="Commercial & sales" icon="handshake" href="/en/use-cases/commercial">
    The full prospecting, qualification, and follow-up pattern — of which real
    estate is a high-volume case.
  </Card>

  <Card title="Native CRM" icon="address-book" href="/en/features/crm">
    Where the lead, the preferences, and the negotiation history stay alive —
    no human memory required.
  </Card>

  <Card title="Outbound" icon="paper-plane" href="/en/features/outbound">
    Email and WhatsApp with approval before the send — the viewing reminders
    and the cold-lead re-engagement.
  </Card>

  <Card title="Scout" icon="magnifying-glass" href="/en/agents/scout">
    The public web research — price per square meter, neighborhood,
    comparables — with sources, no guessing.
  </Card>
</CardGroup>