Demo file / RV-8831

Review routing, shown with fake job data.

Run the pipeline below. It starts with a closed job and shows the record changing as the system checks sentiment, sends the ask, captures the review, and stops for owner approval.

Input
Closed job
Output
Review draft
Demo data
RV-8831
Runnable demo

Press run. Watch the review record change.

The useful bit is the routing logic: public ask when sentiment is safe, private triage when it is not, and approval before anything gets published.

Without automation

The review ask depends on memory.

  1. Job closes, but nobody is sure when to ask for the review.
  2. Unhappy customers may get sent to a public review link.
  3. Good customers forget the experience before anyone follows up.
  4. Owner replies happen late or with generic copy.
With the pipeline

The job chooses the right reputation path.

  1. Completion event starts the workflow.
  2. Sentiment guardrail decides public ask or private triage.
  3. Review gets matched back to the original job.
  4. AI drafts the response, then waits for owner approval.
Scenario
Completed job to public proof
--time to ask
0rating captured
Waitingcurrent state
Review object RV-8831 

        

      


      

    

  






  

    

      
Real examples

      

        
Good experiences should become search assets.

        
Every completed job is a chance to increase trust. The system asks at the right time, routes bad experiences privately, and keeps staff from doing review chores by hand.

      

    

    

      
Example 01
Post-service review ask
When a job is marked complete, the customer gets a timed SMS/email review request with the right link.
  • Works from job status
  • Tracks sent and replied
  • Reduces staff chasing

      
Example 02
Private triage first
Low satisfaction routes to an owner alert or internal feedback path before the public review ask.
  • Catches frustration early
  • Protects the brand
  • Creates callback context

      
Example 03
Response draft queue
AI drafts review responses using service context and tone rules, then waits for owner approval.
  • No generic AI slop
  • Faster replies
  • Human stays in control

    

  






  

    

      
01
Completion trigger
Invoice paid, appointment complete, job card closed, or a manual send button can start the workflow.

      
02
Review routing
Happy customers get the public review link. Poor sentiment gets routed to the owner first.

      
03
Reporting
Monthly snapshots show review volume, response time, rating movement, and unresolved reputation issues.

    

  





Build reputation while the work is still fresh.
Reviews compound. The system makes sure the ask happens before the customer forgets why they liked you.
Find the review gaps →