A8gent
Build guide - Jobber quotes

Jobber quote follow-up automation: past the two-reminder limit

Jobber sends two automated quote follow-ups on Connect and up. The exact limit, and the four-touch sequence to build alongside it when two is not enough.

A8gent
·

What you get from this guide

  • The exact documented limit: two quote follow-up automations, on Connect and up
  • How to decide whether to extend Jobber's reminders or replace them, and why running both blind causes collisions
  • A four-touch cadence with the reasoning behind every gap
  • Copy for each touch that reads like the estimator wrote it
  • The build against Jobber's webhooks and GraphQL API, including every stop signal

What Jobber actually ships

Start with the fact everyone skips. Jobber's own help documentation is unambiguous: quote follow-ups are available on the Connect plan and up, and there are two quote follow-up automations, so you can send clients up to two reminders about quotes sitting in awaiting response status. The Connect plan lets you customise the timing - the number of days after the original quote goes out that each reminder fires.

That is it. Two messages, timing adjustable, plan-gated. As of August 2026 that is what Jobber documents, and it is worth reading that sentence twice because a striking number of pages ranking for this query imply Jobber has an open-ended sequence builder for quotes. It does not.

Check your own account before you build

Software vendors reorganise plan tiers and feature limits regularly, and a page written in August 2026 is a starting point rather than a contract. Open your Jobber automation settings and count the quote follow-up automations available to you. If you find more than two, that is good news and you can skip most of this guide. If you find none, you are below Connect.

To be fair to Jobber, two configurable reminders is more than several competitors ship, and they send from inside Jobber against real quote status - which means they are accurate and they cost you nothing. Turn them on. This guide is about what happens after the second one.

Why two reminders is not enough

The gap is not really about the number two. It is about where quotes actually die.

A customer who was never going to hire you goes quiet immediately. A customer who was going to hire you but got busy goes quiet in the middle - after the site visit, after reading the quote, somewhere between wanting the work done and getting round to saying yes. Two reminders spaced within the first week or so land during the period when the customer is still actively thinking about it. The message that recovers the quote is usually the one that arrives after they have stopped thinking about it, which is precisely where Jobber runs out of automations.

Be careful with the very specific statistics that circulate on this topic. The claim that some large percentage of sales require a particular number of follow-ups is repeated everywhere and traces back to vendor marketing far more often than to published research. The directional pattern is well enough established across sales research and practitioner reporting to plan around - a meaningful share of deals close after several attempts rather than the first, and quotes never followed up mostly stay quiet - but the number that should drive your decision is your own. Pull your last hundred quotes, count how many were lost after day ten with no further contact, and multiply by your average quote value. That figure is the budget for this build.

The second factor is quote value. On low-value, fast-decision work, two reminders is genuinely sufficient and a third would be pestering. On high-consideration work - system replacements, large installs, anything a household needs to discuss - the decision cycle is longer than Jobber's two reminders comfortably reach. If your business does both, that is an argument for a threshold rather than for one policy.

Native, external, or both

Before writing a single node, decide which of three arrangements you are building. Skipping this decision is the single most common way these projects produce an angry customer.

Three ways to arrange Jobber's reminders and an external sequence
ArrangementHow it worksBest when
Native onlyJobber's two reminders, timing tuned. Nothing external.Low average quote value, fast decisions, no appetite for maintaining a workflow.
ExtendJobber's two run first. Your external sequence starts after the second, adding touches three and four.Most trades businesses. Least work, keeps Jobber's accurate status-aware messages, adds the long tail.
ReplaceJobber's follow-ups off. All touches come from your workflow.You want one cadence, one message template set, and unified reporting across email and SMS.

Extend is the right default. It is the least code, it keeps the two messages that are already accurate and free, and it only asks your workflow to handle the part Jobber cannot. The one requirement is that your external sequence must know when Jobber's second reminder went out, so schedule your first external touch comfortably after it rather than guessing.

Replace is cleaner conceptually and more work in practice, because you are now responsible for messages Jobber was sending correctly for free. Choose it if you want a single set of templates and one reporting view, particularly if you are also sending SMS.

What you must not do is enable Jobber's two, build an external four-touch sequence starting at 24 hours, and let them run without coordination. That is six messages, two of them arriving on the same morning, and the customer reads it as a company that cannot keep track of itself.

The four-touch sequence

The cadence below assumes the replace arrangement, so it covers the full fourteen days. If you are extending, map Jobber's two reminders onto touches one and two and build only touches three and four.

