A completed job should trigger the next customer action.

• →Review requests happen inconsistently, dependent on someone remembering.
• →Requests go out too late, after the customer’s satisfaction has faded.
• →Referral asks never happen at all, because there’s no defined moment for it.
• →Responses (a left review, a referral) don’t get logged anywhere.

• →Sending the review request at a consistent point after payment and completion.
• →Sending a separate referral prompt once trust is established.
• →Logging review and referral outcomes back into the CRM.

• →Any personal thank-you note the business wants to add.
• →Handling a negative response before it becomes a public review.

A flagged negative experience (complaint, dispute, callback) pauses the review request and routes to a person first. Review requests follow each platform’s solicitation policies.

Job completion and payment status in the field-service platform trigger the sequence; outcomes write back to the CRM.

Trigger a review request a fixed window after payment and completion, gated by a satisfaction/complaint check, followed by a separate referral prompt, with outcomes logged automatically.

Estimate using: completed jobs per month x current review/referral request rate x the value of a new lead from referral relative to your paid acquisition cost.