Your Booking Automation Questions — Answered Straight

Most contractors assume their customers won't self-book — that they're old-school, prefer the phone, or won't trust a link. Here's what actually happens: when a customer gets a follow-up text within 30 seconds of hitting your voicemail, they click the booking link. Not because they wanted to self-book — because they want their problem fixed and you just handed them the fastest path to a confirmed appointment.

SMS messages are opened at a dramatically higher rate than email — most within the first few minutes of receipt. When your booking confirmation lands by text with a one-tap link, most customers use it. They don't care about the channel; they care about getting the job on the calendar.

Some customers will still call back. That's fine. When they do, the AI receptionist answers, qualifies the lead, and books the appointment directly to your calendar. Either path — self-booking via SMS link or a call to the AI — drops a confirmed appointment into your calendar without you touching the phone. You don't have to pick between phone-first customers and self-booking customers. The system handles both, and you see one clean calendar.

The rescheduling process runs without you. The customer gets a reminder text 24 hours before the job — and that text includes a rescheduling link. If they need to move the appointment, they click it, see only the open slots on your calendar, pick a time, and receive a new confirmation text automatically. Your calendar updates in real time. No missed call from a customer asking to move Tuesday's appointment. No sticky note on your dash. No mental bandwidth spent shuffling the schedule.

The key detail: the customer only sees slots that are genuinely open. They can't double-book you. They can't pick a slot you've already blocked. The system enforces your availability rules — you set them once during the 48-hour setup, and they hold.

If a customer ignores the rescheduling link and still doesn't show up, the two-reminder sequence — 24 hours out, then 2 hours out — catches most of that before you've already driven to the job site. Two chances for the customer to say 'I need to move this' before you lose the slot to an empty driveway.

Yes — and this matters, so it's worth saying clearly. Automated booking doesn't replace your phone. It handles the calls that would have gone to voicemail and been lost forever.

When you or a dispatcher takes a booking over the phone, that appointment goes into the same calendar the system watches. The reminder sequence fires automatically the moment the appointment is entered — the customer gets the same confirmation text, the same 24-hour reminder, the same 2-hour reminder, and the same rescheduling link regardless of how the booking happened.

Phone-first customers keep reaching you by phone. The AI handles overflow — the calls you missed during a job, the 7 PM emergencies, the Saturday requests you couldn't get to. Phone bookings and AI-booked appointments live side by side in the same calendar. Same reminders. Same rescheduling links. One system, no juggling.

TCPA — the Telephone Consumer Protection Act — restricts automated texts to consumers and carries fines of $500 per violation, up to $1,500 for willful violations. That's a real exposure, and you should know exactly how the system handles it before you go live.

Consent. When a customer books an appointment — online or over the phone — the booking form includes a clear disclosure that they'll receive SMS reminders related to their appointment. Completing the booking constitutes express consent. No consent record on file, no texts sent.

Opt-outs. Every text includes a STOP instruction. When a customer texts STOP, they're removed from all future messaging automatically and immediately. The system logs the opt-out. You don't manage a suppression list manually.

Quiet hours. The system enforces time-of-day guidelines — no texts sent before 8 AM or after 9 PM in the customer's local time zone.

These are the structural guardrails built into the configuration we operate on your behalf. This page is not legal advice, and neither is the system's configuration. TCPA compliance depends on your specific business practices, how consent is captured at the point of sale, and how your state interprets applicable rules. Before you launch SMS messaging at volume, consult a qualified communications attorney.

The system syncs with Google Calendar and major calendar platforms — the appointment lands in whatever calendar you're already using, complete with the customer's name, phone number, service address, job type, and any notes collected during booking. You don't download a new app. You don't log into a dashboard.

Changes sync both directions. Block time in your calendar because you're pulling permits downtown, and that block shows as unavailable to the booking system immediately. A new job booked through the AI appears in your calendar within seconds.

Calendar compatibility is confirmed before we take your payment — it's part of the onboarding conversation on day one of the 48-hour setup. If your current calendar isn't supported, we tell you upfront and work out a solution before go-live. You won't discover a sync problem three weeks in.

The guarantee is explicit: if the system doesn't recover at least $5,000 in booked revenue within 60 days of going live, you don't pay the monthly fee until it does — or you get your money back. Here's what 'recovered revenue' means specifically for booking automation:

Rebooking recovered revenue. When a no-show customer receives a follow-up text and rebooks, that job counts toward the threshold. When the reminder sequence catches a cancellation and fills the open slot with another customer, that job counts.

No-show reduction math. If your no-show rate drops from 20% to 5% and you run 40 appointments a month, that's 6 recovered jobs per month. At an average ticket of $500–$800, you clear the $5,000 threshold before the 60-day window closes — often inside 30 days.

We track the numbers from day one. You see every recovered job in your calendar. The math is transparent: appointments generated by reminder sequences, rescheduling flows, or AI-answered calls equal recoverable revenue. No fine print buried in paragraph twelve. If we don't hit $5,000 recovered in 60 days, we work without the monthly fee until we do.

Expect a measurable change in weeks 2–3. The reason it takes that long: the reminder sequence needs to run through enough bookings to produce a meaningful sample. If you're running 10–15 jobs a week, you'll have 20–30 completed reminder cycles by the end of week 2 — enough to see whether the no-show rate is moving.

Week 1 is baseline. You're watching confirmations go out, links get clicked, and rescheduling requests come in without you touching the phone. Weeks 2–3, the pattern shows in the numbers.

Higher job volume speeds this up. If you're running 30 or more jobs a week, you'll likely see a clear trend inside 10 days. Emergency-call volume, how accurately customers entered their cell numbers at booking, and how consistently confirmations are going out all affect the ramp. We're not promising overnight magic — we're promising a measurable, trackable result within 60 days, backed by the guarantee.

Multi-tech scheduling is supported, with one honest note upfront: each technician needs their own calendar connected to the system, and by default the booking flow routes jobs based on availability across the team rather than skills-based assignment.

In practice: a customer books a drain cleaning call. The system checks which techs have an open slot, picks the first available, and drops the appointment on their calendar. The customer gets a confirmation that includes the tech's name. You see the full team's schedule in your existing calendar — one view, all technicians, no separate software required.

What the system doesn't do out of the box: route by zip code proximity, enforce skill-certification rules, or manage complex territory splits. Those routing rules can be configured during setup — but they require a detailed conversation on the onboarding call so we build the logic correctly before go-live.

If you have a crew of four or fewer with a consistent service menu, multi-tech setup works cleanly. If your operation is larger or has complex routing needs, flag it on the first call. We scope the configuration correctly from the start rather than discover the constraint on day 15.