Forum Widgets
Recent Discussions
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.If you run a scaled business with office staff, do you use AI for initial lead intake?
Or do you strictly stick to human receptionists? What’s given you the best conversion rate? Now that I operate purely from a management level, eliminating bottlenecks in our sales pipeline is a top priority. We're looking at tools like Jobber’s AI Receptionist to make sure zero phone leads slip through the cracks when our office team is busy, but I hear mixed reviews on how clients actually react to it.
How fast do you call back a missed call before they phone the next company?
A missed call is the moment the customer decides whether to call you or your competitor — and most of them dial the next number on their list pretty fast. What callback window are you aiming for after a missed call, and what has actually worked to hit it when you're tied up on a job? Curious whether you're thinking in minutes or hours, whether the target changes once you're in a van versus in the office, and what you've tried to stay consistent — a shared missed-call list that someone owns, a timer or checklist built into the day, or something else entirely. How do you track whether you're actually hitting the window, and what happens when you miss it? I'm collecting how home service owners handle the gap between the phone ringing and the call being returned — happy to hear what's real, what's aspirational, and what you've given up trying to do.How do you handle after-hours calls once winter emergencies start?
Once winter weather hits, after-hours calls jump and most of them are real emergencies — burst pipes, no heat, a door locked out at midnight. How are you handling that shift without burning out or missing the jobs that actually pay? Specifically curious about three things: how you split call forwarding between on-call techs (or who picks up when you're off), what your voicemail says after hours (do you set a response-time expectation or just take a message?), and what this season costs you in sleep or lost jobs. If you rotate on-call among your team, how do you keep it fair and how do you separate a real emergency from a "can wait till morning" quote? I'm looking at how home service owners protect their weekends and evenings once winter starts — would love to hear what's working and what's worth skipping.How Fast Do You Pick Up a Phone Call or Call Someone Back After a Missed Call?
Curious how everyone here handles this, because a new Jobber survey of recent homebuyers turned up a stat that stuck with me: 15% had to follow up repeatedly just to get a response from a contractor 9% never heard back at all Losing potential business due to something that is not a pricing problem or a skill problem should be a wake up call. In a world where 75% of new homeowners hire a pro within their first two years of buying, being the one who calls back first might be the easiest job you win all week! So, what's your business standard? Do you answer within a certain time frame or let it go to voicemail and call back same day? Are there systems set up so nothing slips through the cracks? 👉 Recent Homebuyer Report: It's got homeowner quotes on what made them trust (or ditch) a contractor, plus a breakdown of how each generation actually finds a pro.When you get busy does your level of service change?
As the pressure builds in the back half of the year, where is your customer experience most likely to slip—and what are you committed to protecting? The reality is that our clients don’t care that it’s summer, we’re extremely busy, or our team is stretched thin. They still deserve the same consistent level of service. That responsibility falls on us. A systemized business shouldn’t have to reinvent how it operates every time things get busy. You should be able to run more clients through the same well-built system without communication, follow-ups, scheduling, or service quality falling through the cracks. If clients are becoming frustrated or important details are being missed, those are leaks in the boat. Being busy may expose them, but it didn’t create them. So, as you head into the busiest part of your year: Where is your customer experience most vulnerable right now? And what system, process, or standard are you committed to strengthening or protecting?
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.How do you ensure automations reflect the high-touch culture you built early?
I’ve been out of daily operations for almost 3 years now. Our growth came from building deep, personal connections with our cleaning clients, but now that I’m not the one answering every call or visiting job sites, I rely entirely on our systems and office staff to deliver that same warm experience. With almost 450 recurring properties, I'm finding it more difficult to rely on human touch to get to everyone. Thoughts?The Customer Notes That Protect Our Technicians
One of the simplest ways we use Jobber is also one of the most important. Customer notes and instructions on jobs. We document things like: gate instructions and what side of the house the gate is on How many dogs they have dogs that need to be secured aggressive dog history property quirks access issues areas to avoid anything that could affect how the technician enters or completes the job If multiple people need to receive the "On The Way" message That information matters a lot more once the owner isn’t the one servicing every property. I’ve had situations where employees were put in unsafe environments because a customer didn’t properly secure a dog. I’ve also been bitten myself. So I don’t want safety information living in someone’s memory or buried in a text thread. If a technician is going to a property, they should be able to open the job and know what they’re walking into before they ever open the gate. That protects the employee, the customer, and the business. What do other owners document in customer notes that your team absolutely needs before arriving on site?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?
