Skip to content

Illustrative workflow

Requesting a Review After Job Completion

After a verified completion, the system sends a neutral review request to the eligible customer. The request is consistent and not gated by sentiment. A limited reminder sends if no response. Replies route to the team.

Starting event

A roofing job is marked complete and verified in the system.

How the workflow moves

  1. 1
    System

    Confirms the job is complete and verified.

  2. 2
    System

    Checks eligibility: valid contact, not opted out, within the request window.

  3. 3
    System

    Sends a neutral review request with a direct link.

  4. 4
    System

    Sends one limited reminder after a configured wait if no response.

  5. 5
    Team

    Handles any reply that needs a personal response or support.

Exception branch

If the customer needs support instead of leaving a review, a separate service-recovery route handles the issue. Negative feedback is never gated or hidden from public reviews.

Sample output

Review request: 'Thanks for choosing [Company] for your roof. If the work met your expectations, a review helps other homeowners find us. [Link to review profile]'

Illustrative sample. No real customer data or achieved metric.

Measurement definitions

Eligible completed jobs

Verified completed jobs that met the eligibility rules.

Requests sent

Eligible jobs that received a review request.

Delivery

Requests that were successfully delivered.

Reviews received

Genuine reviews verified from the eligible cohort, when that data can be confirmed.

Questions about this workflow

  • No. The request goes to every eligible customer after a verified completion. Feedback is not filtered by sentiment.

Apply this to your business

A strategy session identifies whether this workflow fits your operation and what to build first.

30 minutes. For roofing owners and operating leaders.