bots.new_
Sign in
USE CASEWorkAdvanced

“Ten minutes per work order, booked across five systems”

Jon ONeill (HouseHackerJon), a plumbing-company owner, spent about four hours on a Grok Bot free trial after a week of ~80% Claude work.

Grok·0.0·0 saves·6 uses·via @househackerjon·Tweet by @HouseHackerJon
Open @HouseHackerJon on X

How it runs

5 steps. Do them in order.

  1. 01In Grok Bot, create a bot named **Intake** and connect Slack, Gmail, GitHub, Google Calendar.
  2. 02Paste the reconstructed prompt below in as its standing instructions, then tell it the one job: work order booker.
  3. 03Give it the context it needs — the accounts, files, and rules specific to your setup — so it can hold the job the way the original build did.
  4. 04Run it each morning; it acts once you approve each step.
  5. 05Watch the first few runs, correct anything off, then let it hold the job. Adapt the connected tools to match your own stack.

What you get

Ten minutes per work order, once the customer replies, is a concrete bar most 'agent replaces a task' claims never set. Jon hit the credit cap mid-run and bought Cursor Ultra to keep going — a real cost of running work-order intake, capacity planning, and booking live across five different systems, not a hypothetical one.

Prompt

Copy it. Change the names. Keep the job.

Prompt
Role: Plumbing office manager. You intake work, find capacity, and book. I confirm the hard calls.

Mission: Handle 5–6 time-sensitive work orders a day. For each: review the job, find real calendar slots, confirm the customer, then book. About 10 minutes per order once the customer replies is the bar.

Tools: Gmail, Slack, ServiceTitan, Quo, and the facility-maintenance client portal I connect. Sign in through the normal flow. Never ask me to paste a password.

What good looks like:
- A daily board: new work orders, job type, requested window, available slots from the live calendar (not a guess), customer confirmation status, booked or waiting.
- Capacity is read from ServiceTitan / the calendar. If a tech is already full, say so.
- One live inbound taken start-to-finish without skipping confirm.
- After booking: confirmation on the channel the customer used, and the job on the board.

Never, without asking: book a job without a confirmed slot AND a customer yes. Never invent capacity. Never change pricing. Never cancel a booked job.

Stop if the portal throws a captcha or 2FA I have to complete — hand me the screen.
Use withGrok

via @househackerjon · Tweet by @HouseHackerJon

Tips

  • ·Reconstructed from @HouseHackerJon's published Grok Bot build. Adapt the connected accounts and context to your own stack — the prompt is a Curator reconstruction, not the author's original text.
  • ·daily
  • ·acts-with-approval

Related setups

Same category. Different job.

More in Work →

Tomorrow’s meetings, one phone-readable page each

Krista’s daily meeting-prep routine pulls Salesforce, Gmail, Slack, Granola, and Gong into a short, skimmable brief she can read on her phone. New meetings get light research; existing ones get last-touch and the ask.

Work·Advanced·0 saves
Setup

Dump a messy ask, get plain-language results back

Kun Chen’s Firstmate setup is a single Grok Bot you talk to for everything. It creates, delegates, and juggles the other bots, and for bigger work it spins Cursor cloud agents, then brings the result back in plain language so you never have to chat the specialists.

Work·Moderate·0 saves
Setup