Recover No-Shows: Two-Way Job Texts in Jobber 2026

A customer waits all morning, the technician is running 90 minutes late, and nobody texts them. Half an hour later that customer is gone — a wasted truck roll and a one-star review in the making. Two-way customer text updates fix this. When every job automatically sends an "on the way" message with a live ETA, and the customer can text back to confirm or reschedule, missed appointments fall and trust rises. Jobber manages the job and Twilio carries the SMS, but neither one orchestrates the ETA logic or routes inbound replies on its own. This recipe shows exactly how to wire them together.

Key Takeaways

• Two-way customer text updates send automatic ETA and status messages from Jobber jobs and route customer replies back to the office through Twilio.

• Most homeowners now expect proactive text updates from service contractors according to the ServiceTitan 2024 Pulse Report.

• Jobber triggers the workflow and Twilio sends the SMS, but the ETA calculation, reply routing, and reschedule handling need an orchestration layer between them.

• This recipe lays out the trigger, the message templates, the inbound-reply branch, and the failure handling step by step.

• US Tech Automations connects Jobber and Twilio so the right text fires at the right moment and every reply lands where a human can act on it.

What is two-way customer text updates? Two-way customer text updates is an automated SMS workflow that sends job status messages from your field service software and lets the customer reply, with those replies routed to staff. The large majority of homeowners now coordinate home services digitally, according to the ANGI 2024 Annual Report, making texting the expected channel.

TL;DR: Two-way text updates wire Jobber job events to Twilio SMS so customers get an automatic ETA and can text back to confirm or reschedule. Most homeowners expect proactive contractor communication, according to the ServiceTitan 2024 Pulse Report, and missed-appointment recovery is the fastest payback. If your firm runs Jobber and books more than 15 jobs a day, this recipe recovers no-shows within the first week.

Workflow Overview: What This Recipe Does

This recipe builds one connected workflow with four moving parts. First, a Jobber job event — visit assigned, technician en route, job completed — fires a trigger. Second, US Tech Automations formats a message and an ETA. Third, Twilio delivers the SMS from a number the customer recognizes. Fourth, when the customer replies, the orchestration layer reads the inbound message and routes it: a confirmation closes the loop, a reschedule request opens a task, and anything ambiguous lands in front of a dispatcher.

Who this is for: Home services firms with 8 to 60 field staff, $1M to $15M in revenue, running Jobber for scheduling and dispatch, losing measurable revenue to no-shows and "where is my technician" phone calls. Red flags: Skip this build if you dispatch fewer than 10 jobs a week, have no consistent customer phone-number data in Jobber, or still run paper work orders — get the data foundation solid first.

The reason this needs orchestration is timing and routing. Contractors who communicate proactively see fewer cancellations, but a raw Jobber-to-Twilio connection only pushes a message — it cannot decide when the ETA is accurate or what to do with a reply that says "can we move to Thursday." US Tech Automations supplies that decision logic.

The Trigger: Which Jobber Events Start the Workflow

A good texting workflow is event-driven, not time-driven. Use three Jobber events as triggers. The visit-scheduled event sends a confirmation when the job is booked. The technician en route status — set when the tech taps "on my way" — sends the live ETA text. The job-completed event sends a thank-you with a review link.

Who this is for: Dispatchers and office managers who own the Jobber account and want to stop fielding "what time will you arrive" calls. Red flags: If your technicians do not reliably update job status in the Jobber mobile app, fix that habit first — the en-route text is only as accurate as the status change behind it.

US Tech Automations subscribes to these Jobber events and acts as the workflow's brain. Homeowners increasingly judge contractors by responsiveness, according to the ANGI 2024 Annual Report, and an event-driven trigger guarantees the customer hears from you at the exact moment they are wondering where you are.

Building the Outbound Message Templates

Each trigger needs its own message template. Keep them short, name the company, and include the one piece of information the customer wants. Templates live in the orchestration layer, which merges Jobber data — customer name, appointment window, technician name — into the text before handing it to Twilio.

Here is the contiguous build sequence for the outbound messaging:

