Instant review requests when a Jobber job is completed
The moment a job is marked complete in Jobber, the customer gets a warm thank-you and a review link, and every request is logged so you can track your review funnel.
When a job is marked complete in Jobber, send that customer a personalized thank-you and review request, and log the outcome so I can track my review funnel. Trigger this with a Jobber outgoing webhook subscribed to the JOB_COMPLETE topic, which Jobber fires when a job is marked as completed.
Important: the Jobber webhook payload does NOT contain the job data. It only tells you the topic, the account id, and the item id of the object that changed. Treat the payload as a pointer, not a record. Take the item id from the webhook and call Jobber's Get Job to load the actual job: the job title, line items, notes, completion date, total value, the client it belongs to, and the team member assigned to the work. Everything downstream depends on that lookup, so if Get Job fails, retry before giving up rather than sending a vague email.
Use the client id on the job to call Jobber's Get Client for the customer's name and email address. Use the assigned team member id to call Jobber's Get User for the technician's name. If the job has more than one assigned team member, use the primary or first assigned one.
Before drafting anything, decide whether this job should receive a review request at all. Read the job title, line items, and notes and skip the request if the work reads as a warranty visit, a callback, a re-do, a return trip to fix earlier work, or a punch list cleanup. Asking for a review on a fix-up job backfires and generates negative reviews, so when the signals are ambiguous, err toward skipping. Also skip any client with no email address on file. In both cases still log the job, just with no request sent and a short reason.
For jobs that pass, draft a warm, short thank-you email to the customer. Name the specific work that was performed, drawn from the job title and line items, and thank the technician who did it by name. This should read like a note from a small business owner who remembers the job, not a template: address the customer by their first name, keep it to a few sentences, and vary the wording, structure, and subject line for every customer. Include my review link with a simple, low-pressure ask. Do not invent details that are not in the job record. Send the email with Gmail's Send a Message to the client's email address.
Finally, append a row to my review tracking Google Sheet using Google Sheets' Append Values. Capture the job title and id, the client name and email, the completion date, the job value, the technician, whether a review request went out, and the reason when it did not (warranty or callback, no email on file, below my minimum job value). Append one row per completed job, including the skipped ones, so the sheet is a complete record of the funnel rather than only the sends.
Let me configure the review link, the sending Gmail account, the target spreadsheet and tab, an optional minimum job value below which no request is sent, and the words and phrases that mark a job as a warranty visit or callback in my business.
Additional information
What does this prompt do?
- Starts the moment a job is marked complete in Jobber, so the thank-you lands while the work is still fresh in the customer's mind.
- Writes a short, personal note that names the exact work performed and the technician who did it, then sends it from your own inbox with your review link.
- Skips warranty visits, callbacks, and re-dos automatically, so you never ask for a review on a job that already went wrong.
- Logs every completed job in a spreadsheet with the customer, completion date, job value, and whether a review request went out.
What do I need to use this?
- A Jobber account connected to General Input, with access to jobs, clients, and team members.
- Job completion updates enabled in Jobber so we hear about a job the moment it closes.
- A Gmail account to send the thank-you emails from.
- A Google Sheet to log review requests in. A blank sheet is fine.
- The link where you want customers to leave their review.
How can I customize it?
- Swap in your own review link, or point customers at Facebook or your own site instead of Google.
- Tune the wording that marks a job as a warranty visit, callback, or re-do so it matches how your team writes job titles and notes.
- Set a minimum job value so small or no-charge visits never trigger a request.
- Change which columns land in the tracking sheet, or log to a different sheet per crew or location.
FAQs
How quickly does the email go out?
How does it know a job was a warranty visit or a callback?
Will every customer get the same email?
What happens if a customer has no email address on file?
Can I see how many review requests actually went out?
Related templates
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.
Every weekday at 7am, your active courses are checked for missing work, silent logins, and slipping grades, with a ranked list sent to your advising channel.
Every Monday at 8am, see exactly which assignments have work waiting, sorted worst first, posted to Slack and logged to a spreadsheet.
Every weekday morning your advising team gets a ranked list of students slipping behind in each course, plus a tracking log that shows whether outreach worked.
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.
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.
Ask for the review at exactly the right moment.
Every completed job gets a personal thank-you within minutes, and the jobs that should never be asked get skipped automatically.