RAWTech tool reference · Housecall Pro

When does Housecall Pro request a review after a job?

With Reviews activated, Housecall Pro defaults to email and text requests when a job is marked finished. It also supports requesting after the job is fully paid; check the selected setting before adding automation.

Start with native settings

Do not buy another tool for a step your current account already supports.

Trace the actual handoff

A setting, a customer record and a successful event are different evidence.

Verify before changing

Vendor documentation describes features, not your enabled configuration.

01Native capability

What the tool already does

  • Requests default to job finished, with an alternative Job is paid setting; multi-invoice jobs must be fully paid for the payment trigger.
  • Requests use email and SMS; a missing Mobile field means email only, and notifications-off customers are excluded by default.
  • Native Reviews connects Google and Facebook; default routing sends Gmail-address customers to Google and splits others between Facebook and website reviews, while Premium Reviews permits distribution changes.

02Handoff checks

Where the workflow can break

  • If a technician presses Finish before all work is done, a completion-triggered ask can arrive prematurely.
  • If payment is delayed or only partial, the paid trigger postpones the ask.
  • If notifications are disabled, contact fields are incomplete, or Google routing is not selected, an expected Google request may not occur; do not override notification preferences without authorization and consent review.
  • If NiceJob is connected alongside native Reviews, duplicate requests are possible.

03RAWTech judgment

Do not add a tool before naming the gap

Keep native Reviews if it covers the intended event and destination. Match finished versus fully paid to the actual customer handoff. Test where the request sends before buying another campaign tool.

04Proposed scope

What setup can include, confirmed during your audit

After authorized access, account verification and written approval. These are potential scoped tasks, not a claim that this setup has been installed or tested for your business.

  1. 01With HCP admin access, inspect Reviews activation, selected event, notification preferences, texting setup, and recent job activity.
  2. 02With authorized Google/Facebook access, verify connected profiles and inspect native destination distribution and Premium Reviews entitlement.
  3. 03After approval, test a finished job and a paid multi-invoice case with a designated test contact; disable only overlapping review asks, not operational notifications.

05Read before scope

Limits that change the decision

  • Feature entitlement, Premium Reviews cost, texting availability, and permissions require account confirmation.
  • Do not assume all requests go to Google, that non-Gmail users lack Google accounts, or that a missing SMS means an integration failure.

Plans, regions, permissions and vendor changes can affect availability. No customer account was inspected for this reference. RAWTech does not provide legal, payment-network or clinical compliance advice.

Related setup questions

06Evidence note

Vendor sources and verification limits

Sources checked on 2026-10-21. Vendor documentation supports the feature descriptions above. It does not establish enabled settings, successful delivery or business results.

Human editorial review is pending. This reference is not a signed-off installation specification.

07Next step

Review the current setup before installing anything

The $495 Loop Audit reviews records, settings and a test booking. Delivery is five business days after the required inputs are complete. Any installation follows a written scope.

See the Loop Audit
All tool decisions