How to Figure Out Who to Call Next in Jobber

Hatch's 2025 Home Improvement Industry Report puts the multi-touch follow-up response rate at 89.86% vs 32.39% for a single touch. The gap between a $1M shop and a $5M shop is mostly the discipline of "who do I call next?"

Jobber gives you a few tools for this. Quote follow-up reminders. The Sales Pipeline. The Requests view. The Job Follow-ups Report. Each one shows a slice of the answer.

The full answer (the customer who replied to your quote in Gmail two days ago, the one who called and hung up at 7:42 AM, the appointment that just got cancelled and freed up a slot) lives in three or four systems at once. This walks the Jobber-only workflow first, then names the gaps.

Start With the Sales Pipeline

If you are on the Connect plan or higher, Pipeline in the side nav is your starting view.

It is a kanban board with a column per stage: New Request, Assessment Scheduled, Quote Sent, Awaiting Response, Won, Lost. Per the Sales Pipeline help article, each card shows the client name, quote total, and how many days the card has been in its current stage. Anything camping in Awaiting Response for 14+ days is what we walk through in revive cold leads in Jobber.

Daily triage rule:

1. Sort by days in stage descending.
2. Anything in Quote Sent or Awaiting Response for more than 3 days gets a callback today.
3. Anything in Assessment Scheduled for more than 7 days needs a confirmation text.

That alone runs you a 6-12 person callback list every morning. Most owners we talk to do not even open this view consistently.

Use Quote Follow-Up Reminders

Jobber's quote follow-up feature (available on select plans per the Quote Approvals help article) automates two things.

Automatic follow-up message. Jobber sends an email or text reminder X days after the quote was sent, in the same channel the quote went out in. You set the day count under Settings > Communications > Quote Follow-ups.

Reminder in your schedule. Jobber adds a red reminder card to the schedule of the user who created the quote. The reminder defaults to a phone-call follow-up, exactly the "who do I call next?" trigger.

Two settings worth changing from default:

• Days until follow-up. Default is usually 7. The data says 2-3 is the right window. Per Jobber's own follow-up guidance, if the customer has not responded inside 2-3 days, the deal stalls.
• Days until auto-archive. Default is 90. If you want stale-quote pressure on your pipeline, drop it to 45 or 30.

Text Clint: "who should I call this morning?"

Run the Quotes Report Filtered for Awaiting Response

Pipeline is the quick view. The Quotes Report is the full view.

Open Insights > Reports > All Quotes. Filter:

• Status: Awaiting Response, Changes Requested
• Sent date: last 30 days
• Sort: total descending

Now you have every open quote with the highest dollar value at the top. The high-ticket awaiting-response quotes are the calls that pay back the time.

Add columns for Lead Source and Salesperson if they are not already on. Lead source helps you prioritize (referral leads close 2-4x more than cold web leads). Salesperson tells you whose pipeline is stalling.

A plumbing owner on r/sweatystartup posted in 2024: "I started running this report every Monday morning and assigning the top 10 to my CSR for callback. Booked rate jumped from 22% to 38% on quotes over 14 days old."

That is the move. The report is one filter away. The discipline is the constraint.

Job Follow-Ups Report for Completed Work

Different list, different purpose. The Job Follow-Ups Report under Insights surfaces customers whose jobs were completed but who have not received a follow-up yet.

This is where reactivation and review-ask outreach starts. Customers who just got a great service experience are warm for upsell, repeat work, or a referral ask. The report shows you the warm list.

Per Jobber's help center, the report cannot be exported to CSV, but you can use it as a manual callback queue.

Pipeline Lost Reasons Tell You Who to NOT Call

When you mark a Pipeline card as Lost, Jobber prompts for a reason. Keep this discipline.

Three months in, the Lost report tells you a story:

• "Price too high" wins lost: not callback candidates this quarter. Maybe next quarter when financing changes.
• "Went with another contractor" lost: dead, do not waste calls.
• "Not ready, timing" lost: the gold mine. These are customers who genuinely want to do the work later. They go on a 30-60-90 day callback queue.

The Sales Pipeline summary surfaces 30-day Won and Lost totals. Without categorized lost reasons, the data is useless. With them, the "Not ready, timing" bucket alone is usually a 5-10% lift on next quarter's revenue.

