Catch New Requests Before They Go Cold

Every request in Jobber is someone who raised their hand and asked you for work. Requests land at the worst possible times, and the ones that arrive during a busy week can sit unanswered while the client quietly calls your competitor. Ask Claude one question and it sweeps your account through your private Jobber connector (built on MCP), surfaces every request that never got a follow-up, and helps you draft the reply on the spot.

The request sweep: Claude finds every service request still waiting on a first follow-up.

Updated July 2026

The lead that raised its hand and got silence

Requests don't come in when you're sitting at a desk ready to receive them. They come through your website form at 9pm on a Saturday, or from a call someone on the crew typed in between jobs. Jobber logs them faithfully, the notification gets buried under everything else, and by Wednesday nobody remembers there's a homeowner out there refreshing their inbox.

Here's what makes this leak different from every other one: the clock runs faster. An uninvoiced job is still your money next month. An unanswered request belongs to whichever company replies first, and most homeowners fill out three forms in one sitting. Every day of silence is a quiet handoff to a competitor, on a lead you already paid for with the website and the ads that brought it in.

The request sweep, start to finish

Here's the actual workflow, one prompt at a time.

“Go through my Jobber requests and find any that never got a follow up. New requests where nobody scheduled anything, quoted anything, or even left a note.”

Claude pages through your service requests and checks each one for anything behind it: scheduled work, a quote, a note. The ones sitting untouched come back as a list with the client, what they asked for, the property, and how many days it's been since they reached out.

“Draft a quick reply for each one. Apologize for the wait and ask if they still want the work.”

Claude writes a short, personal message per request using the details each client submitted, ready for you to paste into a text or email. Nothing goes to a client until you send it yourself.

“The deck repair one sounds like real money. Put a task on tomorrow morning to call them first thing.”

Three messages: every stalled lead found, a reply drafted for each in the client's own context, and the biggest one turned into a scheduled call-back you can't forget. No scrolling the requests list trying to remember which ones you answered by phone and which ones you only meant to.

And nothing here happens over your head. Claude finds and drafts; every message a client ever sees goes out from your phone or email, on your say-so, after you've read it.

Make it a Monday habit

Requests pile up over the weekend, which makes Monday morning the highest-value two minutes of the week. One prompt with the coffee:

“Any requests still waiting on a first reply? Oldest first.”

The Monday lead sweep

Run the unanswered-request sweep
Reply to the hot ones first, oldest next
Draft a “sorry for the wait, still interested?” note for each
Put a call-back task on the calendar for the big one
Archive the dead and duplicate requests so the list stays honest

This is the earliest checkpoint in the same funnel the other sweeps protect: this one catches leads nobody answered, the won-quote sweep catches work you sold but never started, and the uninvoiced work audit catches work you finished but never billed.

Once a lead says yes to a walkthrough, the next step is usually a number in their inbox: create and send the quote conversationally without leaving the same chat.

Getting set up

If your Jobber account isn't connected to Claude yet, that's a 5-minute job, one time: How to Connect Jobber to Claude. Your connector is private, runs on your own Jobber developer credentials, and costs $47/month after a 7-day free trial. One rescued lead typically covers the year.

Run your first sweep free →

Frequently asked questions

How does Claude know a request never got a follow-up?

It reads through your requests and checks each one for signs of life: is anything scheduled against it, has a quote been created, has anyone left a note. A request still sitting in its original state with nothing behind it gets flagged, and the longer it's been waiting, the higher it sorts.

Will Claude reply to the leads for me?

No. Claude drafts the replies and you send them from your own phone or email. Finding and drafting is the AI's job; anything a client sees stays under your control.

What about requests that are spam or already handled by phone?

Tell Claude the story and it archives them, so the next sweep only shows requests that actually need you. If one comes back to life, unarchiving is one message.

Can Claude book the assessment in the same chat?

Scheduling an assessment on a request happens in Jobber itself. What Claude can do from the chat is draft your reply, drop a task on your calendar so the call actually happens, and once the lead turns into a quote or a job, run everything downstream by conversation.

How often should I run this sweep?

Monday morning, and after any stretch where the phone was busy. Requests are the one place in Jobber where speed beats everything: the first company to answer usually gets the work, so this sweep pays for the whole habit of checking.