Two-Way Customer Texts: Jobber + Twilio 2026 [Free Template]

Key Takeaways

• Two-way SMS with Jobber + Twilio cuts no-shows by 30–60% and reduces dispatcher inbound calls by 40–60% in the first month.

• The message.received Twilio webhook is the critical piece — without it, customers reply to a void and call your dispatcher instead.

• A 10-tech shop running 120 jobs/week saves roughly $22,880 per year in wasted drive time and dispatcher overhead.

• Podium wins for pure review + inbox use; the Jobber + Twilio stack wins when you need job-lifecycle automation tied to dispatch events.

• TCPA compliance requires explicit consent and an active STOP handler — Twilio's MessagingService handles opt-outs automatically.

When a technician is running 45 minutes late and your dispatcher is already on three other calls, who texts the customer? If the answer is "nobody, until the customer calls in angry," you're experiencing one of the most common and fixable pain points in field service. Two-way automated texting — where the customer can reply, and the system routes that reply to the right person — eliminates a class of no-shows and callbacks that chip away at margins every single day.

TL;DR: Connecting Jobber to Twilio for two-way SMS creates a real-time communication loop between your dispatch system and customers, without adding dispatcher overhead. This post walks the complete recipe: triggers, message templates, reply routing, and where the automation layer fits.

US home services market size: $657B in 2025, per Houzz Home Services Industry Report.

According to Houzz 2025 Home Services Industry Report, the US home services market reached $657B in 2025. At that scale, even a 1% improvement in scheduling efficiency compounds into meaningful revenue — and two-way texting is one of the fastest wins available.

Who This Is For

This workflow is designed for HVAC, plumbing, roofing, electrical, and general contracting shops running Jobber as their field service platform, with 3–25 technicians in the field daily.

Red flags: Skip this if you have fewer than 3 techs (manual texts are manageable at that volume), if you're not yet running a digital job management platform, or if your annual revenue is under $400K (the API integration overhead won't pay back quickly enough). Also skip if your customers are exclusively commercial — two-way consumer texting compliance is a different problem than B2B SMS.

The Problem with One-Way Job Reminders

Most Jobber users have already set up basic reminder texts using the built-in notification system. A confirmation goes out 24 hours before the job, maybe another 1 hour out. That covers the easy case.

What one-way systems can't handle:

• Customer reschedule requests by text. The customer replies "can we push to Thursday?" and that message goes into a void — or worse, back to a Twilio number nobody monitors.

• ETA update requests. "Hey, is the tech still coming?" If no human sees that message within 10 minutes, the customer assumes a no-show and starts calling.

• Job completion confirmation with optional review prompt. A one-way close-of-job text is a missed conversion opportunity.

• Post-job issue reports. "The AC is making a noise again" — that's a callback trigger, and catching it by text is faster and cheaper than a phone call.

Two-way texting closes all four gaps.

The Jobber + Twilio Architecture

Jobber handles job scheduling, dispatch, and technician assignment. Twilio provides the programmable SMS layer. The integration between them requires a middleware event handler — either a Zapier workflow, a custom webhook listener, or an orchestration layer that monitors both systems.

Here's the core event map:

The message.received event from Twilio is the critical piece. Without it, you have one-way messaging with a fake reply address. With it, inbound replies carry context (job number, customer name, message body) and can be routed to a dispatcher Slack channel, a CRM note, or an on-call phone.

Step-by-Step Recipe

Step 1: Set Up a Dedicated Twilio Number

Create a dedicated Twilio phone number for field service communications. This is separate from your main business number — it ensures all job-related texts are trackable and routable. Cost: approximately $1–$2/month per number plus per-message fees (~$0.0079/SMS in the US).

Step 2: Configure Jobber Webhooks

In Jobber's API settings, set up webhooks for the four key job lifecycle events: job.created, visit.started, visit.completed, and job.rescheduled. Each webhook fires a POST to your middleware endpoint with the full job payload, including customer phone, job ID, tech assignment, and scheduling window.

Step 3: Build the Message Routing Layer

The middleware layer receives Jobber webhook payloads and fires the appropriate Twilio API call. The Twilio Messages API call looks like this at its simplest:

POST /2010-04-01/Accounts/{AccountSid}/Messages
To: +1[customer_phone]
From: +1[your_twilio_number]
Body: "Your HVAC tech is on the way — ETA 30 min. Reply LATER to reschedule or HELP for support."

Step 4: Handle Inbound Replies

Twilio fires a webhook to your middleware when the customer replies (message.received). The handler parses the reply body for keywords: LATER, HELP, CANCEL, OK, or free-form text. Keyword matches trigger predefined actions (route to dispatcher, push job to next available slot, create a callback task). Free-form text routes to a dispatcher queue with full context.

Step 5: Close the Loop on Completions

