agentos.guide › blog

Hermes Agent For Real Estate: Five Copy-Paste Prompts To Run A Property Desk In Your Agent OS

By Julian Goldie · 8 November 2026 · agentos.guide

Hermes Agent for real estate runs best in your Agent OS as a dedicated property Bot that you brief in plain English: five prompts set it up, and one daily routine keeps it useful.

Below is the quick start, the five prompts I'd paste in, and the workflow that ties them together for a small estate or lettings agency.

Every prompt keeps client messages as drafts, because Hermes has no approval step for what a gateway sends.

Prefer to have my team plan it with you? Book a free SEO strategy session.

Quick Start: Three Things To Have Ready

• A property Bot. In Bot Mode each Bot is its own profile, with separate memory, skills and model, so create one called "Property Desk".
• A private chat for it. A Telegram group with your negotiators, set up from the Telegram page.
• A dedicated mailbox. Connected through the email gateway with only your staff on EMAIL_ALLOWED_USERS.

With those three in place, open the Bot's chat and paste the prompts in order.

What The Property Bot Can And Can't Reach

Plan around the bottom three rows from the start.

Without a portal feed, the Bot only knows what your team tells it, so keep a simple habit: forward the enquiry, attach the brochure, paste the notes.

The only property-data entry in the catalog is the community jp-reinfolib plugin, which covers quarterly transaction data for one Japanese city, so it won't help a UK or US office.

Everything else on this page uses general tools that already exist.

Prompt 1: Set The Bot's Ground Rules

Paste this first so every later job inherits it.

You are the Property Desk for a small estate and lettings agency.
Ground rules for every task, including scheduled ones:
1. Draft only. Never send, email, text or message a client, buyer,
   seller, landlord or tenant. Post drafts in this chat.
2. Never send or accept offers, contracts or tenancy agreements.
3. Never give legal, tax or financial views. Say "check with our
   broker or solicitor" instead.
4. Put [CHECK] beside any measurement, price wording, tenure or
   feature you have not seen in our notes.
5. Give a source link for every fact about an area.
Save these rules to memory and confirm them back to me.

Read its confirmation carefully; if it paraphrases a rule loosely, correct it in the same chat until the wording is exact.

Hermes keeps MEMORY.md and USER.md per profile, so the rules stay with this Bot only.

Prompt 2: Connect The Diary And The CRM

The MCP catalog can be driven from chat: ask for a server and a setup card appears.

Add the Calendly MCP and the Close MCP from the catalog.
After they connect, list the tools each one gives you and tell me
which ones can change data. For Close, keep the voice-agent tools
excluded. Then show me the config change needed to mark Close as
trust: untrusted so every write asks me first.

The Close entry already excludes its voice-agent tools by default, because one of them places real outbound AI phone calls.

Check the reply lists read and write tools separately, and that the voice tools are still marked as excluded.

Swap Close for Attio if that is your CRM; both use OAuth, and you authorise each in the browser.

🔥 Want the full Property Desk build on video?

Inside the AI Profit Boardroom you get step-by-step video trainings, the installable Agent OS, four coaching calls a week and 3,400+ members running Bots like this.

→ Join the AI Profit Boardroom

Prompt 3: Build The Listing House-Style Skill

Skills are folders in ~/.hermes/skills/, and the agent can write one for you.

Create a skill called listing-style for property descriptions.
Procedure:
- Use only facts from my notes, the brochure PDF and the photos.
- Order: location, layout, kitchen, bedrooms, outside space.
- Describe the home, never the kind of person it would suit.
- Tag every measurement and feature with [CHECK].
- Output a full description and a 60-word portal summary.
Show me the SKILL.md before you save it.

Review the draft SKILL.md line by line; this file becomes the standard every future listing is written to.

Then email the Bot a brochure and photos and ask for a draft using the skill.

Photos go to the vision tool; never use image generation to change how a property looks.

Prompt 4: Schedule The Morning Chaser List

Cron jobs take plain language and deliver back to the chat they were created in, so paste this inside the team group.

Create a scheduled job for 8am every weekday.
Task: using the Close tools, list open leads with no activity in
the last three days. For each: name, last note, and a two-line
follow-up draft in our tone. Draft only: do not send anything.
Deliver the list to this chat.

Ask the Bot to run the job once straight away, so you can judge the first list before tomorrow morning.

By default cron_mode: deny blocks dangerous commands in scheduled runs, so the job can read and draft but nothing drastic.

Prompt 5: Run A Weekly Area Brief

The browser toolset gives the Bot browser_exec, which can navigate, read, scrape and screenshot pages.

