Every job asked, every technician credited

Yes. Reviewflowz checks ServiceTitan every fifteen minutes for jobs that reach Completed and texts the customer after the delay you set, pointing at the Google profile of the branch on the job's business unit; no review after three days and an email reminder follows. Scheduled, dispatched, on-hold and cancelled jobs never trigger, and jobs completed before you connect are imported for reporting and technician credit but never messaged. Two things to plan for: ServiceTitan's API needs the Works or Ent Plus package, and your ServiceTitan admin generates the client ID, secret and tenant ID you paste into Reviewflowz, so allow for that admin step rather than five minutes. See review requests and the ServiceTitan integration.

The field service apps in the tools list below trigger the same way: the job closes in Jobber or is marked finished in Housecall Pro, the customer is asked, and the request points at that branch's Google profile. Jobber connects when an admin on your Jobber account clicks Connect and allows access; Housecall Pro sends job events by webhook, which Housecall Pro switches on only for its MAX plan. Workiz, FieldEdge, PestPac and GorillaDesk are in the catalog too; pick yours in the tools list on this page. See the Jobber integration and the Housecall Pro integration.

Google first: one profile per branch is where the phone rings, and where every job-complete request points. Yelp, Facebook and BBB are read, not asked: connect each branch's pages and their reviews land in the same feed as its Google reviews, labelled with the branch and tagged on arrival, so Salem's BBB 4-star about a slipped window sits beside Portland's Google 5-star about a technician who was in and out in twenty minutes. Angi is not on the standard list yet; if your branches get reviewed there, tell us and we connect a niche site within two weeks. The asks themselves go to Google. See review monitoring.

Four and five-star Google reviews get a reply within the hour from an agent trained on the replies you already wrote, backtested on your past reviews before it goes live, thanking the technician the customer named. Three stars or below never gets an automatic reply: it goes to that branch's manager in Slack or your helpdesk with a draft attached, so "Booked the 8 to 12 window. Nobody came, nobody called" gets a call that afternoon and an answer that says so, not a canned thank-you. Replies post on Google. See the autoresponder.

Yes. Reviewflowz keeps every review it has seen, so when Google removes one it stays in your feed flagged as no longer on the platform, with its text, rating, date and branch. Edits are kept the same way: when a Salem customer's 2-star "still seeing ants" becomes a 5-star after the callback, both versions and the flip are on the record. Reviewflowz cannot tell you why Google took a review down or bring it back, but a company that tags its door-to-door complaints can count how many of them Google removed. See review monitoring.

Yes, when the request came from a job: the credit goes to the technician assigned on the job record, not to the sender or to a name in the review. Two technicians on one install both get a credit, a reassigned job follows the reassignment, and a doubtful match waits in a queue for you. Without job data, Reviewflowz reads the names customers do write, nicknames, typos and two names in one review, against your team list, and a history import credits past reviews too. Technicians can watch their own count in the attribution app with nothing but a phone number, no company email or password. See review attribution.

Pricing is per location: four branches are four locations, whatever the number of technicians, jobs or reviews at each. Every branch starts free for 14 days, with no credit card and no demo call, and your field service app can connect inside the trial so you see the first job-complete requests go out before you pay. The numbers are on the pricing page.