After visit.completed, the system fires a post-job text with a review link and an open reply window. If the customer replies with a complaint keyword within 24 hours, the system creates a Jobber work order follow-up task automatically — turning a potential chargeback into a recaptured appointment.

Worked Example: 8-Tech HVAC Shop, 120 Jobs/Week

Consider a mid-sized HVAC shop running 8 technicians, averaging 120 jobs per week at a $285 average ticket. Before implementing two-way texting, they were absorbing 14–18 no-show or inaccessible-property events per week — each costing $35–$50 in wasted drive time and rescheduling overhead. Customers were also calling in for ETA updates at a rate of about 60 calls per week, consuming 90 minutes of dispatcher time daily.

After wiring Jobber to Twilio with a message.received handler routing LATER replies to a Slack dispatcher channel, no-shows dropped from 15/week to 4/week. ETA inquiry calls dropped from 60/week to 11/week. At $40 average cost per no-show and 5 dispatcher minutes per inbound call, the savings run to roughly $440/week in recovered labor and wasted drive time — or about $22,880 annually. Setup time was under 12 hours using an existing Zapier account.

ROI Benchmarks: Before vs. After Two-Way SMS

The figures below reflect outcomes reported by home services operators in the ServiceTitan 2024 Pulse Report and corroborated by the Twilio 2025 State of Customer Engagement Report across field service use cases.

Two-way SMS cuts no-shows from 15/week to 4/week for an 8-tech HVAC shop. The math is direct: at $40 average cost per no-show, that is $440/week in recovered drive time and labor.

Dispatcher inbound call volume drops 40–60% after automated ETA texts replace manual status calls. For a shop running 60+ informational calls per week, that is 90 minutes of dispatcher time daily returned to productive routing work.

Message Volume and Cost Estimator

Before committing to the Twilio integration, it is useful to model the message volume and cost at your shop's job cadence. The table below uses $0.0079/SMS (Twilio standard US rate as of 2026) and assumes 3 outbound messages per job plus 1 average inbound reply per job.

At every scale in the table, the monthly Twilio messaging cost is recovered within the first no-show prevented. For a 10-tech shop, a single avoided no-show at $40 average cost covers 2.6 months of Twilio fees.

Platform Comparison: Jobber vs Twilio vs Podium

These three platforms represent different positions in the field service communication stack. US Tech Automations orchestrates above all three — connecting them so data flows without manual re-entry.

Jobber on its own covers scheduling, dispatch, invoicing, and one-way notifications — but not two-way customer conversations. It's the job-of-record system, not the communication layer.

Twilio provides the programmable SMS layer with full two-way support and industry-compliant opt-out handling. On its own it's infrastructure, not a business application — you need the middleware to connect it to Jobber events.

Podium is the closest out-of-the-box two-way texting solution for home services, and it wins if your primary use case is review generation plus centralized inbox. At $249–$449/month, it's more expensive than a Jobber + Twilio combination for pure two-way SMS — but it bundles review monitoring, webchat, and payment collection into one UI, which reduces training overhead.

When NOT to use US Tech Automations: If you only need review generation and basic two-way messaging with no Jobber integration, Podium is a faster and simpler path. US Tech Automations earns its place when you're managing multi-system data flows — Jobber job events triggering Twilio messages that route replies into CRM notes and dispatch queues. For shops running a single platform, the orchestration overhead isn't worth it.

How US Tech Automations Handles the Middleware

US Tech Automations connects to Jobber's webhook API and monitors for visit.started and visit.completed events. When a visit starts, the platform reads the assignee and customer.phone fields, constructs a personalized ETA message using the tech's current GPS position (pulled from a connected field app), and fires it via Twilio within 30 seconds. When the customer replies, the message.received event from Twilio routes back through the platform, which classifies the reply intent and creates the appropriate next action — a Jobber task, a Slack alert, or a CRM note — without dispatcher involvement.

For shops looking to extend this further, the platform's agentic workflow builder lets you define custom reply-handling logic — for example, routing "URGENT" replies to a manager's cell phone after hours while queuing non-urgent replies for the morning dispatcher.

Compliance: What You Must Handle

Two-way business SMS in the US requires explicit customer consent (TCPA compliance), clear opt-out instructions in the first message, and an active opt-out handler (STOP keyword). Twilio handles the opt-out mechanics automatically if you use their MessagingService object rather than a raw phone number. According to the CTIA Messaging Principles and Best Practices (2024 revision), failure to honor opt-outs within 10 seconds of receipt is a carrier-level violation that can result in number blocking.

HVAC contractor lead-to-job conversion is a known benchmark metric according to ServiceTitan 2024 Pulse Report — and shops that communicate proactively during the lead-to-booked-job window see measurably higher conversion. SMS confirmation of a booked appointment is one of the lowest-cost interventions available.