1. Provision a Twilio number. Buy a local SMS-capable number in Twilio so texts come from a recognizable area code.

2. Connect Twilio to US Tech Automations. Add the Twilio credentials so the platform can send and receive messages.

3. Connect Jobber to the platform. Authorize the Jobber account so events flow in and customer data is readable.

4. Write the confirmation template. "Hi {first name}, you're booked with [your company] on {date} between {window}. Reply C to confirm or R to reschedule."

5. Write the en-route template. "Hi {first name}, {technician} is on the way and will arrive in about {ETA}. Reply with any access notes."

6. Write the completion template. "Thanks {first name}! {technician} has wrapped up. We'd appreciate a quick review: {review link}."

7. Map the merge fields. Connect each placeholder to the matching Jobber field so no message ships with a blank.

8. Set quiet hours. Tell the platform not to send between 9 PM and 8 AM so a late job completion does not text a customer at midnight.

9. Test with an internal number. Run each trigger against a staff phone before any customer sees a message.

The US home services market exceeds $600 billion in annual spending according to the Houzz 2025 Home Services Industry Report — a market where communication quality is now a competitive differentiator, not a nicety. US Tech Automations makes that quality consistent across every job.

The ETA Logic: Where Most Builds Fail

A confirmation text is easy. A credible ETA text is hard, and it is where naive integrations collapse. If you simply text "arriving soon," customers learn to ignore it. The ETA must reflect the real situation: the technician's current job, drive time, and a buffer.

The orchestration layer calculates the ETA when the technician marks en route, optionally factoring drive time from a mapping service, and writes a specific window into the text. If the technician falls behind on the prior job, the en-route event simply fires later — the customer always gets a fresh number, never a stale promise. An accurate arrival window is the single most-requested update from service customers, and respecting their time visibly drives more repeat business.

The Inbound Branch: Routing Customer Replies

The "two-way" in two-way text updates is the half most contractors never build — and it is the half that recovers revenue. When a customer texts back, Twilio receives the message and hands it to the orchestration layer, which classifies the intent and routes accordingly.

• A reply of C or "confirm" marks the Jobber visit confirmed and exits quietly.

• A reply of R or "reschedule" creates a high-priority Jobber task and notifies the dispatcher to call.

• An access note ("gate code 4412, dog is friendly") attaches to the Jobber job so the technician sees it.

• Anything ambiguous is forwarded to a shared inbox or staff number for a human to read.

Without this branch, a customer who texts "can we move this" gets silence — and silence is how a reschedule becomes a no-show. Responsiveness is among the strongest drivers of homeowner satisfaction in a $600 billion market, according to the Houzz 2025 Home Services Industry Report, so routing every reply to a human or a workflow is not optional.

Handling Failures and Edge Cases

A production workflow has to survive bad data. Build three guards. First, if a Jobber job has no valid mobile number, the workflow skips the text and flags the job so the office can collect the number. Second, if Twilio reports an undelivered message, the workflow retries once and then alerts staff to phone the customer. Third, honor opt-outs — a customer who texts STOP is suppressed from all future automated messages, which Twilio enforces and US Tech Automations records.

These guards keep the system trustworthy. A workflow that silently fails is worse than no workflow, because the office assumes the customer was notified when they were not. US Tech Automations surfaces every skipped or failed message so a human always has the chance to step in.

How the Tools Compare

Contractors building a texting workflow usually weigh Jobber, Twilio, and Podium against each other. Each owns a different slice. Jobber is the field service system of record. Twilio is the messaging carrier. Podium bundles reviews and a shared inbox for customer messaging. None of the three, alone, runs the event-driven ETA logic and inbound reply routing that recovers no-shows — that coordination is the orchestration layer's job.

The honest read: if you simply want a review-and-messaging inbox, Podium is a fair standalone buy, and Jobber's own notifications cover light needs. The orchestration layer earns its place when the ETA timing and reply routing must work as one automated system.

When NOT to use US Tech Automations

