Field service software can add texting with one API: send the appointment window, a "technician is on the way" message and a job-complete note, and take replies into the job record. Each service company gets its own sub-account so its numbers, registration and billing stay separate.

The messages customers want

  • Appointment confirmation with the date and window
  • Reminder the day before
  • Technician on the way, with a time estimate
  • Running late, with a new time
  • Job complete and a request for payment or review

All of these are tied to a job the customer booked, so consent comes from the booking.

Replies belong on the job

A customer who texts "I'm not home yet" should reach the dispatcher. Route inbound texts by the customer's number to the open job and show them in the job timeline. See receiving SMS by webhook.

Build checklist

  1. Store the mobile number in E.164 on the customer.
  2. One sub-account per service company, with its own 10DLC registration.
  3. Send with POST /v1/messages and an Idempotency-Key per job event.
  4. Include the company name in the first text.
  5. Honor STOP and show it on the job.
  6. Hold or reschedule texts that land in quiet hours.

ETA texts

TextWhen to send
Window reminderThe day before, in the customer's daytime
On the wayWhen the technician starts the route
LateWhen the delay passes your threshold

A customer who texted in the last 24 hours can get a reply at any hour. Other texts follow quiet-hours rules based on the recipient's area.

Cost

A typical job might use 4 segments: confirmation, reminder, on the way and complete. At $0.0075 plus a $0.0045 carrier fee per segment, that's 4 times the sum, before any replies. See the pricing page.

The takeaway

Text at the moments customers wonder where the technician is, and route replies to the job. More in the SMS API guide for SaaS platforms and sub-account design.

Accounts opened before November 12, 2026 keep their signup prices, shown under Billing.