Turn every completed roofing job into a review request

By General Input

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.

Integrations

  • JobNimbus
  • Gmail

Type

Agentic Task

Categories

  • Marketing
  • Customer Support

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.

Related prompts

Explore more prompts
Win back LiveChat visitors whose chats went unansweredChase the paperwork every new client and vendor still owesFile Gmail attachments into storage with names you can findCandidate rediscovery desk for your archived Lever applicantsLaytime and demurrage claim workspace for chartering opsKajabi customer support console for member access fixesRun your application review round on Jotform submissionsRun your nutrition clients' weekly meal plans from one consoleReplace the dispatch whiteboard with a live production boardJob search command center with a self-filling pipeline board