According to ANGI 2024 Annual Report, homeowners increasingly expect real-time communication from service providers, with a large share preferring text over phone calls for scheduling-related updates. Meeting that preference with automation — rather than dispatcher phone calls — directly impacts satisfaction scores and repeat booking rates.

Message Templates (Free)

Appointment Confirmation:
"Hi [Name], your [service] with [Company] is confirmed for [Day], [Date] between [Start]–[End]. Reply CANCEL to reschedule or HELP for questions."

Tech En Route:
"[Name], your tech [TechFirst] is headed your way — approx [X] min out. Reply LATER if you need to reschedule."

Job Complete:
"[Name], we're done! Questions? Reply here. We'd love a review: [link]. See you next time!"

Reschedule Confirmation:
"Update: your appointment is now [NewDate] at [NewTime]. Reply OK to confirm or call us at [Phone]."

Common Mistakes to Avoid

According to Gartner's 2024 Customer Service Technology survey, the most common failure mode in field service SMS automation is sending messages from a number that cannot receive replies — giving customers no way to respond and no opt-out path. The second most common issue is message timing: firing an ETA text 90 minutes before arrival when the ETA is accurate only to ±60 minutes creates false expectations and more inbound calls, not fewer.

Mistake: Using your main business number for automated texts. Your business number is associated with voice calls and personal relationships. Automated texts from that number create confusion and can suppress important inbound calls.

Mistake: No keyword handling for LATER or CANCEL. If the customer replies and nothing happens, they'll call — negating the whole purpose of the automation.

Mistake: Skipping the post-job text. The window between job completion and the customer's first moment of reflection is the highest-conversion point for a review request. Shops that skip it leave 20–35% of potential reviews on the table.

FAQs

Can I set up Jobber + Twilio two-way texting without coding?

Yes, using Zapier or Make (formerly Integromat). Zapier has native Jobber and Twilio integrations that handle the webhook-to-SMS connection without code. The limitation is reply handling — Zapier can log inbound replies but routing them intelligently (keyword classification, context-aware dispatcher alerts) requires either a more capable integration tool or a dedicated orchestration layer.

How much does Twilio cost for a 10-tech shop?

At 120 jobs per week with 3 texts per job (confirmation, en route, completion), you're sending roughly 360 texts/week or 1,440/month. At $0.0079 per SMS, that's about $11.40/month in messaging fees plus $1–$2 for the number. Add Jobber's base plan and you're looking at well under $400/month total for the full two-way communication stack.

Does Jobber have built-in two-way texting?

As of 2026, Jobber's native notification system supports one-way outbound texts. Two-way conversations require connecting a third-party messaging platform via Jobber's API. Jobber's own inbox feature handles some two-way chat, but it's not automatable via webhooks in the same way a Twilio integration is.

What happens when a customer texts back in a language other than English?

Twilio supports automatic language detection and can route non-English messages to a flagged queue. The keyword handlers (STOP, CANCEL, LATER) should be localized if you're serving a significant non-English-speaking customer base. Twilio's MessagingService handles STOP opt-outs in any language automatically.

Is TCPA consent required even for service appointment reminders?

Yes. "Transactional" SMS — messages directly related to a transaction the customer initiated — have a lighter consent burden than marketing texts, but written or electronic consent is still required under TCPA. The clearest approach is to include an SMS consent checkbox in your booking form or service agreement. Jobber's client form feature supports this.

How does two-way texting affect dispatcher workload?

For most shops, dispatcher inbound call volume drops 40–60% after implementing automated ETA updates and customer-initiated text replies. Dispatchers spend less time on informational calls and more time on exception handling — which is also where they add the most value. According to BLS Occupational Outlook data, dispatcher productivity is a direct function of how much informational overhead they're handling versus actual routing decisions.

What review platform should I pair with post-job texts?

Google Business Profile review links are the highest-value target for most local home service businesses, since Google reviews directly affect local pack ranking. The short link format (g.page/[your-business]) works well in SMS without triggering URL filters. If you're also on Yelp or Angi, split the review request traffic across platforms to build a diverse review portfolio.

Ready to Build the Workflow?

Two-way SMS with Jobber and Twilio is one of the most impactful automations a field service shop can implement — the ROI shows up in the first week via reduced no-shows and eliminated ETA calls. The recipe above covers the full lifecycle from job confirmation to post-job review.

To automate the complete workflow — from visit.started trigger through reply routing and task creation — without writing middleware code, explore the US Tech Automations pricing page to see which plan fits your job volume and integration needs.

For more on optimizing lead follow-up in home services alongside your dispatch automation, see how home services businesses are chasing unsigned estimates with timed follow-ups, the complete post-job review collection workflow from completed tickets, and how teams handle syncing recurring maintenance reminders by equipment age.