Proof it’s working
The machine on one screen — every number names where it came from, and anything stale carries its date. Counts only: this app never shows a homeowner’s name.
Ladder counted Oct 24, 2026 (lead-machine analysis of the Oct 21 verified export, the Oct 23 activity pull and the verified-values shield). The lineup is the playbook’s daily plan at the proven pace — 35 sends, one lane, inside the 7-day household gate. The full ladder is the Segment ladder card, just below Total client performance.
Add homeowners in bulk
Bring your whole book at once — drop in a CSV from any CRM or portal export.
Send to AgentCRM saves one file — homebot-hq-for-agentcrm.json — holding these households. Open AgentCRM, tap “Import from Homebot HQ” and pick that file: they land as contacts tagged Homebot HQ. It is a file handoff, not a live sync — the two apps will share directly once AgentOS accounts launch Nov 4. The file is built right here on your device, same as the cleaned list; nothing leaves this device unless you link your apps below — then the same households also sync straight to AgentCRM.
🎯 Work this list by selling signal
🔗 AgentOS Sync
Link your apps — MailBook, GuestBook and AgentCRM share one book.
Your personal link
One link sets up this app on your other phone or computer — no codes to type.
Your file never leaves this device — HQ only ever shows counts.
Total client performance
From your Homebot export, Oct 12
Apple opens emails by itself on iPhones — opens lie. HQ counts clicks and replies only.
Segment ladder — hottest to coldest
Every household in the book sits on one rung. The top rungs hold every proven click, every intent tag, and every lead this engine has made — that is where the sending pace goes.
An intent tag on their own record — likely to buy (8), likely to sell (4), highly engaged (2). No batch: one personal email each, worked by hand, plus the named hand-raisers from the logs.
A verified Oct 23 value and equity figure on file, and real clicks. 32 households carry a verified number in all (31 in this book) — the only people who can be quoted a figure.
Lead-score tier 1 — every one a proven clicker, not one ghost. 97 tier-1 households in the book in all. The hot batch: the email sells the verified number they do not have yet.
Clicked at least once — 1,036 proven clickers in the book in all. The quarterly rotation works this rung, and every email asks for a reply.
Scored warm in the old portal (active in the last 30 days) but never clicked. Apple says they open; nothing is proven. One useful touch at a time, hunting a first real signal.
Ghost-only and unranked — the biggest rung in the book. A permission pass first (“want to keep getting these?”), then quarterly value touches for the keepers.
In the book with no activity record at all. One warm reactivation shot, then left alone if silent. The wider “797 no activity” count includes 774 people who never made the verified book — they are not emailed.
Counted Oct 24, 2026 in the lead-machine analysis — the master list joined against the Oct 23 activity split, the lead scores, the per-record signal tags and the verified-values shield, matching on every email on each household record; households on the touch-exclusion list were removed before counting. Rebuilt after every send week.
Working a rung today? Load the book file in Add homeowners in bulk (top of this view) — its selling-signal dropdown filters that list by Likely to sell, Likely to buy, Highly engaged and High equity, and the view you pick is what the cleaned-list download, the AgentCRM file and Sync this view act on. R1’s tags are exactly those dropdown signals.
Pipeline
Verified export — Oct 21, 2026
unique households verified in the book (Homebot support export, Oct 21, 2026)
One duplicate household merged during ingest. The old portal headline is not used as the pipeline count.
This file is the verified roster plus limited loan fields. The supplemental value/equity, tag/intent, and engagement/activity export was requested Oct 21; 13 value / equity records were later pulled from the portal on Oct 23, 2026 and saved into the master list.
144 rows processed so far, including 12 with no match found.
This week in your book
The whole book in four plain lines — built only from the aggregates already on this page. Copy it into your own notes for the week.
- Your book holds 4,311 households. At 70 emails a day, about 490 of them hear from you this week — 11.4% of the book.
- 62 ready-now signals are sitting in the book — ready for refi is the biggest group (37). Work the ready-now names first.
- Email reaches every household — 4,311 (100.0%). Phone reaches 4,021 (93.3%), so email is the channel that covers the whole book.
- Weakest lever: value and equity records — only 13 households have one yet. Every new value record makes the next round of emails sharper.
Aggregates only — no homeowner names, home values, or homeowner emails, same as every other panel here.
Book mix
Who is in the book, by client type in the verified export — counts only, from the aggregates already on this page. Nothing new collected.
About 1 in 4 households in the book is also a buyer — the buy side of the same book, already on the email rotation.
How you can reach them
Contactability from the verified export — counts only, from the aggregates already on this page. Nothing new collected.
Every household in the book has an email on file, so the email rotation reaches the whole book; phone opens a second channel for most of them.
Pipeline health
One score for the whole book — a plain average of the four coverage numbers below, all from the aggregates already on this page. Nothing new collected.
pipeline health score
Weakest link: value and equity records — only a small share of households have a value or equity record yet, so that part of the book is still mostly empty.
What to do next
The three moves that matter most, in order — worked out from the aggregates already on this page. Counts only; nothing new collected.
- Keep value / equity records fresh. 13 records are in the book — keep them current as homes sell and loans change.
- Work the enrichment queue. 5,383 of 5,527 households (97.4%) are not yet processed — every batch finished sharpens the book.
- Work the hot end first. 62 households carry a ready-now signal in the Oct 21 portal snapshot (2 likely to sell · 8 likely to buy · 2 highly engaged · 37 ready for refi · 13 just listed) — they go first in the rotation.
Built from the same aggregates as Pipeline health, Coverage gaps and Hot signals — if those numbers move, this list moves with them.
Hot Signals
Portal snapshot — Oct 21, 2026 · historical, not live
Portal snapshot only — Oct 21, 2026, the last portal read before we took the engine in-house. The support export did not include the per-client value, equity, tag/intent, or activity fields behind these layers; a supplemental export was requested Oct 21. Counts only; the names behind them live in the private master list, never in this app.
Signals per 100 households
How dense the ready-now signals are in the whole book — each Hot Signals count above per 100 households in the book (4,311 households), from the aggregates already on this page. Nothing new collected.
Likely to sell and highly engaged are each 2 households — 0.05 per 100 before rounding, so they show as 0.0 at one decimal. Ready for refi is the densest ready-now signal in the book.
Today's Lanes
Daily cap: 70 emails (35 per lane). Corrections below are extra — they fix our own mistakes.
Lane Pace
What the cap means for the whole book — plain arithmetic on the totals above, nothing new collected.
for one full pass through all 4,311 households at the full 70-a-day pace
The 7-day gate never slows a full pass: at 62 days a pass, every household is well past the gate before its next turn comes up.
Corrections
correction emails sent today
Lane A: 12 · Lane B: 12 — every one sent, every one using the live portal figures.
Wrong values caught, corrected with live portal numbers.
Program Rules
- No stale value goes out. While the supplemental export is pending, any value used for a touch is checked individually before the send.
- 70 emails a day, max — 35 per lane.
- 7-day household gate: no household gets touched twice inside a week, across both lanes.
- Scoring counts clicks, replies, and app logins only. Opens never count — too many of them are machines, not people.
- The homeowner book stays off Facebook, always. The book and the realtor groups never mix.
Our Own System
Homebot is cancelled. As of Oct 21, 2026, this program runs on our own rails — no portal rent, no middleman.
- The database is ours. Homebot's Oct 21 support export delivered 4,312 rows, verified as 4,311 unique households after one duplicate merged — and nobody can bill us for our own data.
- Sending is ours. The same two Gmail lanes, the same caps: 70 a day, 35 per lane, and the 7-day household gate across both.
- Scoring is honest. A homeowner scores when they click, reply, or log in to the My Home app. Email opens are never counted — mail apps fake them.
- Values are handled honestly. The roster export did not include per-home value or equity fields, so a supplemental export has been requested. Until it lands, a value is checked individually before any hot name gets a touch.
Ask AI LIVE · ANSWERS IN SECONDS
Ask how the automated email outreach works — the lanes, the scoring, home values, growing the base, or the $9-a-month realtor plan. If it's beyond the book, the desk points you to Steven.
Running a homeowner book?
This is the HQ view of your automated email outreach: sequences and check-in emails that send themselves to every homeowner in your book — what their home is worth and how much equity they have — with the ready-to-sell names on top. Lanes, touches, pipeline, program status — one screen. Built for realtors who work their database like a business.
Built for your own list — people who know you. No cold email, no bought lists, no blasting strangers. MailBook sends to the homeowners in your own book — people who asked to hear from you. If they didn't ask, they don't belong here.
Want an HQ for your book? $9 a month — first month free, joining is open.
Program notes — behind the scenes
—
Coverage Gaps — What's Missing
The gaps in the book, counted from the same aggregates above — so the next fix is obvious. Aggregates only, as everywhere in HQ.
Email-only for these households until enrichment finds a number.
Refi timing stays a guess for these until the supplemental export lands.
So any value used in a touch is checked individually first — that is the program rule while the supplemental export is pending.
The public-records crawl works the queue in batches; processed rows include 12 no-match results so far.