Every Friday at 9am, research [town or postcode area] using public
pages only: council planning notices, new developments, transport
changes, school news. Respect each site's terms of use.
Return five bullet points, each with its source link and date.
Draft only. Deliver to this chat.

Swap in your own patch: one town per job keeps each brief short enough to read over coffee.

Use the brief for vendor updates or your newsletter after a person checks the links.

📞 Want help getting more instructions from search?

Book a free SEO strategy session and my team will look at how sellers and landlords find you, and where your Property Desk fits.

→ Book a free SEO strategy session

The Daily Workflow

1. 8am: the chaser list lands in the team group; negotiators edit and send from their own inbox or phone.
2. Through the day: staff forward enquiries to the Bot's mailbox and get a draft back in the same thread, with a Calendly link where a viewing fits.
3. New instruction: email the brochure and photos, ask for a listing-style draft, clear every [CHECK] tag.
4. Friday: the area brief arrives with its links.

Each step ends with a person, never with the Bot sending.

After a fortnight, look back at which drafts needed the most editing and tighten the matching prompt or skill, rather than adding new jobs.

A small, reliable desk beats a large one that nobody trusts.

Pick A Model For Each Job

Bot Mode lets the Property Desk carry its own model pin, separate from your other Bots.

Scheduled jobs can go further: the cron docs let each job pin a model with --model and --provider, or lock in the current one with --pin.

Unpinned jobs follow cron.model if you have set one, and otherwise whatever your main model is when the job fires.

A sensible split is a quick, light model for the chaser list and your strongest writer for listing drafts.

If client data must stay in the office, the providers page covers self-hosted endpoints such as Ollama and vLLM.

Troubleshooting The First Week

• Forwarded portal alerts never arrive. The email gateway silently ignores noreply and bulk senders, so a person must forward them from their own address.
• Mail from a colleague is dropped. Check that EMAIL_AUTHSERV_ID matches the top Authentication-Results header your mail server writes.
• Every reply arrives twice. Two gateways are running; check with hermes gateway status and stop one.
• Close tools don't appear. Restart the session after authorising, as the catalog entry's own instructions say.
• The Microsoft 365 plugin fails. The community entry requires a Hermes version below 0.22, so it won't load on v0.23.

Fix these before you add WhatsApp, because a client-facing channel makes every mistake visible.

Adding WhatsApp Later

The WhatsApp Business Cloud API route asks for three things up front: a verified Meta Business account, a phone number used only by the business, and a public HTTPS address where Meta can reach your gateway.

After 24 hours without a message from the client, replies need an approved template, which is Meta's rule.

On a client-facing number the Bot answers people itself, so only connect it once the drafts are reliably right.

Planning a client-facing channel? Talk it through on a free strategy call first.

How This Differs From The Sales Guide

Our Hermes Agent for sales guide is about outbound pipelines and prospect research.

This Property Desk is mostly inbound: enquiries, viewings, listing copy and area knowledge.

Run them as two Bots so their skills and memories never mix.

Want to compare notes with other agencies? The AI Profit Boardroom covers Bot builds on its weekly calls.

FAQ

Where do I paste these prompts?

Into the chat of a dedicated Property Desk Bot in your Agent OS. Paste the scheduling prompts inside your team Telegram group so results come back there.

Why does every prompt say draft only?

Hermes approvals cover dangerous commands and writes on untrusted MCP servers, not messages sent through a gateway. Writing draft only into each job keeps a person in charge of what clients receive.

Can I use Attio instead of Close?

Yes. Both are in the Nous-approved MCP catalog and connect with OAuth. Twenty CRM is available as a community plugin.

Can the Bot pull listings from my portal?

No. There is no MLS, Zillow or portal integration for Hermes, so feed it your own notes, brochures and photos instead.

Final word on Hermes Agent For Real Estate

Paste prompt 1 today, add one prompt a day after it, and join the AI Profit Boardroom for help tuning your Hermes Agent for real estate.

Related guides on agentos.guide

→ Grok Bot For Real Estate: Run A Property Desk In Your Agent OS

→ Hermes vs Manus: Give Each Agent Its Job In Your Agent OS

→ Hermes Agent For Accounting: 5 Prompts In Your Agent OS

→ Hermes Agent For Ecommerce: 5 Shop Prompts In Your Agent OS

📺 Video notes + links to the tools 👉

🎥 Learn how I make these videos 👉

🆓 Get a FREE AI Course + Community + 1,000 AI Agents 👉

← all guides on agentos.guide