This is part of How to Have Grok Bot ______ for You. Capability first. HVAC, roofer, and realtor spins come later.
You open the phone and drown. Calendar. Texts. Email. Yesterday’s jobs that never got a close-out. The van should already be moving.
HVAC. Plumber. Roofer. Cleaner. Landscaper. Handyman. One person, one shop calendar, one inbox where work dies. You are not a Slack team. You do not need a corporate digest. You need five lines and three decisions before the first stop.
Done tonight is not “I automated my morning.” Done is one brief tomorrow morning that you actually use. Then you drive.
Hire a Briefing Officer
Name the bot Briefing Officer. Or Morning Brief. Pin a three-line charter on it.
- Owns: a weekday morning scan of your shop calendar and one inbox.
- Good: a five-line brief with three decisions, ready on your phone before the van moves.
- Never: send. Never move money. Never invent a job time.
That is the job. Not a second employee. Not a status report of everything that happened overnight.
If you already use the knowledge-worker pattern in Don’t Open Slack First, keep that for desk days. This post is for the shop that runs on phone + calendar. Same “three decisions” idea. Different surface.
What the five lines have to hold
One screen. If it scrolls past your thumb in the driveway, it failed.
- Today’s appointments. Names, addresses, windows you actually typed. If a time is missing, write [NEED]. Do not invent 2pm.
- What needs a reply. One inbox only. Texts, email, Marketplace. Name the threads. Do not summarize the whole phone.
- One overnight change. A cancel. A reschedule. A parts delay. If nothing changed, say so.
- Three decisions only. Reply / go / wait. Not twelve tasks dressed up as decisions.
- What to ignore. Vendor spam. Old CCs. The group chat that is not about today’s jobs.
If it pads the list, your charter was too polite. Three means three.
What you connect (and what you don’t)
Grok Bot is early beta. SpaceXAI and Cursor announced it August 11, 2026. Access is included with Cursor Ultra and other qualifying Cursor and SuperGrok plans. Cursor Ultra is $200 a month. That is the only plan price we will name.
You get one cloud computer, shared by every bot you create. Sign-ins and files live on that machine, not on one bot. If you connect the whole stack day one, the blast radius is the whole stack. Don’t.
Connect Calendar and/or one inbox only. Open Settings → Plugins from the sidebar account button, or press Cmd+,. Authorize in the browser. Never paste a password in chat. If the plugin is not there yet, paste a screenshot or a text list of tomorrow’s jobs and the three threads that need a reply. Stop.
Tonight, in seven steps
- Name what “open the phone” costs you. Ten minutes of scrolling before the first stop. A missed cancel. A reply you meant to send yesterday. Say it out loud. That is why this bot exists.
- Create the bot. Name it Briefing Officer. Give it a title that matches the job.
- Paste the charter below. That is the first message.
- Connect Calendar and/or one inbox only. Settings → Plugins. Confirm it shows as Installed. Or paste a screenshot/list. Do not connect the whole stack.
- Do one brief together. Walk tomorrow’s appointments and the threads that need a reply. Edit until it is five lines and three decisions. Kill invented times. Put [NEED] on gaps.
- Save a weekday morning routine. Click the bot name in the chat header to open the info pane, or press Cmd+Shift+I. Ask it to follow along and save a routine: every weekday morning, scan calendar + that one inbox, leave the five-line brief in this chat, do not send. Confirm the schedule and the time zone.
- You read five lines, then drive. Check the names, the windows, the three decisions. Reply from your phone if you need to. Then the van moves.
Copy-paste charter
Paste this as the first message. Change the trade and the inbox name. Keep the never lines.
You are Briefing Officer for a one-person local shop. You own a weekday morning scan of my shop calendar and one inbox. Good looks like a five-line brief with three decisions I can read before the van moves. You never send. You never move money. You never invent a job time. Every weekday morning, leave one brief in this chat with exactly these five lines: 1) Today's appointments (name, address or job site, window I typed) 2) What needs a reply (threads in the one inbox I connected) 3) One overnight change (cancel, reschedule, parts, or "nothing changed") 4) Three decisions only (reply / go / wait). Rank them. Park the rest under ignore. 5) What to ignore on purpose Rules: - If a time, address, price, or name is missing, write [NEED] and stop on that fact. Do not invent it. - Prefer "do nothing" when a thread does not need me today. - Do not summarize the whole phone. Do not pad past five lines. - Do not send. Do not move money. Do not start a second job while this brief is open. - If you cannot see the calendar or inbox, write [NEED] and stop. I read five lines. Then I drive.
What done means
One brief tomorrow morning you actually use. Not a second employee. Not a Slack clone with better formatting.
If it wrote you a strategy memo, the charter was too polite. Tighten it. If it invented a 2pm window you did not type, kill the line. If it handed you twelve decisions, it failed the job.
You still own the send. You still own the money. You still own the calendar.
Limits worth saying out loud
It is beta. Expect rough edges. One shared computer means one leaked login is every bot’s login. Do not connect the whole stack day one. Do not let it send. Do not let it move money. Do not ask it for legal, medical, or financial advice. Do not paste passwords. Do not invent a job time and then drive to it.
If you want the product itself, start at Grok Bot Explained. If you want drafts after leads already wrote you, use the follow-up how-to. If you want public facts before first contact, that is research leads. If you want a tiny team so specialists do not all ping you, that is Chief of Staff. Desk days still belong to the overnight Slack brief.
If you want this built for your shop, that’s a different conversation.
Share this article

Leave a Reply