One of twelve office jobs see them all
Grow the business · an office job you can pick
Ask for reviews after clean close-outs
Review requests drafted only for jobs that finished cleanly. Callbacks, complaints, repeat asks and anyone who opted out stay out.
Choose this office job and we build it around your process, systems, permissions and approval steps.
What it costs you now
The jobs that go well are the ones you never hear about again. The customer is happy, the crew has moved on, and by the time anyone thinks about asking for a review it is three weeks later and awkward. So the reviews you do get are mostly from the jobs that went sideways, and the ask never happens on the good ones because nobody wants to check whether there is still a callback open first.
What it does
The agent watches for jobs that reach the finished state you defined. For each one it checks the close-out, then looks for anything that should stop the ask: a callback, a complaint, a dispute, live warranty work, a review request already sent, or a customer who should not be contacted. Jobs that pass get a plain review request drafted. Jobs that do not are held, with the reason written next to them, so you can see at a glance why the duct repair in Richmond is not in the queue.
- You ask Draft review requests for the cleanly finished jobs, but leave anyone with a callback or complaint alone.
- It checks the close-out Each job is measured against your own clean-finish rule, not a guess about whether it went well.
- It holds the wrong ones back Callbacks, complaints, disputes, active warranty work, repeat asks and contact restrictions keep a customer out, reason shown.
- You approve the wording The drafts sit in review. Nothing is sent until you have read one.
You ask. It comes back with the reasons shown.
You ask in WhatsApp
Today
It hands back
REVIEW QUEUE · 12 DRAFTS
Review-request queue
- ✓Confirmed each job was completed under the agreed clean-close rule
- ✓Excluded callbacks, complaints, disputes and active warranty work
- ✓Excluded prior requests and customers who should not be contacted
Heat pump service · FitzroyClean close-outDraft ready
Switchboard upgrade · CarltonNo open issue · contact allowedDraft ready
Duct repair · RichmondOpen callbackHeld
A review queue that separates safe drafts from held jobs and explains every exclusion.
Illustrative example. Names, numbers and records are made up.
What changes for the business
Review requests that only ever go to customers whose job actually finished cleanly, and a visible reason for everyone held back.
- The ask stops being a job for a person
Nobody has to remember, and nobody has to check the callback list first.
- It protects the relationship
A customer with an open complaint never gets asked to rate you, which is the failure mode that makes owners stop asking altogether.
- You can see the holds
The held jobs are a short list of unfinished business, worth reading on its own.
What it is connected to
Built around whichever of these you run.
These are the systems this office job usually touches, not a required stack. We connect only what your version of it needs, using your own accounts and the smallest set of permissions that does the job.
- ServiceM8 or Simpro Job completion and close-out status, which is what decides whether a job qualifies.
- Open issue and callback records The callbacks, complaints and warranty jobs that hold a customer back.
- Your email Where the requests are drafted and sent from, in your own account.
- Your contact records Prior review requests, and anyone who should not be contacted.
- Your review link The request points the customer at wherever you collect reviews.
The boundaries come with the office job
When it acts, and when it only reports.
What starts it, what it may read, what it may write, who approves, and where it stops. Written down before the office job runs.
What it will not doIt does not chase, incentivise, or ask twice. It does not screen customers by how happy they seem, or route unhappy ones somewhere private, which would breach the review platforms' own rules. Anyone whose consent is unclear, who has already been asked, or who has an open complaint or callback stays out, and an opt-out is honoured immediately and permanently.
- Trigger
- A job reaches the agreed clean-close state or the office requests a review batch.
- Reads
-
- Job completion and close-out
- Open issues and customer replies
- Prior review requests and contact permissions
- Writes
-
- Review-request drafts
- Held-job list
- Request-status update
- Approval
- The office approves the eligibility rules and first batches before any automatic request is considered.
- Stops when
- A request is sent, the customer responds, the job becomes ineligible or the approved window expires.
- Exception path
- Any complaint, callback, dispute, unclear consent or conflicting status keeps the customer out of the batch.
- Audit evidence
- The queue records eligibility checks, exclusion reasons, message version, approval and send status.