Lūgt apmierinātos klientus atstāt atsauksmes

Kad izmantot

A job, project or delivery for a customer has just been completed and closed. Not for a customer with an open complaint or unpaid invoice — resolve that first via ops.customer-complaint or money.chase-overdue-invoice. Not for setting up the place reviews land — that is growth.google-business-profile. Not for responding to a single review as a standalone task — that happens here in S7, or via ops.customer-complaint if it is a serious complaint in review form.

Pirms sāc

• The review destination exists and the direct link works (open it once before any ask).
• The invoice for the job is paid, or the engagement closed cleanly.
• The owner has approved the standing wording at least once; per-run approval is still required in S3.

Ko izpilde pieprasa3

Ceļš9 soļi

1. S1

   Pick the candidatesaģents

   From completed jobs in the last 7 days, list customers whose invoice is paid and who have no open complaint or refund in progress.

   Izdarīts, kad a candidate list exists with payment status and a yes/no on each.

2. S2

   Draft the askaģents

   One short message: thank them, one sentence on what was delivered, the direct link, one line that a review helps a small company. Personal, from a person's name, not "the team".

   Izdarīts, kad a draft exists per candidate, each with the correct link.

   ⛔ No incentives ("leave a review, get 10% off") and no gating (only asking customers you pre-screened as happy) — both breach Google's review policies and can mislead under EU consumer rules.

3. S3

   Approve wording and recipientsīpašnieksvajag apstiprinājumu · īpašnieks

   Apstiprinājums · S3 · īpašnieks — izpilde apstājas, līdz nosaukts cilvēks ieraksta lēmumu

   Show the drafts and the candidate list.

   Izdarīts, kad the owner has approved or corrected the wording and named the recipients to send to.

4. S4

   Sendaģentsvajag apstiprinājumu · īpašnieks

   Apstiprinājums · S4 · īpašnieks — izpilde apstājas, līdz nosaukts cilvēks ieraksta lēmumu

   Send via the mail module from the agreed sender, one message per customer.

   Izdarīts, kad each message shows as sent in the mail module, logged against the customer record.

5. S5

   Wait, then remind onceaģents

   After 7 days, check which reviews have appeared. Send at most one short reminder to those who have not reviewed.

   Izdarīts, kad every candidate is marked: reviewed · reminded · left alone.

6. S6

   Log new reviewsaģents

   Check the review destination (and any other platform the company uses). For each new review, record in the growth module: rating, text, reviewer name, link, date.

   Izdarīts, kad every new review has a row with a working link.

   ⛔ Google sometimes withholds new reviews for days — a missing review is not a refusal; do not re-ask.

7. S7

   Approve public responsesīpašnieksvajag apstiprinājumu · īpašnieks

   Apstiprinājums · S7 · īpašnieks — izpilde apstājas, līdz nosaukts cilvēks ieraksta lēmumu

   Draft a response per new review: thank a positive one by naming the job; for 1–2 stars, acknowledge, offer to fix, and route the substance to ops.customer-complaint.

   Izdarīts, kad the owner has approved each reply.

   ⛔ Never argue in a public reply or mention contract details — the reply is public and permanent.

8. S8

   Post responses and recordaģents

   Post the approved replies on the platform; record response date and link.

   Izdarīts, kad every new review shows a company response on the platform.

9. S9

   Feed the numbers forwardaģents

   Update ask count, review count, response rate and average rating; link the run to growth.monthly-growth-review so the next monthly review sees it.

   Izdarīts, kad the month's numbers are current in the growth module.

Pārbaudes — kā zinām, ka izdevās

• Every ask in S4 was sent only to a customer with a paid invoice and no open complaint (read back the S1 list).
• Every sent ask contains the correct direct link — open it from the sent message, not from the draft.
• Every review found in S6 has a logged row and a posted response.
• No ask message contains an incentive, discount or conditional offer (search the sent text for "discount",

Ja noiet greizi

Ko atstāj katrs solis

1. S1a candidate list exists with payment status and a yes/no on each.
2. S2a draft exists per candidate, each with the correct link.
3. S3the owner has approved or corrected the wording and named the recipients to send to.
4. S4each message shows as sent in the mail module, logged against the customer record.
5. S5every candidate is marked: reviewed · reminded · left alone.
6. S6every new review has a row with a working link.
7. S7the owner has approved each reply.
8. S8every new review shows a company response on the platform.
9. S9the month's numbers are current in the growth module.

Ko saglabāt

Candidate list from S1 · the owner's approval in S3 (who, when) · sent message ids from the mail module · each review's link, rating and date · posted response links · the month's counts in the growth module.

Kā šī procedūra uzlabojas

After every 20 asks ask: what share produced a review, and how many days did it take? Did any ask go to a customer with an open complaint or unpaid invoice? Did any response need rewording after posting? A new version changes the step that caused the miss, and says so in its change note.