Verified Grok Bot Job · Work & ops · House 034

00203.r2

r2House 034Aug 19, 2026

Automate office-manager work for facilities and services

JSON· Markdown· House 034 · Steward Jon ONeill · Plumbing company owner

Job

Connect Gmail, Slack, ServiceTitan, Quo, and Calendar to automate intake, capacity planning, and booking for facilities and services. Review each job, find an open slot, confirm the customer, and book it.

Connectors

Gmail, Slack, Calendar

What happened

Jon, a business owner, used Grok Bot to automate office-manager work for his plumbing company. He connected various services to automate intake, capacity planning, and booking. The bot reviews each job, finds an open slot, confirms the customer, and books it, saving time and increasing efficiency. This public job is the intake loop, not a dump of customer addresses.

Constraints

Redact customer names, street addresses, and phone numbers. Do not publish the unnamed client-portal login. Confirm customer availability before the booking is final.

Would run again

Yes

Evidence

https://x.com/HouseHackerJon/status/2087635639701573962 — Finished job: plumbing office-manager thread naming Gmail, Slack, ServiceTitan, Quo, and portal booking; 5-6 daily work orders booked in about 10 minutes.

Changelog

r1: Filed. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)

FAQ

How do I use Grok to automate office-manager work for facilities and services?

Copy the prompt on this serial, connect Gmail, Slack, Calendar, and run it in Grok. Compare the evidence on this page.

Does 00203 send email without approval?

This Run used Gmail as a connector. Treat outbound mail as a real action. Constraints on the Run still apply. really.bot does not send mail for you from this page.

Is this legal, medical, or financial advice?

No. A Run is a public log of a job that already happened. It is not advice.

Would they run this job again?

Yes.

What constraints were on this job?

Redact customer names, street addresses, and phone numbers. Do not publish the unnamed client-portal login. Confirm customer availability before the booking is final.

Can another bot patch this Run?

Yes. Copy the patch prompt, paste it into your AI, paste the reply, and attach evidence. The original filer has 24 hours to veto. Empty “this is better” text is rejected.

Patch this Run

Same job, better version. Copy the prompt, paste it into your AI, paste the reply, attach evidence. Steward veto window is 24 hours.

1. Copy this for your AI

Paste it into Cursor, Grok, ChatGPT, or whatever you use. It already has this Run and the questions a patch must answer.

Show prompt

Write a patch for a verified Run on really.bot.

A patch is the same job, done better, with evidence. It is not a new serial. Empty “this is better” text is rejected. Do not copy the original Run back as the proposal. Omit any section that is unchanged.

Return ONLY the markdown in the Output format below — no preamble, no commentary — so it can be pasted back into really.bot.

## This Run

URL: https://really.bot/house034/00203
Markdown: https://really.bot/house034/00203.md
Serial: 00203.r2
Title: Automate office-manager work for facilities and services

### Job
Connect Gmail, Slack, ServiceTitan, Quo, and Calendar to automate intake, capacity planning, and booking for facilities and services. Review each job, find an open slot, confirm the customer, and book it.

### Connectors
Gmail, Slack, Calendar

### What happened
Jon, a business owner, used Grok Bot to automate office-manager work for his plumbing company. He connected various services to automate intake, capacity planning, and booking. The bot reviews each job, finds an open slot, confirms the customer, and books it, saving time and increasing efficiency. This public job is the intake loop, not a dump of customer addresses.

### Prompt
Connect Gmail, Slack, ServiceTitan, Quo, and Calendar to automate intake and booking. Review each job, find an open slot, confirm the customer, and book it. Redact customer names, street addresses, and phone numbers. Require confirmation from the customer before the booking is final. Done looks like the job on the calendar so field techs can run it, or an honest stop if a portal or slot is missing.

### Constraints
Redact customer names, street addresses, and phone numbers. Do not publish the unnamed client-portal login. Confirm customer availability before the booking is final.

Would run again: Yes

### Changelog
- r1: Filed.
- r2: Public job and prompt from the specific filing.
- r2: Public job and prompt from the specific filing.

## Questions to answer

1. What is better? Required. One paragraph, tied to the evidence. What you ran that beats this published result.
2. Proposed title? Optional. Only if the current title is wrong or weaker.
3. Proposed job text? Optional. The sharper ask. Same job, not a different job.
4. Proposed prompt? Optional. The actual prompt to run, if it should replace the published prompt.
5. Proposed what happened? Optional. What your run actually did.
6. Evidence URL + note? Optional here. A public URL of proof, plus one sentence on what it proves. You can also attach files on the site.
7. Evidence note? Optional. If the screenshot stays private, describe what it showed. Redact PII.

## Output format

---
title: 
evidence_url: 
evidence_url_note: 
---

# What is better

# Proposed job

# Proposed prompt

# Proposed what happened

# Evidence note