Four-touch quote follow-up cadence for trades work
TouchTimingJob of the message
124 hours after the quote is sentConfirm it arrived and invite questions. Low pressure, and it catches the quote that went to spam.
2Day 3Add something useful rather than asking again: current availability, a scope clarification, a note specific to their job.
3Day 7Ask the direct question. Are we going ahead, and what would help you decide? This is where the price objection surfaces.
4Day 14Clean close-out. Say you will stop chasing, note when the pricing expires, keep the door open.

Touch four earns its place more than people expect. Explicitly saying you will stop chasing frequently produces a reply from customers who felt awkward about the silence, and it protects the relationship for the next job even when this one is lost. It also gives you clean data: a quote that goes past touch four is genuinely closed rather than sitting in a list forever.

Do not extend past four on ordinary residential work. Long-cycle jobs - commercial, insurance work, anything waiting on a third party - justify a slower tail at day 30 and day 90, framed as a genuine status question rather than another sales push.

Message copy for each touch

Fill the braces from the Jobber quote record. Keep the amount and the job description as literal fields so nothing is ever paraphrased into something you did not quote - that is a real risk if you let a model write the whole message rather than personalise one line of it.

Touch 3 - day 7 (email or SMS)

Hi {first_name},

Checking in on the quote for {job_description}
({amount}), quote {quote_number}.

Are you looking to go ahead, or has something changed?
If it is the price, the scope, or the timing, tell me
which and I will see what I can do. A no is completely
fine too - it just helps me plan the schedule.

{sender_name}
{business} - {phone}

Touch 4 - day 14 (email)

Subject: Closing out quote {quote_number}

Hi {first_name},

I will stop chasing you on the {job_description} quote -
I know it is not the only thing on your plate.

The {amount} holds until {expiry_date}. If you want to
pick it up after that, message me and I will re-check
the numbers against current material prices.

Thanks for thinking of us.

{sender_name}
{business} - {phone}

The general quote follow-up guide carries the full template set for all four touches in both email and SMS lengths, including the earlier touches this page compresses. The copy rules that matter more than the wording are the same everywhere: send from a real person, keep every message shorter than the quote itself, thread later touches onto the original email rather than starting new subjects, and never open with "just following up" twice in one sequence.

Building it against Jobber's API

Jobber has a GraphQL API and webhooks, and n8n has no Jobber node, so every step below runs through the generic HTTP Request node. The Jobber and n8n integration guide covers the OAuth flow, the required headers, and webhook signature verification in full detail. Do that first; this section assumes it is working.

1

Trigger on the quote reaching awaiting response

Subscribe your app to the relevant quote topic in Jobber's Developer Center and point it at an n8n Webhook node. Verify the HMAC signature, then query the quote by id over GraphQL for quote number, status, total, client name, email, and mobile. Branch immediately on status: only quotes genuinely awaiting a response enter the sequence.

2

Write the follow-up record

One row per quote in a sheet, Airtable base, or Postgres table: quote id, contact details, amount, sent timestamp, status = open, step = 0, and next_touch set to your first gap. If you are extending Jobber's reminders rather than replacing them, set that first next_touch after Jobber's second reminder is due, not at 24 hours.

3

Build every stop listener before any send

This is the step people build last and should build first. Inbound email replies via a Gmail or IMAP trigger, inbound SMS via your messaging provider's webhook, and Jobber's own quote status change webhook for approved, converted, or archived. Each one finds the matching record and sets status = stopped with a reason and timestamp. Also give the team a one-click manual stop, for the very common case where the estimator spoke to the customer on the phone.

4

Sweep hourly rather than waiting

A Schedule trigger every hour reads records where status = open and next_touch is in the past. Multi-day wait nodes do not survive restarts, redeploys, or plan limits, and a stranded sequence is worse than no sequence. An hourly sweep is more than precise enough for a cadence measured in days and is trivially resumable.

5

Re-check, guard, send, advance

For each due record: re-read the stop status, apply the quiet-hours guard in the customer's timezone, send the template for the current step, log it, increment step, and set the next next_touch. After the final step set status = closed_no_response. Never let a record loop back to step one.

6

Push the outcome back into Jobber

This is the step that separates a real integration from a spreadsheet with opinions. When the sequence ends, write a note onto the Jobber client or quote over the GraphQL API recording what was sent and what happened. The estimator then sees the follow-up history in the place they already work, rather than having to remember a second system exists.

7

Escalate the big ones to a human

