Turn every completed roofing job into a review request

Every evening we find the jobs you just finished, email each customer a personal review request, and log it on the job so nothing slips.

Agentic Task
JobNimbusGmailMarketingCustomer SupportEmail AutomationContent Generation
PromptCreate

Every day at 5:00pm on a cron schedule I can adjust, find the jobs we finished today in JobNimbus and turn each one into a personal review request while the customer is still happy. Start with JobNimbus List Jobs, narrowed to recently updated records using the filter {"must":[{"range":{"date_updated":{"gte":"now-1d"}}}]} passed as a URL-encoded JSON value. From that set, keep only the jobs whose status_name matches the completed status I name. Completed status names come from each account's own workflow settings and vary per account, so ask me for mine rather than hardcoding a guess like 'Complete' or 'Job Closed'.

Before doing anything else with a job, run two skip checks. First, look for a review request that already went out: call JobNimbus List Activities filtered to that job with {"must":[{"term":{"related.id":"<job jnid>"}}]} and skip the job if any activity on the record already logs a review request, so nobody gets asked twice across runs. Second, pull the linked customer with JobNimbus List Contacts using the contact id on the job, and skip the job if that contact has no email address on file.

For every job that clears both checks, write a short personal review request. Read the job record for what we actually did (the job type, the work description, the address) and for the crew or sales rep who ran it, and reference those specifics by name in the message. It should read like someone in the office wrote it that afternoon, not a template with the customer name swapped in. Vary the subject line and the wording for every customer, keep it to a few sentences, thank them for the business, and include our Google review link, which I will provide.

Send each message with Gmail Send a Message, one email per completed job, addressed to the email on the customer's contact record.

After the email goes out, log it back onto the job with JobNimbus Create an Activity related to that job, noting that a review request was sent, to which email address, and on what date. This is what lets the office see the request went out, and it is also what the duplicate check reads on later runs, so always write the activity and use consistent wording so it can be found again.

When the job's dollar value is above a threshold I set, also create a follow-up with JobNimbus Create a Task assigned to the rep who ran the job, due three days out, asking them to follow up by phone. Tasks need a record_type_name matching one of my account's task types, so ask me which one to use. Jobs below the threshold get the email only.

Let me configure the run time, my completed status name or names, the Google review link, the dollar threshold, and the task type. One thing to be clear about: this workflow sends the request and records that it was sent. It cannot see whether the customer actually left a review, so never report on review counts or claim a review was received.

Additional information

What does this prompt do?
  • Checks each afternoon for the jobs that just moved into your completed status and matches every one to its customer.
  • Writes a short, personal note that mentions the actual work you did and the crew or rep who ran the job, then emails it with your Google review link.
  • Logs the request back on the job record and, for your bigger jobs, creates a task for the rep to follow up by phone three days later.
  • Skips customers with no email on file and jobs that already have a review request logged, so nobody gets asked twice.
What do I need to use this?
  • A JobNimbus account connected to General Input.
  • A Gmail account to send the review requests from.
  • Your Google review link (the short link that opens your review form).
  • The name of the status your jobs move into when work is finished, and the task type your office uses for follow-up calls.
How can I customize it?
  • Change the time of day requests go out, or the status that counts as finished.
  • Set the dollar amount above which a rep gets a phone follow-up task, or turn the task off entirely.
  • Paste in your own review link and adjust how formal the message sounds.

FAQs

How does it know a job is finished?
It reads the status on the job. You tell it which status your office uses for completed work, since every JobNimbus account names its statuses differently, and only jobs sitting in that status get a request.
Will every customer get the same email?
No. Each note is written fresh from the job record and mentions the specific work and the crew or rep who did it, so the wording and the subject line vary from customer to customer.
Could a customer be asked for a review twice?
No. Before sending, it checks the job for a review request that has already been logged and skips it. That record lives on the job itself, so the check still holds on later runs.
What happens if a customer has no email address on file?
That job is skipped and nothing is sent. Add the email address in JobNimbus and the job gets picked up on a later run.
Can it tell me whether the customer actually left a review?
No. It sends the request and records that it went out, but it cannot see your Google reviews. Checking the reviews themselves stays a manual step.

Related templates

Chase past-due JobNimbus invoices with escalating emails

Every weekday, find every unpaid JobNimbus invoice, email each customer one reminder that gets firmer as it ages, and post a receivables summary to Slack.

JobNimbus
Gmail
Slack Bot
Agentic Task
Turn website roof inspection requests into JobNimbus leads

New roof inspection requests from your website form land in JobNimbus within a minute, with no duplicate records and nothing retyped by your team.

JobNimbus
Google Forms
Slack
Agentic Task
Chase overdue ERPNext invoices with escalating reminders

Every weekday morning, review your unpaid ERPNext invoices, email each customer a reminder that gets firmer as the debt ages, and brief finance in Slack.

ERPNext
Gmail
Slack
Agentic Task
Sync JobNimbus jobs, invoices and payments to Google Sheets

Every night, copy the last day of JobNimbus jobs, invoices and payments into one spreadsheet your bookkeeper and owner can pivot.

JobNimbus
Google Sheets
Deterministic Code
Weekday Blackboard reminders for work due in the next 48 hours

Every weekday morning each student gets one short, friendly email listing everything they still owe across all of their courses.

Blackboard
Gmail
Google Sheets
Agentic Task
Enroll new student intake form responses in Blackboard

Every intake form response becomes a Blackboard account, a course enrollment, a welcome email, and a logged row in your intake spreadsheet.

Blackboard
Google Forms
Gmail
+1
Deterministic Code

Stop losing reviews on jobs you nailed.

Every finished roof turns into a personal review request the same day, logged on the job so your office knows exactly who has been asked.