Field notes / AI systems · Level 3 of 5

Wiring an Assistant Into Your Inbox, Sheets, and CRM

Three inboxes, two hundred emails a day, and somewhere in there: a seller who finally said yes. This is the build that finds it before your second coffee, and the honest list of ways it will quietly fail you.

If you run a real estate operation for any length of time, you end up with inbox sprawl. A personal Gmail that sellers somehow still use. A business address on your website. One for your rental brand that Airbnb and your cleaners write to. Deal flow, money issues, and tenant problems arrive scattered across all of them, interleaved with four hundred newsletters.

At Level 2 you built a buy box that screens whatever you paste. The problem is the word "paste." Nobody pastes two hundred emails. So the real deals sit unread in inbox number three until Thursday, and Thursday is sometimes too late.

Level 3 removes the paste. The model reads your email itself, screens what it finds against your buy box, and hands you a ranked list. You run it with one sentence in the morning. Here is the whole build on Claude with the Gmail connector; no code, about an hour, most of which is Gmail settings.

Step 1: Aggregate the inboxes

The connector reads one Google account. Your leverage move is making one account see everything, and Gmail has done this for free since forever. Pick your main business account as the hub, then in each of the other accounts:

1. Open Gmail Settings, then Forwarding and POP/IMAP, and add your hub address as a forwarding address (Gmail sends a confirmation code to the hub; click it).
2. Instead of "forward everything," go to Filters and create a filter that forwards what matters: everything except obvious noise. A filter like from:(-noreply -newsletter -notifications) forwarded to the hub cuts 60% of the junk before the model ever sees it.
3. In the hub account, create a label per source (src/personal, src/rentals) with a filter that applies it to mail forwarded from each address. Now the model can tell you where a thread came from.

Fifteen minutes, and you have solved a problem no AI can: knowing where all your email is. If an account cannot forward for some reason, Gmail's "Check mail from other accounts" (POP import) in the hub achieves the same thing from the other direction.

Step 2: Connect Claude to Gmail

1. In Claude (desktop app or claude.ai), open Settings, then Connectors.
2. Connect Gmail and sign into the hub account. Connect Google Drive too while you are here; you will want it for the log sheet.
3. Create a Project called Morning Triage. Add two documents to its knowledge: your Buy Box doc from Level 2, and the triage doc from the next step.
4. Read the permissions screen before clicking accept. You are giving a third party read access to your email. That is a real decision, make it deliberately. (It is also the conversation Level 4 fixes with scoped service accounts.)

ChatGPT equivalent: connect Gmail under Settings, Connected apps, and use a Project the same way. Same shape, same caveats.

Step 3: Write the triage doc

Same principle as the buy box: the intelligence goes in a document, not in the prompt. This one defines what "important" means in your business, because the model's default idea of important is not yours.

TRIAGE RULES v1 (updated 2026-08-17)

P1, DROP EVERYTHING (deliver first, one line each):
- Seller or agent replying to an active negotiation
- Anything about money movement: wires, payoffs, escrow, arrears
- Capital partner or lender asking for something
- Tenant/guest emergency (water, power, locked out, safety)
- Legal or title: notices, deadlines, recorded documents

P2, TODAY (screen deals against the Buy Box doc):
- New deal flow from any source. Run the buy box verdict:
  PURSUE deals go at the top of P2 with the verdict line.
- Contractor bids or scheduling on active projects
- Booking issues on rentals that cost money if slow

P3, THIS WEEK:
- Everything else a human should eventually read

IGNORE (do not mention, do not count):
- Newsletters, promos, receipts under $200, platform
  notifications, cold vendor pitches

RULES
- When unsure between two levels, pick the higher one.
- Never summarize away a number, a date, or a name.
- Note which source label (src/...) each item came from.
- If an attachment seems load-bearing (contract, payoff
  letter), say so; don't pretend you read what you can't.

Step 4: The morning run

Open the Morning Triage project and type:

Run triage on the last 24 hours across my inbox, including
mail under the src/ labels. Follow the Triage Rules doc.

Output:
1. P1 items, each with: who, what, the ask, suggested reply
   in my voice (short, direct).
2. P2 deals with buy box verdicts, PURSUE first.
3. P2 non-deals, one line each.
4. P3 as a count with 5-word topics.
5. Bottom line: the 3 things I should do before 10am.

The model searches the mailbox, reads what matches, applies your two documents, and produces the digest. First run takes a few minutes and will surprise you twice: once with a real item you had missed, and once with a P1 that should have been a P3. The second surprise goes into the triage doc as a rule, version bump, same loop as the buy box. By v1.4 it will call priorities the way you do.

On weekends, change "24 hours" to "since Friday morning." That is the entire configuration interface.

Step 5: Log it so patterns show up

Add one line to the end of the morning prompt:

Then append every P1 and P2 item to my "Triage Log" sheet in
Drive: date, source label, sender, priority, one-line summary,
buy box verdict if a deal, action taken (leave blank).

The blank "action taken" column is for you, ten seconds at end of day. A month of this log answers questions you currently guess at: which source actually sends deals worth pursuing, which wholesaler's "great deal" emails have never once passed your buy box, what percentage of P1s you handled same-day. This sheet also becomes the test data for Level 5, so start it now.

The failure modes nobody warns you about

1. Connector auth dies silently. Google expires tokens; Claude will say it cannot access Gmail, but only when you run it. Nothing emails you about it. Symptom: a suspiciously quiet digest. Fix: reconnect in Settings. Rule: a digest that seems light is a prompt to check the connector, not a reason to relax.
2. The forwarding chain rots. A filter gets edited, an account password changes, forwarding stops, and the hub looks normal, just emptier. Once a week, ask: "How many emails arrived under each src/ label in the last 7 days?" A source at zero is a broken pipe, not a slow week.
3. Volume clipping. On a 400-email day the model may read a subset and not volunteer that. Force honesty: the digest prompt's structure helps, and you can add "state how many emails you searched and how many you actually read."
4. Attachments. Body text gets read; a payoff letter PDF might not be. The triage doc's attachment rule makes the model flag instead of fake it.
5. You stop reading your own inbox. The most dangerous one. The digest feels complete, so you stop scanning. But this whole system still runs on you remembering to trigger it, and it has no way to tell you when it is wrong. Keep a daily two-minute manual scan of P1 sources until Level 4 gives you real alerting.

Where Level 3 breaks

Notice what all five failure modes have in common: the system cannot tell you about them. Every one is discovered by a human noticing something feels off. That is the structural ceiling of Level 3, and no amount of prompt engineering fixes it, because the missing piece is not intelligence. It is infrastructure: a trigger that fires without you, logs that prove what ran, and an alert that fires when it does not.

Also notice the vacation test still fails. Two weeks dark and the triage simply does not happen, because you are the trigger. If that is acceptable for your operation, stop here honestly; excellent Level 3 beats mediocre Level 4. If a missed P1 costs you a deal or a partner's trust, the next post is the jump: the same triage running at 6am on a server, posting to the channel your team reads, and pinging you when it fails. That last clause is the entire upgrade.

The series

1. 00The Five Levels of AI in a Real Estate BusinessThe map
2. 01Getting real value out of a chat windowPublished
3. 02Building a buy box that the model actually followsPublished
4. 03Wiring an assistant into your inbox, sheets, and CRMYou are here
5. 04Getting it off your laptop: hosting, logging, and alertsComing next
6. 05Evals and cost control, or how to know it is still rightComing soon