How Are Home Service Businesses Preparing for AI Search Visibility?
Search is changing fast. We’ve already seen Google test online estimates and AI-assisted pricing in local search. Now, AI tools are helping homeowners decide who to call, sometimes before they ever visit a website. Scorpion Marketing published a report with the following stats: 22% of homeowners are already using AI tools to research services or get recommendations 80% of business owners say they don’t know how to prepare for AI-driven search visibility We’d love to hear what you’re seeing👇 Have you noticed changes in how customers find you or ask questions? Are you doing anything intentionally today to prep for AI-driven search? If AI search on your radar but still confusing, what question do you have? This space will continue to evolve. Sharing what’s working (or not) across different trades helps everyone get ahead of it!
Built my own AI operating system on Jobber. One gap: Jobber's text conversations
I run a home services company, and since late September I've been building what I call our "OS": a private web app that connects Claude AI to Jobber, GoHighLevel, RingCentral and Google. I'm not a coder. I built it by describing what I wanted to Claude Code, the same way I built our end-of-day reporting app. Claude connects to the OS through a custom MCP connection, and the OS talks to Jobber through my own Jobber API apps (one read-only, one with write access). Nothing gets sent or created without my approval. Claude proposes it, and I approve it. Here's what it does today: JOBBER - Read: find clients by name, phone, email or address - Read: properties and custom fields - Read: jobs, visits, requests and invoice summaries - Read: price history (past invoices and quotes) - Read: team calendar and open estimate time slots - Read: new requests still waiting on a reply - Write: create new clients (with texting turned on) - Write: create draft quotes GOHIGHLEVEL - Read: contacts, conversations and message history - Write: send SMS replies (opt-outs checked first) RINGCENTRAL (our office texting line) - Read: text conversations and recent calls - Write: send text replies GOOGLE - Read: check service addresses before they go into Jobber SCREENSHOT INTAKE - I drop in a screenshot of a lead, and it pulls out the details, checks whether they're already in Jobber, then creates the client or adds a note BEHIND THE SCENES - Our business rules and price list live in the OS, and Claude reads them live - On/off switches for every kind of write - An activity log of everything it did in each app - When I correct a draft, it logs the change so the drafts get closer to how we actually talk THE ONE GAP: text conversations inside Jobber. Claude can read a customer's texts in GoHighLevel and RingCentral, but not the conversation they're having with us through Jobber's own texting. As far as I can tell, the public API doesn't expose those messages, and there are no webhooks or Zapier triggers for them. Right now I work around it with screenshots and copy/paste. I've emailed Jobber API support and I'm waiting to hear back. Has anyone found a way to read (or send) Jobber text messages through the API or an integration? Or is there a setting or solution I'm missing? I'd love to hear how others are handling it, and I'm happy to share what I learned along the way.When High-Maintenance Customers Cost More Than They Pay
I’ve had customers who looked perfectly fine when I only looked at the monthly revenue. Then I looked at everything surrounding the account. Extra calls. Special scheduling. Repeated exceptions. More office time. More technician questions. More follow-up after the visit. That changes the math. A customer can pay a decent rate and still be a poor fit if the account constantly pulls attention away from the rest of the business. I’ve gotten better about watching for that earlier instead of waiting until I’m frustrated with the relationship. Sometimes a clearer boundary fixes it or the price needs to change. And sometimes I’d rather free up the capacity for a customer who fits the way we operate. Have you ever looked at a customer and realized the revenue wasn’t worth everything that came with it?
Instant response times might be hurting your business more than helping it.
This used to be hard for me to accept. Like most service business owners, I thought good service meant being available 24/7—answering every call, replying to every text immediately, even while on a job. But in reality, it made me slower, more distracted, and honestly less professional in the field. So I changed how I operate. Now I run structured communication windows during the day instead of reacting constantly. I set clear expectations with customers on when they’ll hear back from me, and I use simple systems to keep everything moving—estimates, reminders, and updates. The surprising part? Customers responded better to the structure than the availability. Another thing I’ve realized: cheap competitors aren’t the real problem. The problem is when customers can’t clearly see the difference between what we do and “just showing up and doing the job.” If they can’t see the value, price becomes the only comparison. So I’ve been working on tightening how we communicate what actually goes into the service—reliability, consistency, communication, professionalism—not just the task itself. I’m curious how others are handling this: Are you optimizing for speed and availability… or structure and consistency? What’s actually working better for you right now?
Best way to handle inbound calls to company line?
Curious yalls thoughts. Looking to not just grow, looking to scale and improve / continue to implement systems. Currently have myself, 1 outside sales rep, and field labor crew (fence install company) current process: customer calls into company # (my cell phone). I try to answer as if it were an office line to answer asap. From that, I confirm I can Text them, I then send a request form via jobber that has basic info / few questions to answer. If / when they fill it out, I add to the schedule for a confirmed day / time to quote on site. etc…… I feel this part is a lot of back and forth, and until I have an in house admin office worker that can answer these calls the first ring - I won’t be able to truly grow / stay efficient. (If I’m tied up, I don’t like calling them back 2 hours later, etc) but also - I love having them fill out the form bc the way I have questions on it, it turns it from a warm lead, to a warmer lead. Any way to streamline this, get more efficient, improve this current process? ANY thoughts or advice - real thankful.How We Define “Done Right” With Job Forms
As we added technicians, I realized “do a good job” is way too vague. What does that actually mean? For us, it means things like checking the gate, following the right yard pattern, documenting anything unusual, making sure the area was actually completed, and leaving the property secure. The more of that we can put into Job Forms, the less we have to rely on someone remembering every detail from training. That matters even more when someone is new, covering another route, or just having an off day. I still think training and judgment matter. A checklist can’t replace a good technician. But it can protect the standard. The goal is that “done right” looks the same no matter who is on the route that day. What are the non-negotiables you’ve built into your Job Forms?Why We Stopped Relying on Memory for Customer Communication
As we grew, I realized how risky it was to let important customer details live in someone’s head. Gate instructions. Dog notes. Access issues. Special requests. Things a customer had already called about. That might work when you have a small client list and the owner touches everything. It falls apart once multiple people are servicing the same accounts. We started leaning more on Jobber to keep those details attached to the customer and job so the technician can see what matters before they arrive. It also helped us get more consistent with communication. Customers get reminders, on-the-way messages, completion communication, and we send a gate photo after service. The goal is that the customer experience shouldn’t depend on whether myself, my wife or a technician happened to remember something from a conversation three weeks ago. As the team grows, memory becomes a terrible operating system. What customer information do you make sure your team can see before they ever arrive at the property?
>$3M companies - what do you use for a phone system?
For those running larger home service companies, what phone system are you using, and how are you balancing responsiveness with still feeling like a local business? One of our biggest priorities is making sure customers can actually reach someone. We have enough call volume that having every call ring directly to one person isn’t realistic anymore. We have a dedicated person managing new inquiries and general calls, with different departments handling more specific existing-customer needs. We’ve used an IVR/phone menu for years. We were on Google Voice for a while, but it gave us almost no useful reporting, metrics, or call recording, so we switched to Dialpad this year. Dialpad gives us much better visibility, but I’m questioning whether we’ve gone too far in the other direction. The feedback we’re getting is that the experience feels too much like a call center. A customer may call our local family-owned company and: Go through a phone menu • Hear the required call-recording announcement • Potentially reach our remote virtual assistant in the Philippines Individually, all of those things help us manage volume and stay responsive. Collectively, though, I worry we’re creating a customer experience that feels disconnected from who we actually are. At the same time, we’re well beyond the point where cell phones or a traditional landline setup would work, and we have remote employees who need to be part of the phone system. For those of you with multiple departments and meaningful inbound call volume, what are you using? What phone system and call-routing setup has worked best for you? And have you found a good way to maintain call recording, reporting, accountability, and responsiveness without making the customer experience feel overly automated?