US Tech Automations orchestrates above Jobber and Twilio, which is the right architecture when you need event-driven timing, ETA logic, and inbound reply routing working as one system. It is overkill in two situations. If you only need a single, manually sent confirmation text per job, Jobber's built-in client notifications may be enough on their own. And if your shop runs under 10 jobs a week, the office can simply text customers directly without any automation layer. Choose the orchestration layer when message volume and routing complexity exceed what a person can reliably handle by hand.

Glossary

Two-way SMS: A texting workflow where outbound automated messages and inbound customer replies both flow through the same system.

ETA logic: The calculation that turns a technician's en-route status, drive time, and a buffer into a credible arrival window.

Trigger event: A change in Jobber — such as a visit being scheduled or a technician marking en route — that starts an automated workflow.

Merge field: A placeholder in a message template that is replaced with live job data before the text is sent.

Inbound routing: The logic that classifies a customer's text reply and directs it to the correct task, note, or staff inbox.

Opt-out (STOP): A customer's request to stop receiving automated texts, which is legally honored and recorded permanently.

Orchestration layer: Software that connects Jobber, Twilio, and other tools and runs the cross-tool logic none of them perform alone.

Frequently Asked Questions

Can Jobber send two-way text messages on its own?

Jobber includes basic client notifications and can send some outbound texts, but it does not provide full two-way routing — classifying inbound replies and turning a "reschedule" into a dispatcher task. Twilio carries the messages but supplies no logic. US Tech Automations connects the two and adds the ETA calculation and reply-routing layer that makes the workflow genuinely two-way.

Why use Twilio instead of Jobber's built-in texting?

Twilio gives you a dedicated, programmable phone number and reliable delivery reporting, which is what an event-driven workflow needs. It also enforces opt-out compliance automatically. The orchestration layer uses Twilio as the carrier while handling the timing, templates, and inbound branching that Twilio itself does not provide.

How accurate are the ETA texts?

The ETA is calculated when the technician marks en route in Jobber, so it reflects their actual current position rather than an optimistic guess. The workflow can factor drive time from a mapping service and add a buffer. If the technician runs late on a prior job, the en-route event simply fires later, so the customer always receives a fresh, honest window.

What happens when a customer replies to a text?

Twilio receives the inbound message and passes it to the orchestration layer, which classifies the intent. A confirmation marks the Jobber visit confirmed, a reschedule request creates a dispatcher task, an access note attaches to the job, and anything unclear is forwarded to a staff inbox. No reply is ever left unread.

Will this stop us from calling customers entirely?

No — and it should not. The workflow handles routine status updates and confirmations, freeing the office from "where is my technician" calls. Reschedules and ambiguous replies still route to a person, because rebooking a job is a conversation. US Tech Automations removes the repetitive texting, not the human judgment.

How do we stay compliant with texting rules?

Customers must be able to opt out, and a STOP reply suppresses all future automated messages — Twilio enforces this and the workflow records it. Quiet hours prevent late-night texts, and messages always identify your company. Build the workflow to text only customers who have an active job, not cold marketing lists.

How long does it take to build this workflow?

A focused team can stand up the full recipe in about one week: provisioning the Twilio number and connecting accounts on day one, building and mapping templates over the next two days, and testing the trigger and inbound branches before going live. The build is short because the Jobber and Twilio connectors and the routing logic are configured rather than coded.

Conclusion

Two-way customer text updates turn the most common service-business failure — the silent late arrival — into a recoverable, automated touchpoint. The recipe is concrete: pick the Jobber trigger events, write tight message templates, build credible ETA logic, route every inbound reply, and guard against bad data. Jobber and Twilio each do one part well, but the ETA timing and reply routing that recover no-shows live in the orchestration layer between them.

US Tech Automations wires Jobber and Twilio into one workflow so every job sends the right message at the right moment and every customer reply reaches a person who can act. See the platform in action and review plans at US Tech Automations pricing. To go further, the booking confirmation reminders guide covers confirmation automation, the emergency dispatch workflow with Kickserv and Twilio extends SMS into urgent jobs, and the crew dispatch scheduling optimization guide shows how dispatch and messaging connect.