Text Clint: "show me lost deals tagged 'not ready timing' from 60-90 days ago"

Where Jobber Stops Telling You Who to Call

Jobber's view of "who to call next" is bounded by what is in Jobber. Three callbacks live outside.

Missed calls

The CallRail integration (per the Jobber and CallRail integration article) creates a Jobber Request for every inbound call. It does not flag missed calls separately. A Request created at 7:42 AM looks the same as a Request from a 12-minute conversation.

Worse, CallRail does not pass voicemail transcripts or text messages to Jobber. If the customer left a voicemail saying "yes I want to book," that message lives in CallRail, not in the Jobber Request.

A roofing owner posted at the Jobber community forum in 2024: "We had 47 missed calls last quarter. CallRail logged them all. Jobber created Requests for them. Nobody on our team looked at the Request feed every hour, so 19 of those never got called back. Lost an estimated $42k of work." That bleed shows up cleanly in a Jobber lead audit for revenue leaks.

That is the gap. The data is there. The triage is not. We covered the AI missed-call follow-up agent for contractors build pattern in another post.

Gmail replies on Jobber quote emails

Quotes go out from Jobber. The customer hits Reply on the email. The reply lands in your Gmail inbox, not on the Jobber quote record.

Jobber's quote shows "Awaiting Response" forever, even after the customer replied. The follow-up reminder fires anyway, telling you to call a customer who already wrote back two days ago.

Worse case we have seen: a CSR called a customer to follow up on a quote. The customer had emailed three days earlier saying "yes, please book me Tuesday." Nobody saw the email. The CSR's call to "follow up" was the customer's first signal that the company was disorganized. They cancelled.

Calendar gaps that just opened up

A 9 AM job got cancelled. The tech now has a 3-hour window. Who lives nearest, has an open quote, and is most likely to say yes to a same-day install?

Jobber cannot answer that. The pipeline has the open quotes. The calendar has the gap. The customer's address is on the property record. Nothing in Jobber stitches them together as "call this person right now."

Text Clint: "I have a 3-hour gap at 1 PM, who has an open quote within 10 miles of my next job?"

What Clint Synthesizes That Jobber Alone Cannot

This is where the cross-source view earns its keep. The single text "who should I call this morning?" returns:

• Stale quotes from Jobber. Awaiting Response over 3 days, sorted by total.
• Missed calls from CallRail. Inbound calls that never got a callback, from this morning and yesterday.
• Gmail replies on Jobber quote emails. Customers who responded but the Jobber record still says Awaiting Response.
• Calendar gaps. Where the schedule has open slots that could absorb a same-day visit.
• Reactivation candidates. Customers with completed work in the last 12-18 months tagged warm for re-engagement.

Each input is a list. The intersection is the order to call them in. Jobber's pipeline shows you the first list. The other four are why most callback queues are wrong.

We covered the AI customer reactivation playbook for contractors and the questions Jobber's dashboard cannot answer for more of the same pattern.

Text Clint: "rank my callback list this morning by likelihood to close, and tell me why each one's on it"

A Working Daily Routine

For an owner running 6-15 techs through Jobber:

6:30 AM. Text Clint: "who should I call this morning?" Get a 5-10 person list with reason for each.

7:30 AM. Open Jobber Pipeline view, sort by days-in-stage descending. Cross-check Clint's list against the kanban. Add anyone Clint flagged that you want a second look at.

8:00 AM. First three calls go out. The high-ticket awaiting-response quotes get a phone call, not a text.

Throughout the day. Clint flags new missed calls and new Gmail replies as they come in. You answer them within 2 hours instead of letting them age.

End of day. Mark anything dead as Lost in Jobber with a reason. Schedule callbacks for the "not ready, timing" bucket 30-60-90 days out.

This routine works because the question "who do I call next?" gets a real answer in under 10 seconds, every morning, without you doing the spreadsheet math yourself. Jobber's tools are 30-40% of the data. The rest is in the systems Jobber does not see.

Sources

• Jobber Help Center: Quote Approvals and Follow-ups
• Jobber Help Center: Job Follow-ups
• Jobber Help Center: Jobber Workflow Overview
• Jobber Help Center: CallRail Integration
• Jobber Academy: How to Follow Up on a Quote
• Hatch 2025 Home Improvement Industry Report
• Jobber Community Forum: Lead Tracking Discussion