Skip to content

Project

Review requests that stop the moment somebody replies

Asks a client for a review a fortnight after go live, chases twice, and stops the instant they reply or leave one.

At a glance

Built for
ZhorxOur own
Sector
Professional services
Nodes
15, 3 branches
Live since
2026-07
Systems
Airtable · Gmail · Slack

What changed

The job before

Asking for a review is the whole job, and it is the thing that never gets done. It happens at the end of a project, which is when everyone has moved on to the next one. Most clients will say yes and then never get round to it, so one ask is not enough, and a second ask sent to somebody who already replied is worse than no ask at all.

What runs now

A schedule reads projects that went live a fortnight ago, checks nobody has already been asked, and sends the request. Two follow-ups go out at four and eleven days. Any reply, from any of the three, stops the sequence for that client and puts it in front of a person.

The workflow, from the export

Node names are made generic and parameters are stripped before publishing. The shape, the branches and the node types are exactly what runs.

truefalsetruefalsetruefalseSCHEDULEEvery morningAIRTABLEProjects live 14 daysIFAlready asked?SETWrite the askGMAILSend itAIRTABLEMark as askedWAITWait 4 daysIFAny reply?SLACKTask for a personGMAILSecond nudgeWAITWait 7 daysIFStill nothing?GMAILFinal askNO OPLeave itNO OPNothing to do
StartsDoesDecidesWaitsEndsDrawn from the workflow export, not redrawn by hand.
Every step in order15
  1. Every morningSchedule
  2. Projects live 14 daysAirtable
  3. Already asked?If
  4. Write the askSet
  5. Send itGmail
  6. Mark as askedAirtable
  7. Wait 4 daysWait
  8. Any reply?If
  9. Task for a personSlack
  10. Second nudgeGmail
  11. Wait 7 daysWait
  12. Still nothing?If
  13. Final askGmail
  14. Leave itNo Op
  15. Nothing to doNo Op

What to look at

  1. The check before sending is the important node. Without it a client who replied to the first message gets chased twice more, which is the failure everybody has been on the receiving end of.
  2. The branch that finds a reply does not try to read it. Working out whether a reply is a yes is exactly the kind of judgement that belongs to a person, so it becomes a task instead.
  3. There is no third follow-up. Two is the point at which asking again stops being a reminder.

Want the full specification for a workflow like this, including the failure modes? The blueprints set them out step by step, free to download and build from yourself.

Free automation audit

Don't know what to automate?

That is exactly what the audit is for. You know your business. We know what can be automated.

Get my free automation audit

Replies within one working day. No commitment, and a person reads it.

What we look for

Including the things that should stay exactly as they are.

  • Work that repeats
  • Bottlenecks where things sit and wait
  • Leads that go cold in a gap
  • Admin nobody should be doing
  • Where AI genuinely helps
  • Where it genuinely does not
  • Tools that should be talking and are not
  • What to leave exactly as it is