Do I Have to Replace My Current Review Tool?

Most home service companies evaluating a referral engine already have something collecting reviews: a reputation product, a feature bundled into their field service system, or a manager who texts a review link after every good job. The question that follows is practical: do I have to rip that out?

The short answer

Usually not. Most companies run both, with the referral engine complementing what they already have rather than replacing it. Some do consolidate, typically when their existing product is only being used for review requests and nothing else. Which path fits depends less on features than on what you are actually using today.

Key Takeaways

• Complement is the common outcome, particularly when the incumbent does more than review requests.
• Replace makes sense when the incumbent is review-only: you are paying for one function twice.
• The manual in-house method is the real incumbent for many companies, and it works, until it hits a ceiling.
• Overlap on review requests is worth resolving: two vendors texting the same customer is the failure mode to avoid.
• Decide by what you use, not by the feature grid: most companies use a fraction of what they pay for.

When complement is right

If your existing product is doing several jobs (webchat, a unified inbox, text-to-pay, appointment messaging), then reviews are one function among many, and removing it would strand the rest. Keep it.

In that arrangement the referral engine handles the referral relationship: the ongoing conversation with past customers, the follow-up, the partner program, the payouts and attribution. Your existing product keeps doing the operational messaging it was bought for.

The one thing to settle is overlap. If both are sending review requests to the same customer after the same job, you have created a small, entirely avoidable annoyance. Pick one owner for the review ask and turn the other off. That is a fifteen-minute configuration decision, and skipping it is the most common way a complement arrangement goes badly.

When replacing makes sense

The other case is straightforward: you bought a reputation product and the only thing you use it for is sending review requests.

That happens frequently. A company buys a broad product, uses one feature, and keeps paying the full price for years because switching feels like a project. If you are on a tier priced for capabilities you never turned on, consolidating is worth genuinely evaluating, not because two vendors cannot coexist, but because you are paying twice for one function.

The honest way to check is to open the last month of activity in your existing product and count which features actually produced anything. Most companies are surprised, and the surprise usually points at a smaller tier or a consolidation.

The in-house method nobody talks about

There is a third incumbent that never shows up in vendor comparisons, and for a lot of well-run companies it is the real one: the owner or a manager doing it by hand.

It looks like this. Every morning they open yesterday’s completed jobs, pick the ones that went well, and send a personal text: how did the move go? When the customer says it went great, they send a second message with a review link. It works. Response rates are high, because the message is genuinely personal and comes from a name the customer recognizes.

That method should be respected rather than replaced on principle. Its limits are volume and continuity, not quality. It scales exactly as far as one person’s morning, it stops entirely during busy season, and it captures the review while leaving the referral conversation unstarted. The customer who just said “your guys were amazing” is at peak willingness to send you someone, and the manual method almost never asks.

So the useful framing for a company doing it by hand is not “replace this.” It is: keep the personal touch where it matters most, and add the sustained follow-up that a person cannot maintain across a thousand past customers.

How to decide

Three questions, in order.

What is your existing product actually doing? Not what it can do, but what produced something last month. If the answer is only review requests, consolidation is on the table. If it is running your customer messaging, keep it.

What is not happening today? For most companies the honest answer is the referral side: nobody is following up with past customers, nobody is running a partner program, and referrals arrive untracked. That gap is the thing to buy for, and it is not what a reputation product is built to close.

Who would own the overlap? Whatever you decide, one system owns the review ask. Write it down.

The default assumption should be complement, because reviews and referrals are different jobs and most companies are already doing one of them adequately. What they are usually missing is the second one entirely.

For more, see why reviews and referrals do different jobs, judging review tools by outcome rather than tier, and contract questions to ask before you sign.