Multi-location home services · the event reviews never see

Your dispatch software knows the exact second a job closes. Your review requests do not.

A technician closing a ticket is the best review-request trigger a business has — satisfaction is highest right then. Most reputation platforms never receive that event; they fire on a generic timer instead, because dispatch and reviews are two vendors with nothing wiring them together.

The desire, and the event two vendors both half-own

Nobody searching “dispatch software” wants a scheduling tool. They want more of the reviews the great jobs deserve and fewer that arrive a week late from a customer who has half-forgotten the job. That comes down to timing, and the system that owns the timing is not the one that sends the request.

1. 1. The event — the job closes. ServiceTitan, Housecall Pro and Jobber all fire a completion event with the technician, the location and the service performed. This is the well-known half; every dispatch platform has it.
2. 2. The gap — the request fires on its own clock. Podium and Birdeye send review requests on a schedule or a manual trigger they control, because the job-close event never reaches them. The request is not late by design; it is late because nobody told it the job was done.
3. 3. The close — one event, one trigger. Point the dispatch platform’s completion webhook at the reputation platform’s own request API. The ask goes out the moment satisfaction peaks, not on the reputation platform’s best guess at when that was.

This is the same shape as the gap between a missed call and a CRM’s lead routing — one system produces the event, a second system that could act on it never receives it, and the fix is a webhook, not a third tool.

Which platforms close the gap

• Field-service software, by scale — the platform that owns the job-closed timestamp.
• Reputation management platforms, by scale — the platform whose request needs that timestamp.
• Reputation management software: one signal, two AI jobs — what happens to the review once it arrives.

Some links on the recommendation pages are partner links: the vendor pays us if you sign up, your price does not change, and each button says which.

How to build it yourself, end to end

Five steps. Each names the vendor touchpoint from the picks above.

1. 1. Confirm the job-closed webhook fires with the fields you need. Technician name, location, service type — not just a job ID. The personalization in step 3 depends on this.
2. 2. Filter for the jobs worth asking about. A completed warranty callback is not the same request as a completed install — route only the job types your team already treats as a good review candidate.
3. 3. Call the reputation platform’s request API directly from the webhook. Skip the reputation platform’s own internal timer entirely; the job-closed event is the trigger, not a secondary signal feeding into one.
4. 4. Personalize the ask with the technician and the service. “How did Marcus do on your AC repair today” gets answered more often than a generic “how did we do.”
5. 5. Feed the response rate back to the dispatch record. Per-technician review-request response rate belongs beside the job record it came from, not in a separate reputation dashboard nobody on the dispatch side ever opens.

Step 2 is the one worth thinking through — asking after every job type, including the ones that closed rough, produces worse results than asking after the ones your team already knows went well.

Or have it built and run

The missed-call half of this stack — the same job-event thinking, applied to the call that almost got away instead of the job that finished — built and operated, paid only as a share of the revenue it recovers.