NiceJob problems and complaints: what's actually going on

NiceJob's review scores sit well above most software in its category, which makes the complaints that do exist worth reading carefully rather than dismissing. A tool with mostly five-star reviews that still draws the same handful of specific criticisms repeatedly is telling you something real, even if it's a minority view.

This sorts those complaints by cause, says which ones are preventable setup mistakes versus genuine tradeoffs, and is honest about where I couldn't verify something. Review platforms are opinions, not confirmed facts, so I'm labelling them as such throughout.

What do NiceJob reviews say overall?

As of this check, NiceJob sits at roughly 4.8 out of 5 on G2 and roughly 4.9 out of 5 on Capterra, with review counts in the low hundreds on each platform. Exact counts vary slightly depending on which page of a given site you land on, which is normal for review aggregators and not worth treating as a precise figure. The consistent praise across both platforms: quick implementation, low ongoing maintenance once it's running, and specifically its integration with Jobber for one-click review requests.

The complaints that recur, in roughly descending order of how often they come up, are below.

What reviewers consistently praise	What reviewers consistently flag
Quick to implement, little ongoing maintenance	Templates and timing sequences feel fixed, more so on Starter
One-click Jobber integration for review requests	Customers sometimes get messaged twice if the job platform's own follow-up is left on
Responsive support, in most reviews	A minority report slow responses or bugs
Noticeable increase in review volume after setup	Price feels steep for a business only wanting basic review requests

Why do customers get asked for a review twice?

This is the most concrete, most preventable issue, and it isn't really a NiceJob problem. When you connect NiceJob to a job platform like Jobber or Housecall Pro, a job marked complete triggers NiceJob's own review sequence. If that job platform also has its own automatic review-ask or follow-up feature still switched on, the customer gets contacted by both systems separately.

Jobber's own help center is explicit about this: it recommends turning off Jobber's automatic job follow-ups once NiceJob is connected, specifically to avoid duplicate requests. Housecall Pro's integration documentation offers a related workaround, a "noreview" tag you can apply to a specific customer or job to exclude it from NiceJob's sequence entirely. Both point to the same root cause: this is a setup step that gets skipped, not a flaw in either product. Worth separating from this: NiceJob itself has a built-in safeguard against over-asking a repeat customer, a 6-month cooldown before the same customer can be enrolled in a new review request, plus a "Smart Auto-Exit" that stops a sequence the moment someone leaves a review. The duplicate-message complaint isn't NiceJob re-asking too soon on its own, it's two separate systems (NiceJob and the job platform's native follow-up) both firing for the same job.

What to do about it: turn off your job platform's own automatic review messaging the same day you connect NiceJob, not after the first complaint. See my NiceJob setup guide for exactly where that setting lives on the platforms NiceJob connects to natively.

Why do people say NiceJob feels rigid?

A recurring theme in reviews is limited customization: fixed-feeling email templates, automated workflows that are hard to adjust in fine detail, and timing sequences you can nudge but not fully rebuild. One characterization from a reviewer: wanting granular control over every template and timing sequence can make NiceJob feel too rigid for that specific need.

My honest read: this is a real tradeoff, not an oversight. NiceJob's whole pitch is that review requests run themselves without you managing a marketing tool. That same design choice is what makes it feel inflexible to someone who wants precise control over wording, timing or segmentation by customer type. If that control matters more to your business than the hands-off automation, it's worth comparing against NiceJob alternatives that trade some of the simplicity for more configuration, or having something built that does exactly what you want instead of adapting to what a platform allows.

Is NiceJob worth the price for a small business?

At $75 a month for Starter, reviewers who only want simple review requests sometimes describe the price as high for what amounts to automated text and email sequences, especially early on before the business has grown into needing it. That's a fair complaint on its own terms: the software is doing something straightforward, and the price isn't tied to job volume, so a business doing a handful of jobs a week pays the same as one doing fifty.

What I'd weigh against that: a basic version of this costs nothing. Google gives every business its own review link and QR code, and a short personal text with that link after each job is free. Software like NiceJob starts to earn its price once you have enough jobs, staff or locations that doing this by hand consistently stops happening, which is exactly the point my review management software guide makes more generally. If you're not there yet, the honest answer may be to wait.

What about customer service and bugs?

A minority of reviews mention slow customer service responses or occasional bugs, alongside the much larger volume of reviews praising NiceJob's support specifically. I can't verify how often these issues actually occur versus the glowing majority, since review platforms don't publish a breakdown by issue type, so I'd treat this as a pattern to ask about directly, by requesting a specific support-response-time commitment before you sign up, rather than a confirmed, frequent problem.

Is NiceJob down often?

I could not find a public NiceJob status page, which is a genuine information gap compared with a vendor like ServiceTitan that publishes one. Without that, there's no independent uptime record to check, only the occasional bug or outage mention inside a review, which I can't verify as a pattern from outside the product. If uptime matters for how you run your business, specifically because review requests are time-sensitive after a job, ask NiceJob directly about its uptime history before relying on it, rather than assuming either way.

Which of these actually matters for your business?

Not every complaint applies equally to every business size:

• A solo operator or a small crew is most likely to feel the price complaint, since $75 a month against a handful of jobs a week is a real cost, and least likely to hit the customization ceiling, since the default sequence is usually enough.
• A growing crew on Jobber or Housecall Pro is the profile most likely to hit the duplicate-message issue, specifically right after connecting the integration, and the one most likely to get clean value from the price once job volume justifies it.
• A multi-location or enterprise business is most likely to hit the customization and competitive-intelligence ceiling, since NiceJob's design favors a single straightforward sequence over the kind of granular, location-by-location control that Birdeye or GatherUp are built around.

Should you leave NiceJob, or just fix the setup?

Most of what gets called a "NiceJob problem" turns out to be one of two things: a setup step that was skipped, specifically the duplicate-messaging issue, or an honest mismatch between what you need and what the product is designed to do, specifically customization depth or price at low volume. Neither is a reason to assume the software is broken.

It's genuinely worth comparing alternatives if you need deep control over templates and segmentation, if you're running multiple locations and want enterprise features like Birdeye's competitor benchmarking, or if your job platform isn't one of NiceJob's native integrations at all and you'd be running everything by hand anyway. See NiceJob alternatives, NiceJob vs Podium and NiceJob vs Birdeye for how the realistic options actually compare.

How I'd approach this

If a client's complaint is the duplicate-message issue, that's a five-minute settings fix in the connected job platform, not a reason to switch anything. If it's genuinely about customization, I'd rather build the one specific piece they need, often a custom review-request trigger tied to their own job data with the exact wording and timing they want, than have them pay for a bigger, more expensive platform that still won't give full control. And if the real issue is that NiceJob doesn't connect to whatever system they actually run their jobs through, that's a case for building the missing integration rather than replacing software that otherwise works fine.