⭐ We help you get set up. Start your 14-day free trial →
    Back to Resources
    Getting ReviewsNovember 12, 2026•By ReviewCatch Team

    14 Ways to Get More Google Reviews When You Only Complete a Few Jobs a Month

    14 Ways to Get More Google Reviews When You Only Complete a Few Jobs a Month

    Count the customers you have served, give each eligible customer a simple review invitation, and build the request into your project handover.

    You can start with a spreadsheet and a tested review link. Add a short message, one appropriate reminder, and a clear person responsible for the process.

    Use the 14 actions below to create that routine. They are designed for roofers, renovators, painters, flooring installers, landscapers, and other businesses that complete a smaller number of substantial projects.

    Work through the setup steps first, then use the weekly and monthly checks to keep requests from being forgotten.

    1. Count your completed customer relationships from the last 90 days

    Open your job records and list completed work from a defined period.

    Count unique customer relationships rather than invoices. Several payments or site visits on the same renovation should not automatically create several review invitations.

    Record:

    • Customer name.
    • Project or service.
    • Completion or handover date.
    • Contact details.
    • Whether a review invitation was already sent.
    • Whether the customer is known to have reviewed or declined.

    Use this list to understand the size of your genuine customer pool.

    For example, four different completed customers per month creates 12 customer relationships over three months. The number of published reviews will depend on what those customers choose to do.

    Take action: Write down your actual customer count before setting expectations. Use your own records instead of comparing your business with a contractor completing dozens of service calls every week.

    2. Build one clean invitation list

    Combine customer details from your job system, spreadsheet, and handover notes into one working list.

    Remove duplicate entries. Check opt-outs, previous refusals, known reviewers, and whether your contact permissions support the channel you plan to use.

    Choose eligibility using neutral criteria, such as completed projects within a defined period. Keep the invitation open regardless of the rating you expect.

    Google prohibits incentivized reviews, manipulation through multiple accounts, and selectively soliciting positive reviews. Its policies also address conflicts of interest involving employment or family relationships.

    Keep the list focused on genuine customer experiences.

    Do not add friends, employees, or other people simply to increase the count. Keep private feedback and customer support available alongside the public review invitation.

    Take action: Give each customer one current status: eligible, invited, replied, known reviewer, declined, or do not contact.

    3. Create and test your direct Google review link

    Open your Google Business Profile and find the review-link or QR-code sharing option.

    Google provides these tools so businesses can make review requests easier to complete. Customers need to be signed into a Google Account to publish a review; the account does not have to use Gmail.

    Test the link before sharing it:

    • Open it on your phone.
    • Confirm it leads to the correct business.
    • Check what a signed-out customer sees.
    • Send a test message to yourself.
    • Make sure the link remains clickable.

    Save the verified link where the office and field team can find it.

    If you create a QR card, test a printed sample too. Check the code at its actual printed size.

    Take action: Keep one approved link in your message templates. Replace any old links that send customers to the wrong place or require unnecessary searching.

    4. Choose one clear handover trigger

    Decide when your normal workflow should create a review invitation.

    Use a stage when the customer has enough experience to describe the service. Apply the same project criteria across customers.

    ServicePossible trigger to adapt
    Interior paintingFinal walkthrough of agreed work
    Flooring installationHandover and care instructions
    RoofingCompletion review and explanation of finished work
    LandscapingHandover with maintenance information
    RenovationAgreed project completion stage
    Appliance repairRepair checked and explained

    Write down who marks that stage complete and who sends the message.

    Keep support responsibilities separate. If the customer raises a concern, assign someone to handle it without making a particular review rating part of the resolution.

    Take action: Add “review invitation” to your handover checklist. Avoid creating a new invitation at every invoice or progress meeting on the same project.

    5. Save a ready-to-send text and email

    Prepare both templates so you can use the channel appropriate to the customer relationship.

    Keep the message focused on one action.

    Text template:

    Hi [First Name], thank you for choosing [Business] for your [Project]. If you'd like to share your experience, here's our Google review link: [Link]. Honest feedback is welcome. Thank you, [Name].

    Email template:

    Subject: Your experience with [Business]

    Hi [First Name],

    Thank you for choosing us for your [Project].

    If you'd like to share your experience in a Google review, you can do that here: [Link].

    If you need help with the completed work, contact us at [Details].

    Thanks again,

    [Name]
    [Business]

    Include sender identification and any required unsubscribe information for your channel.

    Check the customer name and project description before sending. Remove unrelated promotions, referral requests, and newsletter links.

    Take action: Save the approved versions where your team already works, rather than rewriting them after every job.

    6. Introduce the request in one short conversation

    At the normal handover, explain what the customer may receive.

    Use a brief script:

    Thanks again for choosing us. We'll send you a link if you'd like to share your experience in a Google review. It's completely optional, and your honest feedback is welcome.

    Then return to the handover.

    Let the customer decide whether and when to respond. Give them room to use their own device later.

    If they decline, thank them and record the preference. Make that note visible to whoever sends requests.

    If you use a handover card, include the business name, support contact, and tested review link or QR code. Keep the design readable and order a small test batch first.

    Take action: Add the script to your handover notes. Practise it once so the invitation sounds natural and stays brief.

    7. Invite appropriate past customers who were never asked

    Filter your working list for completed customers who did not receive an invitation.

    Check their records before contacting them. Confirm the project, approximate date, contact accuracy, previous preferences, and whether they already left feedback.

    Begin with a manageable group so someone can handle replies.

    Use a message that accurately describes the past relationship:

    Subject: Feedback on your [Project]

    Hi [First Name],

    We worked with you on [Project] in [Month or Year]. Thank you again for choosing [Business].

    If you'd like to share your experience in a Google review, here's the link: [Link].

    There's no obligation. We appreciate the opportunity to have worked with you.

    [Name]
    [Business and contact details]
    [Unsubscribe option where required]

    Avoid implying that old work was completed recently.

    Take action: Prepare the first small group, check each record, and set aside time to respond to any questions the messages generate.

    8. Add one limited reminder

    Choose a reminder interval that fits your service and customer relationship.

    For a straightforward completed job, one reminder around a week after the original invitation can be a starting point to test.

    Use a short message:

    Hi [First Name], a quick reminder that you're welcome to share your experience with [Business] here: [Link]. If you've already left a review, thank you. No need to do anything else.

    Before sending it, check whether the customer has replied, declined, opted out, or been identified as a reviewer.

    Do not send the same reminder by several channels. Set a clear endpoint instead of letting messages continue indefinitely.

    If a customer replies about the work, pause reminders while a person handles the conversation.

    Take action: Write the reminder limit into the workflow. Make sure the office and any automated system follow the same rule.

    9. Stop duplicate requests across projects and systems

    Check whether more than one system can contact the customer.

    An invoice platform, CRM, administrator, and technician may all have their own reminder process. Assign one place to control the invitation.

    Use a simple record:

    FieldWhat to save
    Customer referenceOne identifier across the project
    Invitation dateWhen the request was sent
    Reminder dateIf a reminder was sent
    Current statusAwaiting response, reviewed, declined, or stopped
    NotesCustomer preferences or support conversation

    For repeat customers, check existing feedback before sending another request. Where appropriate, they may choose to update an existing review about later experience.

    Keep progress payments and project milestones from triggering overlapping invitations.

    Take action: Inspect one customer journey from job completion to reminder. Remove duplicate messages and make sure status changes are visible to the people involved.

    10. Fix delivery problems before increasing reminders

    Review failed emails and undelivered texts.

    Check whether the contact record contains a typo, an outdated address, or a number that cannot receive your message.

    Use your existing customer records to correct genuine errors. Avoid adding alternative contact details simply to keep pursuing someone.

    Test the message formatting too:

    • Is the business clearly identified?
    • Does the project description make sense?
    • Does the link open correctly?
    • Is there one obvious action?
    • Does the opt-out work where required?

    If a customer reports difficulty, explain the basic steps and let them use their own account. Keep their password and private account information with them.

    Take action: Correct a delivery issue where you have reliable information. Add a note so the same error does not cause another failed request later.

    11. Give the team a 10-minute walkthrough

    Show the people involved exactly what to do.

    Cover the handover trigger, approved wording, review link, customer statuses, and the person responsible for replies.

    Practise these three situations:

    • A customer welcomes the link.
    • A customer declines.
    • A customer replies with a problem about the work.

    For each situation, explain what gets recorded and who takes the next step.

    Google's policies prohibit pressure, requests for specific review content, and asking staff to solicit a set number of reviews. Keep training focused on the service workflow and customer choice.

    Leave a short checklist where the team can find it.

    Take action: Ask one employee to explain the workflow back to you. Fix any unclear handoff before expanding the process.

    12. Read new feedback and assign one useful response

    Check new reviews and customer replies during a regular administration block.

    For each item, decide whether it needs:

    • A concise public acknowledgement.
    • A private support conversation.
    • An operational improvement.
    • No further action beyond recording it.

    Keep public replies relevant to the feedback. Avoid sharing private project details or turning a response into a promotion.

    When a problem needs attention, assign a person and date.

    For example, if a customer describes confusing arrival information, update the appointment message and confirm who sends it. If customers repeatedly appreciate careful cleanup, add the relevant checks to your normal completion process.

    Take action: Turn one useful piece of feedback into a named task. Check at the next team review whether the task was completed.

    13. Review the numbers once a month

    Use a short report to see where the process needs attention.

    MeasureCheck
    Unique completed customersHow many genuine relationships were available?
    Invitations sentWere any eligible customers missed?
    Failed deliveriesAre contact details causing problems?
    Known published reviewsWhat visible feedback arrived?
    Replies and opt-outsDoes the workflow need adjusting?
    Administration timeIs the process manageable?

    Keep uncertain matches marked as unknown. A delivered request does not prove it was read, and a link click does not prove a review was published.

    Combine several months before drawing conclusions from small numbers.

    If you completed four projects and received no reviews this month, inspect the records first. Check the trigger, invitation delivery, and time customers have had to respond.

    Take action: Choose one problem shown by the report and fix it before adding more messages.

    14. Put the routine on your calendar and automate the useful parts

    Use this first-month schedule:

    WhenAction
    Week 1Build the customer list, test the link, and save templates
    Week 2Start the handover workflow and appropriate past-customer invitations
    Week 3Check replies, delivery failures, reminders, and duplicate requests
    Week 4Review the records and improve one weak point

    Assign a weekly administration block and a monthly review date.

    If manual work is causing missed requests, examine automation. Test the completion trigger, message timing, duplicate handling, and stop conditions before relying on it.

    ReviewCatch supports personalized SMS and email review requests, follow-ups, and requests to past customers.

    Take action today: Count your recent customers, test your review link, and prepare your first appropriate invitation. Keep the routine running each time a project reaches handover.

    Ready to Automate Your Google Reviews?

    ReviewCatch automatically sends personalized review requests by text and email after completed jobs, handles polite follow-ups, and helps you win more 5-star reviews on autopilot.

    Ready to dominate your local market?

    Join local businesses using ReviewCatch to automate their 5-star reviews. Start your 14-day free trial today.

    Loved by local businesses
    Setup in 5 minutes•14-day free trial•Cancel anytime