Finally Made the Jump to Jobber… Now What About AI Receptionists?
Hey everyone, After years of debating it, we finally got convinced enough to switch over to Jobber — big moment for our little backflow company here in California. The setup has been smooth so far, but now we’re staring down the next big decision: AI receptionists. I’ve heard mixed reviews about Jobber’s AI Receptionist. Some folks say it’s better than a lot of the options out there, others say it’s still not quite where it needs to be. So now we’re sitting here with a ton of choices and even more questions. We’ve been getting absolutely blown up by Clara AI sales reps, plus about a million other AI companies claiming they can do it better, faster, smarter, cheaper — you name it. I know a lot of these tools integrate with Jobber, which is great, but it also leaves us stuck trying to figure out which direction to go instead of wandering down ten thousand different paths. So I’m asking the pros here: What do you feel is the best AI receptionist for skilled trades? Plumbing, backflow, HVAC, electrical — anything where the calls are technical, urgent, and sometimes chaotic. If you’ve tested multiple platforms, I’d love to hear real‑world experiences. If you’ve stuck with Jobber’s AI Receptionist, I’d love to hear why. If you’ve found a third‑party AI that actually understands trades work, even better. Any solid advice that can point us in one direction instead of ten thousand would be hugely appreciated. Thanks in advance — From Cali with Love, Mr. BackflowIs “the customer is always right” hurting service businesses?
I don’t think the customer is always right. Customers deserve respect. They deserve clear communication, fair treatment, and a business that fixes mistakes when they happen. But that doesn’t mean every request is reasonable. A customer may ask for an exact arrival time your route can’t support. Or someone expects free work outside the agreed scope. Another client talks down to your team because they think paying the invoice gives them permission. Those situations affect the whole business. The owner starts making exceptions that turn into expectations. Good service needs boundaries. For us, that means clear policies around service windows, locked gates, aggressive dogs, weather, skipped visits, and what’s included in a visit. When we mess up, we make it right. When a customer ignores the policy or creates an unsafe situation, I can’t treat that the same way. That line matters. Where do you draw the line between taking care of the customer and letting the customer run the business?Claude API/ FB/Instagram API
Curious if anyone else here has implemented API's into their websites. I just figured out how to enable Claude API and Facebook/Instgram API's to automaticall generate instagram/facebook descriptions, alt tags, and hashtags by clicking a button. Then I can click another button to uplaod directly to FB and IG. It's made my image gallery uploads and social uploads to my IG and FB pages a breeze. Huge game changer! I even have my stats in my site now and can comment on posts and DM's all through my site without having to go into my social platforms anymore.Are you actually studying churn, or are you just guessing why customers leave?
I’ve been spending more time looking at churn in my business lately. Not just “how many customers canceled.” I wanted to know when they cancel, what stage of the relationship they’re in, what cities are weaker, what service types retain better, and where we should act before the cancellation happens. So I used Claude to analyze recurring residential client data from the last 4 to 5 years. Closed jobs. Active jobs. Win-backs. Monthly pricing. Client tenure. Service frequency. Number of dogs. City. Cancellation timing. The report ended up looking at 586 client runs from January 2022 through July 2026, including our active clients. A few things surprised me. The first big one: our danger zone is months 3–5. That’s where cancellation risk peaks. Month 1 is healthier than I expected. Most new customers make it past the first month. The bigger problem happens once the newness wears off. By month 3 or 4, some customers start re-deciding if the service is still worth it. They’ve experienced it and paid a few invoices. The yard is no longer a disaster and life settles back down. That’s the moment where the service either becomes part of their routine, or they start thinking, “Maybe I can just do this myself.” The data also showed that once a customer passes month 6, their expected stay jumps. That matters because it changes where we should focus retention. A customer in month 2 needs a different touchpoint than someone who has been with us for 14 months. Another thing that stood out: spring and summer are where we bleed the most. April, May, and July are higher-churn months for us. July was the worst month in the report. That makes sense when I think about customer behavior. People travel. Budgets get tighter. Kids are home. The yard dries out. Some customers think they’ll handle it themselves for a while. Then a few weeks later, the yard gets away from them again. But if we already know that pattern, we can do something before it happens. That’s the part I care about. Churn analysis is only useful if it changes your behavior. Here’s what I’m doing with the information: Month 1: Focus on the first experience. Welcome touches, clean communication, day-after check-ins, making sure the customer feels confident they made the right decision. Months 2–3: Add a surprise-and-delight touchpoint before the cliff. This could be a free deodorizer/sanitizing treatment, a small yard report card, or a referral ask while they’re still happy. Months 5–6: Celebrate the 6-month mark. That milestone matters because customers who make it past month 6 are much more likely to stay long term. Months 11–12: Send an anniversary thank-you and possibly a prepayment offer. If someone prepays for the year, they’re carried past another risky decision window. March: Start the spring retention push before April and May cancellations hit. This is where we can remind customers why staying on service matters before the DIY thought gets too strong. June: Send vacation-related messaging before July churn hits. Remind customers that service continues while they travel, and they can come home to a clean yard. October: Prepare for winter budget cuts. Instead of letting someone cancel completely, we may offer a lower-frequency winter option when it makes sense. On cancellation: Use a cancellation survey and systematic win-back sequence. We had 58 client runs that were previous cancelled clients returning, so coming back is common enough that it deserves a process. That’s why I think recurring service businesses need to study churn more seriously. New leads and sales matter. But if customers are quietly leaving at predictable points and you’re not watching for it, you’re paying to replace people you could have kept. For me, this has been a reminder that retention can’t just be a vague goal. Do you track when customers leave, or are you mostly finding out after the cancellation request hits your inbox?Strategies for Explaining Your Contract to Your Client
Contracts are a tough subject. First of all, that word in of itself elicits a negative chemical reaction in the brain so don't call it the contract to your customers. It's called an agreement. But just because you have something in the agreement, doesn't mean that you are completely off the hook and they customer reads and understands it. The reason I'm even writing this is every once in a while, a customer approves a time and materials job then our technician shows up and the conditions the customer presented make it impossible to perform the service. In our agreement, we have a "failed job" clause where they get charged $150. Our technician planned their day around the job, we did our best to assess it ahead of time but sometimes the customer doesn't know or hides details. This is clearly stated in our contract. I've tried to "enforce" this a few times but it always leaves a negative taste in their mouth. This also applies to leaving pets out while we are working, change orders and all sorts of things we have written out in a policies and procedures contract. I don't think it's enough to just put it in the contract. Try these things: If the job is big enough, go over all the most important items with them in person. Have a landing page telling them what happens next and who to contact Make a fun video going over some of the items Check This Out Main thing is don't assume they read it because they probably didn't. If you do it in person, use a Plaud unit and send them a summary of the convo after. Don't be that person that tries to just say "well it was in the contract". What is everyone's experience with describing contracts to customers?Using Claude API and Facebook/Instgram API For Social posting
Curious if anyone else here has implemented API's into their websites. I just figured out how to enable Claude API and Facebook/Instgram API's to automaticall generate instagram/facebook descriptions, alt tags, and hashtags by clicking a button. Then I can click another button to uplaod directly to FB and IG. It's made my image gallery uploads and social uploads to my IG and FB pages a breeze. Huge game changer! I even have my stats in my site now and can comment on posts and DM's all through my site without having to go into my social platforms anymore. If anyone would like help with this, please let me know, would be glad to walk you through it.How early is too early to start servicing a customer?
This came up for me because summer routes can get brutal. When temperatures are pushing 95 to 100 degrees, I don’t want my team out in the hottest part of the day if it can be avoided. In our line of work, the job is outside. It’s physical. There’s no shade in a lot of backyards. The heat wears people down fast. So my general opinion is this: If the sun is up, visibility is good, and the technician can clearly see the yard, then it’s reasonable to start service. For pet waste removal, that means we can see the ground, see the waste, safely walk the property, check gates, read yard conditions, and do the job to our standard. I don’t think the clock alone should decide whether it’s “too early.” The bigger question is whether the customer has been properly prepared for how your service operates. If a customer thinks you’re coming between 10 AM and noon, and you show up at 6:30 AM, that’s going to feel wrong to them. If your onboarding explains that service may begin early during summer months, especially to protect technicians from extreme heat, then the expectation is different. Communication is what makes the difference. For us, this is why customer expectations matter so much. You can’t surprise people with an early arrival and then act like they should have known. They need to know upfront: what your service window is whether you give exact arrival times how much notice they get before arrival what happens if dogs are outside what happens if gates are locked why summer routes may start earlier how you handle extreme heat days I’m a big believer in the on-the-way message. If the customer gets a reasonable heads-up before arrival, they can bring dogs inside, unlock the gate, or prepare for the visit. That message matters even more when service starts early. The goal is not to sneak onto a property before people are awake. It is to run the route safely, protect the team, and still give customers enough communication to feel respected. There’s also a real operations side to this. If you wait until late morning to start every summer route, the team may end up doing the hardest part of the day in the worst heat. That can affect: speed morale safety quality callbacks employee retention A customer may prefer a later visit. But the business also has to protect the people doing the work. If we can safely complete a yard at 7 AM instead of 2 PM on a 100-degree day, that’s usually better for the technician and the route. The key is making sure your policy is clear before it becomes a problem. For example: “During summer months, our team may begin routes earlier in the day to avoid extreme heat. You’ll still receive an on-the-way message before arrival so dogs can be secured and gates can be accessible.” That one line can prevent a lot of confusion. This is another example of something that feels small until the business grows. When you’re solo, you can adjust everything manually. Once you have a team, policies matter more. You need a standard that protects the customer, the technician, and the route. How early is too early for your team to start work? And do your customers know your summer service window before the appointment happens?AI Transcription Hack - use Plaud. Thank Me Later
I've got to share this because it's genuinely changed how I run my day, and I think a lot of you dealing with client walkthroughs, team conversations, and constant mental juggling will get a lot out of it too. It's this little device, about the size of a credit card, that sticks on the back of your phone. It records and transcribes conversations, then hands you back a summary. There are a bunch of templates built in depending on what kind of conversation you're having. I originally picked it up to help with walkthroughs. If you're like me, people talk to you about so much stuff during a single job site visit that it's impossible to keep it all straight in your head. Now I've got it recording, and afterward I get a clean summary instead of trying to remember everything or scribble notes while I'm supposed to be paying attention to the person in front of me. Here's the part that's saved me more than once: when a client says "well, I said this" or "you told me that," I can actually go back to the AI summary and say, "here's what was actually said." No more he-said-she-said. It's all sitting right there. But the thing I'm most excited about is what it's done for GSR meetings — goal setting and review meetings. There was a recent Jobber podcast episode that got into these, and I liked the idea, but I had a mental block about actually doing them. I hate the idea of filling out extra spreadsheets and handing my team more stuff to track. It just becomes one more thing nobody keeps up with. So instead, I just run the meeting, let Plaud record it, and have it spit out a summary. That summary becomes my record. No spreadsheet, no separate tracking system, no extra homework for anyone. I just keep the summaries and refer back to them next time. If you're drowning in notes, or you've been putting off something like GSR meetings because of the extra admin, this might be the nudge you need. Worth checking out.Should you fire customers who only want the bare minimum service?
This is a hard one because those customers are still paying you. And when you’re growing, it feels wrong to turn away money. I’ve had to think about this a lot in my own business because the bare minimum customer can quietly become one of the hardest customers to serve profitably. In pet waste removal, this usually shows up with frequency. Someone has 3 or 4 dogs and wants every-other-week service. Or they want monthly service. From the customer’s point of view, they’re trying to save money. I get that. But from the operations side, that yard can become a completely different job. A weekly yard may take 10-15 minutes. That same customer on every-other-week or monthly service may turn into a 30, 40, or 45-minute cleanup. Now the technician is behind. The route gets pushed and is harder on the body. The customer is still expecting it to look great. Plus your business is making less money per hour. That’s where the bare minimum becomes a problem. They may technically be a paying customer, but the job no longer fits the way the business needs to operate. I used to be more flexible with this. I wanted to help people or to lose the sale. And assumed a lower frequency was better than no customer at all. Then I started paying attention to what those jobs were doing to the route. They were taking too long and wearing out the techs. At least from my experience, these types of accounts created more room for complaints. They were lowering the quality of the day for better-fit customers. Eventually, we made the decision to remove monthly service. We also made every-other-week service available only for customers with fewer than 2 dogs. If someone has 3 or more dogs, weekly service makes more sense for the customer, the yard, the technician, and the business. That boundary protects the operation. It also protects the customer experience. Because if the service frequency is too low for the amount of waste being produced, the customer may still blame the company when the yard doesn’t feel as clean as they expected. That creates a bad situation for everyone. And this can show up in other industries too. A customer wants the cheapest maintenance plan but expects premium response time. Or they want the smallest cleanup package but expects the full deep clean. Maybe they'll ask to skip recommended work and then gets upset when the result doesn’t hold up. A customer wants the lowest level of service but still wants the highest level of outcome. That mismatch creates tension. I don’t think every customer who wants a lower option is a bad customer. Some people truly need a temporary down-sell because of finances, travel, life changes, or seasonality. I’m willing to work with that when it still makes sense. But there’s a difference between a temporary adjustment and a customer who consistently wants the cheapest version of the service while expecting the business to absorb the consequences. Those customers can cost more than they pay. Sometimes the best move is to explain the standard clearly: “Based on the number of dogs and the amount of waste, weekly service is the lowest frequency we can offer and still provide the level of service we’re comfortable putting our name on.” That kind of policy may lose some customers. But it can also protect your route, your team, your quality, and your profit. Do you allow customers to choose the bare minimum service, even when you know it may create problems later? Or have you created minimum standards for who you will and won’t serve?
