Spec: Question 01 When does the customer receive a review request?
We define the completion signal and delay with your team. The request should start from the system that knows the work is actually finished, not from a rough sales date. Before it sends, the workflow checks whether the job was reopened, a service issue is active, or someone is already handling the customer.
Spec: Question 02 What happens if the customer has an open service issue?
The issue reaches the right person and the routine request pauses while the job isn't in a valid completed state. That doesn't erase the customer or hide their feedback. It keeps an automated public ask from colliding with work your team is still resolving.
Spec: Question 03 Do you only ask happy customers for reviews?
No. Once a job is complete and the customer passes the same checks, the public review request isn't based on a guess about whether they'll leave a positive rating. The request invites honest feedback without requiring a particular score.
Spec: Question 04 Why are reviews and referrals separate workflows?
A review asks someone to share an honest experience publicly. A referral asks them to introduce another person to the business. Those are different levels of trust and different moments. Keeping them separate protects the relationship and lets your team decide when a personal referral ask makes sense.
Spec: Question 05 Does the system ask for every referral automatically?
No. It handles the routine timing, identifies the opportunity, and creates a task with the project and relationship context attached. If the reminder goes unanswered, a Lead Care agent can call and make the ask. For high-value referrals, the better experience is often for the owner, salesperson, or project manager who knows the customer to make the ask personally, and we set that threshold with your team.
Spec: Question 06 Who calls the customer, and what do they say?
A US-based Lead Care agent who can see the project, the completion status, the service history, and whether the customer has already been asked. The call is short: how did the job go, would you be willing to share that publicly, is there anyone else who should know about the work. If the customer raises a service concern, the ask stops and the concern goes to your team the same day.
Spec: Question 07 Can we keep our current CRM and review platform?
Usually, yes. Lead Intelligence connects the useful history already spread across your website, CRM, project system, review platform, and approved outside data added to the customer record. We identify which system confirms the work is finished, where reviews should go, whether a service issue is open, and whether the customer has already been asked. You don't have to replace a working tool just to connect the process.