All use cases
Office & Admin

An HVAC owner spent two hours on one Sunday morning wiring AI into reviews, his inbox, SOPs and ServiceTitan dispatch

Rob Brooks says he set up review responses for several locations, inbox filtering with Slack alerts, a cleaned-up SOP library, and a daily ServiceTitan dispatch summary for his call center, partly from his phone.

Real storyDone with Grok Bot (with Google Business Profile, Slack, Google Drive and ServiceTitan); before that Claude Code and Gemini
TradesHVAC

What they did

Rob Brooks (Chosin Companies; Tampa, FL; USMC veteran) posted on November 15, 2026: "Until now, my AI stack was mostly Claude Code for building internal software and Gemini for content cleanup. Today, I spent two hours testing @bot and completely overhauled how parts of my HVAC company will operate." What he says he built: review responses and alerts across multiple Google Business Profile locations; a content calendar and posting workflow; email cleanup and filtering with "real-time Slack alerts for priority events"; a rebuilt, deduplicated SOP library in Google Drive; and a ServiceTitan connection "that pulls a daily 3-day dispatch review and delivers a summary straight to our call center team in Slack every morning."

How it went

He says moving the SOPs into Google Drive let him "cancel Notion and cut redundant software costs" (he doesn't give a dollar amount). He started on his desktop and "finished the builds from my phone while having morning coffee outside with my wife." Asked why not do it all in Claude Code, he answered: "More intuitive. Faster. Easy to use across devices." Asked which job it took off his plate first, he replied: "I'm the CEO.. it's can't take my job. But it will make my teams jobs easier." This was day one. Several replies asked whether the call center actually reads the morning dispatch summary, and that wasn't answered in the thread. Results over time aren't in yet.

Worth knowing

This was a two-hour setup, not a proven result, so treat it as a list of good first jobs, not as proof. The one most people in the replies wanted to copy was the morning dispatch summary for the people answering phones. One reply made a fair point about reviews: a good reply to a bad review needs the job history, not just the review text. Note: he also promotes a "Trades Accelerator" program in the thread. When the cold hits, the first few days of no-heat calls are when CSRs most need to know what's booked for the next three days. A one-page summary in their inbox or Slack before 8 AM is something even a 3-truck Wisconsin shop could copy.

Try it yourself

You are the dispatch-summary assistant for a small Wisconsin HVAC company. Every morning you turn the schedule into a one-page brief for the people answering phones, so they can tell callers the truth about availability. You only read the schedule. You never book, move or cancel jobs. TASK: Write today's 3-day dispatch brief for our call team. CONTEXT (fill in the [BRACKETS]): - [COMPANY]: Example: Lake Country Comfort Heating & Air (fictional), Delafield, WI, 4 techs - [SCHEDULE EXPORT]: paste the next 3 days from ServiceTitan, Housecall Pro, Jobber or your calendar: date, time window, tech, job type (no heat, tune-up, install, estimate), city, status - [TECHS]: names, what each can do (installs, service, boilers), who's on call - [OUR RULES]: Example: no-heat calls get same-day if any opening; tune-ups can wait; installs take a full day; no jobs past 6 PM except on-call STEPS: 1. For each of the next 3 days, show: total jobs, open slots by tech and by morning/afternoon, and who's on call. 2. List every no-heat or no-hot-water job and its status. Put unassigned ones at the top as URGENT. 3. Find the soonest opening a CSR can offer for: a no-heat call, a tune-up, an install estimate. 4. Flag problems: a tech double-booked, a job with no address, a day that's over capacity. 5. Write 3 short lines CSRs can say on the phone, based on today's real openings (no promises beyond the schedule). RULES: - Use only what's in [SCHEDULE EXPORT]. If something's missing, say "NOT IN SCHEDULE." - Don't include customer phone numbers or full addresses in the brief. City only. - Keep it to one screen. Bullets, no paragraphs. OUTPUT FORMAT: Part A: urgent. Part B: openings by day. Part C: problems to fix. Part D: what to tell callers today. FOLLOW-UPS TO TRY NEXT: - "Rewrite Part D for a caller who is upset and has no heat with small kids at home." - "Compare this week's no-heat calls with last week's. Are we getting slower to schedule them?" - "Make this a Slack/email message I can paste in at 7:30 AM." FILLED-IN EXAMPLE (fictional Wisconsin business): - [COMPANY] = Lake Country Comfort Heating & Air (fictional) - [SCHEDULE EXPORT] = 31 jobs over 3 days, 4 techs, 3 no-heat calls (1 unassigned) - [OUR RULES] = no-heat same day if possible; on-call tech until 10 PM

Want help getting this working? Rise Systems in Oconomowoc sets these up.

Want this running in your business without the DIY? Rise Systems in Oconomowoc sets these up.

Free 15-minute AI check-up
Read the original

Source: X (Twitter) · November 15, 2026

Related