Dispatch board, estimates, invoices, tech tracking — Housecall Pro runs the back office for thousands of home-service firms across the UK, US, Canada, and Australia. Then the working day starts, and 85%+ of customers arrive somewhere Housecall Pro isn't: WhatsApp, while techs are mid-job or mid-drive. Two-to-four-hour reply gaps hand those jobs to whoever answered first. Link Housecall Pro to WhatsApp through Susan and the gap closes: sub-three-second greeting, photos and details captured, live availability checked, prices quoted, deposits banked, job cards raised — automatically, around the clock.
⚡ Key Takeaways
- Every enquiry greeted instantly with triage attached — photos requested, details captured, estimates started. Bookings become scheduled jobs with customer profiles and tech dispatch attached, no retyping. Callout and diagnostic fees clear before vans roll. No middleware maze — one native OAuth instead of Zapier/Make/Twilio contraptions. And customers stay informed (arrival texts) and come back (review asks, tune-up nudges) without anyone remembering to do it.
SMS-and-email operations leak four ways. The five-minute emergency rule: most field jobs go to first contact, and manual replies lose them. Site reality: ladders, live wiring, moving vans — answering there is unsafe as well as slow. SMS itself: carrier spam filters, no buttons, photos compressed to mush. And ghost bookings: cross-town drives with no postcode check and no deposit, cancelled on arrival, fuel and mornings gone.
Five minutes, no code, no webhook plumbing:
Phone tag versus middleware versus chat-run: replies took two to four hours between jobs, or five to fifteen minutes via static alerts — now seconds, always. Photos went by email chase and SMS mush, or clunky external forms — now requested and attached automatically. Job creation was double data entry, or webhook text-dumps — now full two-way sync. Deposits were phone-read cards, or browser redirects — now one tap in chat. Setup was daily labour, or pricey fragile stacks — now two-minute native OAuth. Nights meant voicemail, or static auto-replies — now fully autonomous booking. Drop-off ran 40–55% or 30–45% — now under 4% in conversation.
In the working day it looks like this. Breakdown message arrives — serial-plate photos requested, triage done, right tools loaded first time. Diaries read live — genuine slots offered, patch respected, no over-promising the far edge. Money first — PCI-clean Stripe links, Apple Pay to card, booking locked on verified payment. Tech rolling — customer gets photo, name, ETA, and confirms access with one tap. Job done and paid — thank-you plus review ask on WhatsApp, seasonal tune-up scheduled months out. Repeat business that used to need remembering.
Related: Jobber, ServiceM8, Tradify, quoting automation, Stripe links — plumbers, garages, cleaners, repair shops.
Frequently Asked Questions (FAQ)
Any code or developers?
None. Native OAuth wizard, two minutes. Zapier, Make, Twilio, webhooks — none required.
Customers and dispatches — created properly?
Records created or updated, photos attached, slots scheduled, techs assigned. The dispatcher’s job, done by software.
No-shows — handled?
98%-opened reminders at 24 and 2 hours, confirm-or-move in one tap. Ghosts filtered by deposits first.
Deposits before the job exists?
Mandatory callout and diagnostic fees over Stripe, in chat, before the slot locks. Unpaid travel stops here.