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 is uploaded anywhere.
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.
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.
144 rows processed so far, including 12 with no match found.
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.
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 — no value or equity records are in this export yet, so that part of the book is still 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.
- Chase the supplemental export. 0 value / equity records are in this export — requested Oct 21, 2026. Without it, the weakest link in Pipeline health stays at 0%.
- 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.
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 outreach system 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 email outreach system: automatic check-in emails 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.
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.
