Ask for the review at the moment the customer is happiest, which is usually within an hour of a job going well. The right customers get asked, the wrong moment is avoided, and the reviews and referrals that drive your next month of work arrive without anyone remembering to chase them.
A live Taskade Genesis app is embedded on this page. Walk a completed job through the request flow, look at how timing and targeting work, then use it and a running copy is yours in about ten seconds. The finished system is there to try before you commit.
That app is the Kanban Board, a live Taskade Genesis app you can click through and clone in about ten seconds. It is not a review and referral request flow out of the box, so treat it as the starting point: clone it, then carry its columns across and describe the rest of this build to Taskade Genesis.
The build is a real advocacy record. Each completed job is scored for whether asking is appropriate, using signals you define: the job went smoothly, there was no callback, payment cleared, and this is not a customer who just had a difficult experience. Requests are personalized with the technician name and the work done, because a request that mentions the actual visit converts far better than a generic form. Responses are tracked, referrals are attributed to the customer who made them, and anything negative routes to a private conversation with you rather than to a public page.
Read the program in whichever layout suits:
- List view for the request as the customer receives it
- Table view for the tracker with job, technician, request date, and outcome
- Board view for referrals moving through received, contacted, quoted, and won
- Calendar view to see request timing across the week
- Plus Mind Map, Gantt, and Org Chart across the 7 project views
Automations handle the timing, which is the entire game. With Taskade automations, a job completing cleanly triggers the request after the delay you choose, a non-response gets one gentle follow-up, a positive response opens a referral ask, and a negative response opens a service recovery task immediately. Across 100+ bidirectional integrations, review platforms and forms pull responses in while Gmail pushes requests out. See scheduled automations and automation actions.
The AI agents inside carry 34 built-in tools including persistent memory, web search, file analysis, custom slash commands, and multi-agent collaboration. The Advocacy agent writes each request from the actual job, and it knows which customers to leave alone, which protects the relationships that matter more than any single review.
Use the app, invite your office, and the requests, the responses, and the referral attribution are yours.
Browse live customer programs in the Community Gallery, start a build at Taskade Genesis, or read the brand voice guide. The request follows the customer-ready job summary, and referred customers enter through inbound inquiry intake.
Reviews compound in a way that most service businesses underestimate. A steady trickle from every good job produces a public record that is recent, specific, and mentions technicians by name, which reads very differently from a burst of reviews collected during one campaign two years ago. Consistency beats volume, and consistency is only achievable when the asking is automatic. The referral side compounds faster still, because a referred customer arrives pre-trusted, converts at a much higher rate, and tends to refer someone else in turn.
Frequently Asked Questions
When is the best moment to ask?
Shortly after a job that went well, usually within a few hours, while the relief of a solved problem is still fresh. Waiting a week reduces response rates substantially in field service.
How does it avoid asking the wrong customer?
By checking the signals first: an open complaint, a recent callback, an unpaid balance, or a difficult visit all suppress the request. Asking a frustrated customer for a public review is worse than not asking at all.
Does it handle negative responses?
Yes, and that path matters most. A negative response opens a service recovery task and routes to a person rather than to a public review page, which turns a bad experience into a saved relationship more often than you would expect.
Can the technician be named in the request?
Yes, and it helps. Customers remember the person, not the company, and technicians who are named in positive reviews tend to care more about the next job.
Are referrals tracked back to the source?
Yes. Each referred customer records who referred them, so you can thank the right person and see which customers genuinely send you work.
How many reminders should we send?
One. A single gentle follow-up captures most of the additional responses, and anything beyond that reads as pestering a customer who already paid you.
Can we ask for different things from different customers?
Yes. A commercial account might be asked for a case study or a reference call, while a residential customer is asked for a public review. The request type is a rule you set per segment.
How many reviews do we actually need?
Recency matters more than volume for local service work. A steady handful each month that mention specific technicians and specific jobs is worth more than a large number collected years ago, which is why an automatic ask beats a periodic push.
