> For the complete documentation index, see [llms.txt](https://docs.fyxer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fyxer.com/workflows/fyxer-in-practice/workflows-by-role/fyxer-for-real-estate.md).

# Fyxer for real estate

For estate agents, property consultants, buyer's agents, and commercial property professionals.

Your day is valuations, viewings and calls, with the paperwork squeezed in between. Fyxer works across your email, calendar, meetings and Slack or Microsoft Teams, so you can prep, keep your team in the loop and follow up from wherever you are.

New to Fyxer? [**See how agents at Knight Frank and eXp are using it.**](https://www.fyxer.com/teams/real-estate)

***

### Workflows for real estate <a href="#workflows-for-real-estate" id="workflows-for-real-estate"></a>

<table data-view="cards"><thead><tr><th align="center"></th><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td align="center"><h4>Prep, reply, and follow up between appointments</h4></td><td>Walk into every listing appointment prepped, and get follow-up drafts before you’re back in the car.</td><td><a href="/workflows/fyxer-in-practice/workflows-by-role/fyxer-for-real-estate/prep-reply-and-follow-up-between-appointments.md">Prep, reply, and follow up between appointments</a></td><td><a href="https://2071956920-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQw8dD7zhmYjhngY9WCfZ%2Fuploads%2F9uaUtBstfvUk8TEWvDjs%2FProduct%20updates.png?alt=media&amp;token=019c9605-7511-40ac-b187-34e9d00ea6ae">Product updates.png</a></td></tr><tr><td align="center"><h4>Stay on top of your inbox between viewings</h4></td><td>Catch every inquiry, even when you're out on viewings all day.</td><td><a href="/workflows/fyxer-in-practice/workflows-by-role/fyxer-for-real-estate/stay-on-top-of-your-inbox-between-viewings.md">Stay on top of your inbox between viewings</a></td><td><a href="https://2071956920-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQw8dD7zhmYjhngY9WCfZ%2Fuploads%2FsCwy64ntQpVb7fhYtSNP%2FScheduling.png?alt=media&amp;token=38ac25c1-7bd5-4caf-90d6-c91017979ded">Scheduling.png</a></td></tr></tbody></table>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.fyxer.com/workflows/fyxer-in-practice/workflows-by-role/fyxer-for-real-estate.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.