Feedback score → low: instant alert; high: a review request in 7 days
A one-question Tally form (0–10) after every project. A 6 or lower pings you on Telegram with the comment while there is still time to fix it; a 9 or 10 is marked for a review request a week later.
The problem
Unhappy clients rarely complain; they leave. Happy clients rarely review; they forget. One question at the end of a project catches both, if someone acts on the answer the same day.
What happens when it runs
- A Tally form (name, email, score 0–10, comment) sends the answer to the Make webhook
- A row in the feedback sheet; a 9–10 gets "review request due <date + 7 days>" in the follow-up column
- A Telegram message: a low score arrives with the comment in bold, a high one as a quiet note
The tools inside
- Tally — the form that fires the webhook (free; any form tool works) · Create a free form →affiliate link
- Make — the automation engine · Sign up (one month of Core free) →affiliate link
- Google Sheets — log and lists
- Telegram — alerts
Before you start
Three things to have ready before importing, or Make will ask and you will have to leave halfway:
- The webhook address (paste it in Tally)
- The feedback spreadsheet id
- The score thresholds (default: 6 and below alerts, 9 and above earns a review request)
- Chat ID
Sheet templates
The file maps columns by position. Start from exactly these headers, in this order — a column in the wrong place writes a phone number into the email column.
- Feedback sheet ·
timestamp | client | email | score | comment | followupDownload ↓
How to import (2 minutes)
- In Make: Scenarios → Create a new scenario
- At the bottom, the three dots (⋯) → Import Blueprint → choose the file you downloaded
- Click every module with an exclamation mark: choose your connection (Google, Telegram) — Make creates one in a click if you have none
- Replace every value in double curly braces ({{…}}) with your own from the list above
- Run once with a test row in the sheet. Only when it passes — Schedule and ON
Read more
What does not work in it
- This marks the review request; it does not send it. Pair it with the review-request automation, which reads the sheet daily and emails on the due date — or send it by hand from the sheet.
- A 7 or 8 gets neither an alert nor a request, on purpose: those clients are fine and not enthusiastic. Chasing them for a review produces lukewarm reviews.
Affiliate link. If you sign up through it we earn a commission from Make; your price is the same, and the link gives you one month of Core free.
More automations
All automations →
AUTO WELCOMENew client → welcome email → onboarding checklist → alert
The moment a client signs, three things happen on their own: they get an email that says what comes next, an onboarding checklist opens, and the team is alerted.
QUOTE FOLLOW-UPQuote unanswered for 3 days → one follow-up, automatic
Every quote sent and unanswered within three days gets one short follow-up email, and the consultant gets an alert. Nothing to remember, nobody to chase.
REVIEW ASKProject closed → 7 days → a Google review request
A week after a project is marked "done", the client gets a personal email with a direct link to write a review. Once, at the right moment.