Set a value threshold. Quotes above it skip the automated sequence entirely and create a task for the person who walked the site, with the quote attached. Automate the long tail and protect the top end - a twelve thousand dollar job deserves a phone call, and a templated nudge on it reads as carelessness.

Where these builds go wrong

  • Leaving Jobber's two reminders on while an external sequence starts at 24 hours, so the customer gets doubled up.
  • Triggering on quote created rather than quote sent, so customers are asked about a quote that has not reached them.
  • Multi-day wait nodes instead of a state table, then losing or duplicating sequences on a restart.
  • Checking the stop condition only when a reply arrives, rather than immediately before every send.
  • Running email and SMS as two sequences with separate state, so a text reply does not cancel the queued email.
  • Sending at 9pm because the quiet-hours guard uses server time rather than the customer's timezone.
  • Never writing the outcome back to Jobber, leaving the estimator blind to what the automation said.
  • Adding SMS in the US without A2P 10DLC registration, so messages are filtered rather than delivered.
  • Automating the follow-up on a five-figure job that deserved a phone call.

If your business runs on Jobber and quotes are your main lead-to-revenue path, this is usually the single highest-return automation available to you - the trigger is clean, the copy is repeatable, and the only judgement involved stays with a human. Sector-specific context is on the HVAC and plumbing and cleaning company pages, and what an automation build actually costs covers the money side if you are pricing the work out. For the wider small-business budgeting picture, see AI automation cost.

FAQ

How many quote follow-ups does Jobber send automatically?
Two. Jobber's help documentation states that quote follow-ups are available on the Connect plan and up, and that there are two quote follow-up automations, letting you send clients up to two reminders about quotes in awaiting response status. You can adjust how many days after the original quote each one sends. That is the documented ceiling as of August 2026, and it is the entire reason this guide exists.
Which Jobber plan do I need for quote follow-ups?
Jobber documents quote follow-up automations as a Connect plan and up feature. If you are on a plan below Connect, there is no native quote follow-up to configure at all, and every touch has to come from outside Jobber. Check your own account rather than trusting any third-party comparison table, including this one, because vendors reshuffle plan tiers regularly.
Can I add a third and fourth follow-up inside Jobber?
Not through the quote follow-up automations, which are documented as two. What you can adjust is the timing of the two you have. Anything beyond the second reminder has to be built outside Jobber, driven by Jobber's webhooks and GraphQL API, which is exactly what the build section of this page walks through.
Will an external sequence and Jobber's own reminders collide?
Yes, if you let them. Jobber's two reminders fire on their own schedule and know nothing about your sequence. The two clean options are to turn Jobber's off and own the whole cadence externally, or to leave Jobber's two in place and start your external touches after the second one has been sent. Pick one deliberately rather than discovering the overlap through a customer complaint.
How do I stop the sequence when a customer replies?
Hold a status field on the follow-up record and set it to stopped on any inbound signal: an email reply, an inbound text, the Jobber quote status changing to approved, converted, or archived, or a job or invoice being created for that client. Re-check that status immediately before every send, not only when the reply arrives, because a reply landing two minutes before a queued message otherwise loses the race.
Does Jobber send follow-ups by text as well as email?
Jobber's client communication settings cover both email and text messaging, but treat the specific channel each automation uses as something to confirm in your own account settings rather than assume. If you add SMS through your own automation instead, you take on US carrier registration yourself - see the A2P 10DLC guide, because unregistered automated texting from a 10-digit number gets filtered rather than delivered.
Is it worth building this if Jobber already sends two?
It depends entirely on your average quote value. Two reminders on a three hundred dollar drain clear is probably enough. Two reminders on a twelve thousand dollar install is leaving winnable work on the table, because higher-consideration purchases take longer to decide and go quiet in the middle rather than at the start. Look at your own quotes that went cold, count how many died after day ten, and the answer will be obvious.
What does it cost to have this built?
A follow-up sequence wired into an existing CRM is one of the cheaper genuinely useful automations, because the trigger is clean and the logic is small. The variable is how much reconciliation your quote data needs first. Our automation build cost page breaks down what drives the number up and down, and we quote a fixed price in writing per scoped workflow after a free consult rather than publishing a package price that would only be a guess at your setup.

Done for you

Want the sequence Jobber cannot build, wired into the quotes you already send?

We build quote follow-up against Jobber's API - the state table, every stop signal, the write-back into Jobber, and the reporting that tells you whether it is winning work. The audit comes first, and it is free.

The consult is free, and you keep whatever we build.

Keep building

The rest of the cluster