Grok Bot for real estate earns a 6.6 out of 10 from me: excellent at drafting and holding back, average at scheduling and research, and thin on property-specific connectors.
The score is an editorial reading of xAI's documentation, criterion by criterion, not a lab benchmark.
Sources are the official computer and apps guide, the security page, the files and results guide and the shared Bots page.
This is a tool review, not legal advice; contracts and legal documents still go past a broker or lawyer.
Want help deciding before you subscribe? Book a free SEO strategy session.
The scorecard: eight criteria for an agency
| Criterion | Score / 10 | Why, from the docs |
|---|---|---|
| Enquiry reply drafting | 8 | Email arriving at the Bot's address can start a routine, and the reply is held as a draft. |
| Send safety | 9 | Routine email from the Bot's own address always waits for Send; no unattended option exists. |
| Viewing scheduling | 7 | Calendar reads free time and creates events, but cannot add a Zoom link. |
| Property data connectors | 3 | No MLS or portal connector is named; Zoho CRM is the only CRM in the table. |
| Area and listing research | 7 | Browser on the cloud computer, with sessions that persist; sites can still block automation. |
| Client-ready summaries | 7 | Pages give tables, charts and filters, but are rolling out and not on Enterprise yet. |
| Team use | 7 | Shared Bots with Collaborator and Manager roles and private chats, Cursor teams only. |
| Data separation | 5 | All your Bots share one computer, its files and its credentials. |
| Overall | 6.6 | Average of the eight rows above |
The weights are equal, and the overall is a plain average rounded to one decimal.
Scores reflect what the docs say each feature does for an estate or lettings office.
How I scored it and what the numbers are not
Each criterion asks one question an agency owner would ask, such as "will it ever email a buyer without me?" or "can it see our listings database?".
The score reflects how fully the official docs answer yes, and how many caveats they attach.
A 9 means the docs describe the behaviour plainly with few exceptions.
A 3 means the docs show a workaround at best.
No row reflects speed, output quality on a real listing or anything measured in a test, because the docs do not publish that and I am not inventing it.
Where the docs and changelog differ on a detail, the current docs page wins.
Why enquiry drafting scores an 8
The Bot can claim one address at mail.grokbot.com, and plus aliases such as +enquiries land in the same inbox.
A routine can watch an alias and filter by sender or by a whole domain, which suits a website form that sends from a fixed domain.
The miss is that routines cannot filter by subject, so the alias has to do that sorting.
The address is permanent and can't be renamed, which a careful office will treat as a feature rather than a flaw.
Why send safety is the highest score
For an agent, the scariest failure is a wrong price or a wrong address going to a buyer.
Grok Bot's docs close that door for routines: email from the Bot's own address that you did not request in chat always waits as a draft.
First-contact emails go to one recipient each with an unsubscribe link, and bounced or unsubscribed addresses are dropped.
One setting to know: the chat and collaboration page describes Disable drafts for Bot, which lets a Bot send chat-requested messages directly, subject to Auto Review.
Routine email from the Bot's own address still waits as a draft, so the score holds, but leave that switch alone on a client-facing Bot.
Why scheduling stops at a 7
The Google Calendar app reads calendars, creates and updates events, checks free time and answers invitations.
That covers proposing viewing slots and holding them.
It cannot add a Zoom link because the Zoom add-on is unavailable to the app, and the docs also list a Zoom authorisation error on desktop with no workaround yet.
Offices that do video viewings will paste links by hand.
🔥 Want the setups that score highest on this card? 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 who share their Bot builds. → Join the AI Profit Boardroom
Why property data connectors score a 3
The connector host table names GitHub, X, Origin, the Google Workspace apps, the Microsoft 365 set, Stripe Link, Tailscale, QuickBooks Online, Workday, WhatsApp Business, Zoho CRM, Zoho Books and Zoho Desk.
Nothing in that list is a listings database or a property portal.
xAI does say a Bot can add an MCP server not in the catalogue, by URL or by command, and Team Marketplace connectors are checked by host, so your vendor may offer a route.
Out of the box, though, property data reaches the Bot through the browser or through files you attach.
Why research and summaries both land at 7
The browser lives on the same persistent cloud computer, and sign-ins carry over between tasks.
Cursor's Grok Bot page notes that sites can block automation or demand a human step, and the Bot hands those steps back rather than working around them.
For output, Pages turn research into a readable report or tracker in the Bot's Library, ready to share.
Both lose points for the same reason: rollout limits on Pages and site-by-site limits on browsing.
Team use and data separation
Team use: good roles, one big condition
A shared Bot can go to the whole Cursor team or to named people, with Collaborator for chatting and Manager for changing instructions, skills, memory and apps.
Every chat with it is private, even from the owner.
The condition is that it uses the owner's apps and secrets for everyone, and a shared Bot has no team email address.
Data separation: the weakest structural point
One account means one cloud computer: every Bot you run works on it, from a screen of its own.
Files, cookies and command-line credentials are visible to every Bot on the account, and xAI calls the screens work surfaces, not security boundaries.
Between users the isolation is strict, since each user's computer is dedicated and hardware-isolated.
For an agency, that means one person's Bots should not mix client files with experiments.
📞 Want a second opinion on your agency stack? Book a free SEO strategy session and my team will tell you straight where a Bot helps and where it doesn't. → Book the free session
The scorecard read by office type
The same eight rows land differently depending on how your agency works.
| Office type | Rows that matter most | Fit |
|---|---|---|
| Solo sales agent | Enquiry drafting, send safety, scheduling | Strong |
| Lettings and property management | Enquiry drafting, send safety, team use | Strong |
| Buyer's agent | Research, client-ready summaries | Good if Pages has reached the account |
| Brokerage on one property platform | Property data connectors | Weak |
| Office doing mostly video viewings | Scheduling | Workable with manual Zoom links |
Weight your own top three rows and the overall can swing well above or below the 6.6 headline.
What would lift each low score
Property data connectors would rise sharply the day xAI names a listings or portal connector in the docs.
Data separation would rise if Bots on one account could be walled off from each other; today the docs describe one shared computer by design.
Scheduling would gain a point if the Calendar app could add video links itself.
Client-ready summaries would gain once Pages is on every plan, including Enterprise teams.
None of these are promised in the docs or the changelog, so score the tool you can use today.
First-week checks before you trust it
- Send three past enquiries through the routine and compare the drafts with the replies you actually sent.
- Press Test on each routine with a dummy message from your own address.
- Confirm the Bot stopped at every Ask first rule you set.
- Ask it to list the facts it could not confirm in each draft.
- Check the time zone under Settings, Bot, Timezone matches the office.
If a draft ever states a property detail that is not in your notes, tighten the skill before you go further.
Strengths and limits
Strengths in one list
- Drafts by default for routine email, with no unattended send.
- Plus aliases that give each enquiry source its own routine.
- Ask first rules, up to 20, that always stop for you, per the approvals page.
- Pages for side-by-side property summaries.
- Work continues with your laptop closed.
Limits in one list
- No MLS, portal or e-signature connector named in the docs.
- No Zoom links on calendar events.
- Shared computer across all your Bots.
- Pages not yet on Enterprise teams.
- No model picker; the FAQ says Grok Bot picks the model for each task.
Who should use it, and who should not
Who should use it
A solo agent or small office that already lives in Gmail or Outlook and a calendar will get the most from it.
A lettings team that chases documents by email fits well, since aliases and drafts suit that rhythm.
A buyer's agent who writes comparison summaries fits too, as long as Pages has reached the account.
Plan names that include it: Premium, Super and Ultra on The X Subscription, per the plan page.
Who should not
Skip it if your whole operation runs inside a single property platform and you want the Bot to work there directly.
Skip it if you need offers submitted or documents signed by software.
And skip it if nobody on the team will review drafts every day.
Final verdict
Grok Bot is a strong drafting assistant for an agency and a cautious one by design.
It is not a property system, and the docs never pretend it is.
If you sell services rather than homes, the scorecard in our Grok Bot for sales verdict is the closer match.
Pick it for enquiry drafts, viewing holds and summaries; pass if you need deep listings integration.
🔥 Turn this verdict into a working Bot 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. → Join the AI Profit Boardroom
Also On Our Network
- 🌐 The ten-step listing desk build with aliases, Ask first rules and a tested routine
- 🌐 Whether a small agency should use it, with five office examples step by step
- 🌐 A ten-minute property desk quick start with five copy-paste prompts
- 🌐 Which AI models build listing pages around the Bot, with live Landing scores
- 🌐 The complete Grok Bot for Real Estate guide on the AI Profit Boardroom blog
FAQ: Grok Bot For Real Estate Verdict
How was the 6.6 score worked out?
Each of eight criteria got an editorial score out of 10 based on what the Grok Bot docs say, and the overall is the plain average.
What is the weakest part of Grok Bot for an agency?
Property data connectors. The docs name no MLS, portal or e-signature connector, so listings data comes through the browser or attached files.
What does Disable drafts for Bot change?
It lets a Bot send messages you ask for in chat directly, subject to Auto Review. Email a routine writes from the Bot's own address still waits as a draft.
Can an agency team share one Bot?
Yes, on a Cursor team. The shared Bot uses the owner's apps for everyone, and each person's chat is private.
📺 Video notes + links to the tools 👉
🎥 Learn how I make these videos 👉
🆓 Get a FREE AI Course + Community + 1,000 AI Agents 👉
About Julian
I'm Julian Goldie, an SEO entrepreneur, author and founder of the AI Profit Boardroom, which has 3,400+ members.
I help business owners scale with AI agents, automation and SEO.
- I've built a 7-figure SEO and link building agency, Goldie Agency, with a team of 70+ SEO experts.
- I've grown a YouTube channel to 400,000+ subscribers.
- I wrote "Link Building Mastery".
- My Udemy courses have taught over 29,000 students.
→ Get my best AI training inside the AI Profit Boardroom
Score it against your own office, start with the drafting jobs it rates highest, and join the AI Profit Boardroom for the full build of Grok Bot for real estate.
