> For the complete documentation index, see [llms.txt](https://thecontentforge.gitbook.io/thecontentforge-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://thecontentforge.gitbook.io/thecontentforge-docs/real-estate/people-market-work.md).

# People, Market and Team Operations

## People

* **Contacts** is the organization-wide person record for contact details, roles, consent and relationship context.
* **Leads** triages and assigns buyer, seller, renter and investor inquiries.
* **Past Clients** manages post-close check-ins, milestones and long-term relationship work.
* **Reviews & Referrals** handles consent-aware feedback, referral and testimonial-permission workflows.
* **Needs & Matches** compares explicit buyer/renter needs with eligible property facts and explains proposed matches.

Never use protected traits or proxies for matching, routing, audience selection or neighborhood descriptions.

## Market

* **Signals** shows timely real-estate events and data changes with source, geography and freshness.
* **Intelligence** summarizes geographic and market-level patterns.
* **Opportunities** turns permitted signals into explainable items for review.

Confirm evidence, geography, freshness, legal outreach basis and affected property/audience before acting. Market signals are not appraisals or guaranteed predictions.

## Team Operations

Use **Work → Team Operations** for routing rules, candidate/selection explanations, queues and service-level work. Routing must not use protected traits or proxies. Review exceptions and expired assignments rather than assuming a route was correct.

## Automations

Use **Work → Automations** to inspect agent configuration, schedules, run history, evaluations and exceptions. Automation authority should remain bounded. Publishing, legal acceptance and client communication follow the configured human-review controls.

## Workspace configuration

* **Voice & Brand** compiles agent/brokerage style. It controls style, not facts or compliance.
* **Brokerage & Team** stores brokerage, office, team, agent, license and service-area context.
* **Data Import** maps and validates supported real-estate CSV rows before acceptance.
* **Social Connections** controls publishing accounts.
* **Team Members** controls roles and workspace access.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://thecontentforge.gitbook.io/thecontentforge-docs/real-estate/people-market-work.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.