Jobber missed-call automation: what to wire, in what order

Missed-call automation on Jobber is a voice agent on your existing phone system through Twilio, creating the job or the appointment in Jobber in real time as the call happens, with the SMS agent behind it for confirmations, follow-ups and rebooking. The voice agent is live in 3 to 4 weeks, the SMS agent in 2 to 3.

What does missed-call automation on Jobber look like?

Two modules on one phone line. The voice agent is deployed into your existing phone system through Twilio, so you keep the system you have. On each call it works out what the caller needs, asks the qualifying questions, and creates the job or the appointment in Jobber in real time as the call happens. A call outside its scope is warm-transferred to a person with the caller's name, the issue and the qualifying details. The service page names the share of calls at stake: 60% of service calls come outside business hours.

The SMS agent deploys into the same Jobber account. On the field services agent page it runs confirmations, follow-ups and seasonal rebooking, and the audit before it maps three gaps in Jobber: dormant accounts, rebooking misses and after-hours leakage. The third gap is the missed call; the first two are what the same text channel does once the call is booked.

Review reactivation is added in month 2, once SMS opt-in rates stabilize: job completion in Jobber triggers the review request, typically 2 hours after service, and the requests and rebooking sequences go out through Twilio.

What does the voice agent read and write in Jobber?

As an office names them, Jobber holds a client, a property, a request, a quote, a job with its visits, and an invoice, and Jobber's shape puts the request first; the integration map leaves the API's own object and endpoint names to be verified against your account. The ServiceTitan and Jobber integration map draws the voice agent as four reads and one write. The reads, in the order they happen on a call: the client by phone number, so the agent knows who is calling before the caller says; the property; the job history; and the open windows, from the visits, so it offers a time that is actually free. The reads run live, because a cached schedule offers a window that was taken a minute ago.

The one write comes last, after every slot the booking needs is filled and the caller has said yes: the request or the job, depending on how the office wants a call to land, with the type, the window and the call notes. Then a read-back of what was booked, from Jobber, not from memory, and a quieter write at call end: the summary, the transcript link and the recording. The fallback for the write is a person, and the agent says so rather than reading back a confirmation it does not have.

The credential is issued by your Jobber admin and scoped to the objects on the map, so the agent can change what the map says and nothing else. Draw the map before you connect anything.

Why does a text-back beat a voicemail?

I tell owners the same thing in every working session: a text-back beats a voicemail, and an answered call beats both. A voicemail asks the caller to wait for you, and the field services page says what a homeowner does instead: leaves the voicemail, calls two more companies, and by morning has booked someone else. A text asks the caller a question they can answer with one tap, from the truck or the couch. The one text we carry a number for, the review request 2 hours after the job, averages a 35 to 40% response rate because it reads as a person who did the work checking in. I have no published number for a text sent minutes after a missed call and will not quote one until I have measured it, but I expect it to read the same way: a person answering, not a box collecting messages. So the order I wire on Jobber is the agent answers, the confirmation text follows, and the voicemail box is the last resort, not the front door.

Whether the SMS agent texts back a caller nobody answered, and how soon, is not on a published deployment yet: Details to follow.

How do I count the calls I am missing?

Before anyone builds anything. The missed-call worksheet runs the calculator's formula by hand: missed calls per month, times your average ticket, times your close rate, is the revenue that leaks each month. A missed call is any call that rang and was not answered by a person: voicemail, rang out, or abandoned on hold, after-hours calls included. Pull the last 30 days from your phone system's call log; if it does not list unanswered calls, keep a tally sheet at the front desk for one week and multiply by four.

On the calculator's starting numbers, 100 calls times $500 times 40% is $20,000 a month of leakage, and at the calculator's 60% capture-rate assumption the recovery is $12,000 a month. The 60% is a working number for an estimate, not a promise about your phones. The way to know your real number is to count missed calls for 30 days before go-live and again 30 days after, on the same metric. The before number is the baseline the written ROI commitment is written against; bring it to the working session.

What is the week-by-week plan on Jobber?

For the voice agent, 3 to 4 weeks from kickoff. Week 1 maps your call flows: scripts, booking logic, escalation rules, and the edge cases your CSRs handle from memory. Weeks 2 to 3 train the agent on your services, pricing tiers, service areas and FAQs, alongside the Jobber integration. Week 4 is live calls in shadow mode, then the switch-over. A complicated integration can add 1 to 2 weeks.

For the SMS agent alongside it, the field services plan runs 3 weeks: audit the recurring-revenue gaps in Jobber, wire voice and SMS, shadow mode on a single tech's route for one week, then full rollout at week 3. Most field service engagements start with the voice agent plus the SMS agent, and ROI is typically visible within 60 days.

What we saw in deployment

The published Jobber deployment is on the SMS side. A 3-location cleaning and restoration company in the Southeast, $5M to $8M in annual revenue with 20+ techs, had recurring work but no rebooking system: past customers sat dormant in Jobber and 1-star reviews sat on Google for days. In 3 weeks, as one sprint, we deployed review reactivation and an SMS agent into Jobber and Twilio: week 1 audited the CRM data, segmented the customer base and designed the rebooking sequences; week 2 deployed review monitoring and the SMS agent; week 3 was testing, optimization and handoff. No ongoing retainer; the system runs on its own with monthly check-in calls. The numbers, each dated 2026-02-20 on the case study: rebooking rate on targeted segments increased 2.4x compared to the previous quarter's manual outreach, with no before number stated; within 90 days the client reactivated 340+ dormant customers through automated SMS sequences; negative review response time dropped from 3+ days to under 2 hours after go-live. Read the case study.

What went wrong: on the cleaning deployment the first SMS sequences were too frequent for some customer segments, and a preference center went in after the first week of complaints rather than on day one. On the integration map that is the read a review request makes before it sends, the customer's consent to be messaged and the record of what was sent before, so nobody is asked twice; the same reads belong in front of a rebooking text.

The voice agent's published number is on ServiceTitan, not Jobber. A regional concrete contractor in the Midwest, $10M to $15M in annual revenue, estimated it was losing 15 to 20% of inbound leads to voicemail after hours and at peak call times. We deployed a voice agent into its existing phone system through Twilio, integrated with ServiceTitan dispatch, first deploy in 4 weeks; within 60 days of deployment monthly lead capture was up 23%. Jobber is wired the same way, and a Jobber deployment would carry its own baseline and its own number. Read the case study.

Set out in the agreement