Google Reviews | Apilon AI
Google Reviews

Ask every customer. Reply to all reviews.

After every completed job, the customer gets one neutral request for a Google review. The AI keeps an eye on your profile, tells you right away about a low rating and writes reply drafts in your tone for you to approve.

  • One request per purchase
  • Every customer asked the same way
  • No reply without your approval
The problem

Happy customers go home. Unhappy ones write.

Your Google profile rarely shows what an ordinary day actually looks like. Not because the work is bad, but because nobody has time to ask for the review and reply when it comes in.

  1. 01

    Happy customers forget

    They pay, say thanks and move on. Nobody asks them to write a few words, so it rarely happens.

  2. 02

    The ones who write on their own are often unhappy

    A disappointed customer has a reason to open Google. That's why your profile can paint a darker picture than your everyday work.

  3. 03

    Nobody gets around to asking or replying

    It isn't anyone's job. Customers don't get asked, and reviews sit unanswered for weeks.

Why it matters

Customers look first

Many people look up a local business on Google before they call or book. The reviews are one of the first things they see.

Recent reviews say the most

A review from last week says more about you today than one from three years ago. That takes a steady flow, not a once-a-year campaign.

Replies get read

A bad review with no reply looks worse than one you answered calmly and factually. The reply shows how you handle it when something goes wrong.

Four steps. Nobody has to remember anything.

The system connects to the place where you already mark a job as done. From there the rest runs on its own, and your team only gets involved when there's a reply to approve or a call to make.

  1. 01

    The job is completed on your endBooking · calendar · customer system

    When a job or a visit is marked as completed in the system you use today, the system picks it up. Nobody has to remember to send anything.

  2. 02

    The customer gets one neutral requestText or email · same wording for everyone

    A short message about that specific purchase: would you write a review of your visit? It goes to every customer who has given consent, no matter how the visit went. No reward, no asking for stars and an easy opt-out in every message.

  3. 03

    New reviews are monitoredGoogle profile · alert on low ratings

    The AI keeps an eye on your Google profile. If a low rating comes in, the person responsible is alerted right away, so you can reach out to the customer.

  4. 04

    Reply drafts for approvalApprove · edit · write your own

    Every review gets a reply draft in your tone. Someone on your team reads it through and approves it. Nothing gets posted without you.

What the AI does once the review is written.

Getting reviews is half of it. The other half is responding to them, including the critical ones. Here's what your team sees.

An alert right away on a low rating

If a review comes in with few stars, the person responsible gets a text or an email. Then you can call the customer and sort it out while it's fresh. The review stays exactly as the customer wrote it. You decide the threshold and who gets alerted.

Reply drafts for every review

Praise and criticism both get a reply in your tone. Someone on your team reads it, edits it if needed and approves it. You can also write the reply yourself. Nothing gets posted without you.

Monthly overview

Once a month you get the trend in your average and the topics customers mention most. Both what they praise and what keeps coming up in the criticism, so you know what to fix.

The screenshots are examples. Names and numbers are fictional.

Done right from the start

How we keep your reviews honest.

Some review tools first ask the customer whether they're happy and only send the happy ones on to Google. Everyone else lands in a private feedback form. It's called review gating. Google's review policies don't allow businesses to selectively ask for positive reviews or to discourage negative ones, and it gives new customers a skewed picture. We don't build it.

Instead, every customer is asked the same way, and every review gets a proper reply. That gives you a profile you can stand behind, even when someone looks closely.

What the system does

  • Asks every customer with a completed purchase, the same way
  • Uses neutral wording: “Would you write a review of your visit?”
  • Sends one request about that specific purchase. At most one reminder, and only if you want it
  • Has an easy opt-out in every message and honors it right away
  • Only messages customers who said yes when they bought or booked
  • Replies to every review, including the critical ones

What the system never does

  • Asks first whether the customer is happy and sends only the happy ones to Google
  • Asks for five stars or a “good” review
  • Offers discounts, gifts or prize drawings for a review
  • Nags again and again until the customer gives up
  • Messages people who haven't bought anything from you
  • Posts replies that no one on your team has approved

Data processing agreement first

We sign a data processing agreement with you before anything goes live.

Only the access you give

The system only sees the customer data and the Google profile you give it access to.

Everything is logged

Every request, opt-out and approved reply is logged, so you can always see what was sent to whom.

Questions we often get

If you can't find the answer here, bring it to the call. We'll go through your specific setup.

Book a call
Why not just ask the happy customers?

Because that's review gating. Google's policies don't allow selectively asking for positive reviews, and a profile that only shows the happy customers gives new customers a skewed picture. That's why everyone with a completed purchase gets the same request, no matter how the visit went.

What happens when a customer writes a bad review?

It stays on Google exactly as the customer wrote it. You're alerted right away, and the AI writes a calm, factual reply draft that you can edit and approve. You can also call the customer and sort it out. A proper reply shows new customers how you handle it when something goes wrong.

Do you send reminders?

By default, one request goes out and nothing more. If you want a reminder, we set up one at most, a few days later. Customers who have opted out never get another review message.

Can we give reviewers a discount or a prize entry?

No. Google doesn't allow payment, discounts or free goods or services in exchange for a review. The request is neutral and offers nothing in return, so the reviews can stand as they are.

Do customers have to agree to the message first?

We always recommend it. The easiest way is a checkbox in your booking or at checkout that the customer checks themselves. We help with the wording and connect it to the system, so only customers who have given consent and completed a purchase get a request.

Does the AI post replies on its own?

No. Every reply is a draft until someone on your team has approved it. You can edit the text, write your own reply or choose not to reply.

We're a clinic. Can we use it?

Yes, but the replies need extra care. A public reply must never reveal that the person is your patient, or anything about their treatment. We build that in as a fixed rule for the reply drafts, and you still approve every reply.

Which systems does it work with?

We connect to the place where you mark a job or a visit as completed today, for example your booking, calendar, point-of-sale or customer system. We figure that out together on the first call.

What does it cost?

It depends on your setup and how many systems need to be connected. We agree on the price after the first call, once we know what you need.

Let's look at your reviews together.

On a short call we look at your Google profile, where jobs get marked as completed today and how a neutral request fits into your business. You get a concrete proposal afterwards.

On the call

Your Google profile as it looks today01
Where the request should be sent from02
Consent and opt-out in your flow03
Tone, replies and who approves them04