Four to switch on. One to skip.

Transcript

JobNimbus automation. The four rules JobNimbus says to switch on first, the one worth building yourself, and the one to skip.

This is for owners and office managers already on JobNimbus. Everything here is from JobNimbus's own help center and Zapier's app page, checked October twenty-sixth. Every job and name you'll see is made up.

Start with the leak. A siding job moves to Sold on Friday at three-ten. The contract is signed and the measurements are attached, but the homeowner hasn't signed off on the color. Sales can fairly call it sold. Purchasing can't order it. And if Sold is wired to release the material order, the order goes out anyway.

JobNimbus says to start with the automations already in your account, and it names four to switch on. Two: the inspection appointment reminder task, a day before the start date. Three: the estimate follow-up, two days after the status changes. Five: invoice balance due, three days after. And six: the thank-you and review email, when a job is modified.

Before you switch them on, read the email templates behind the reminder, the invoice and the review email, and check which statuses each one watches. Number six needs one more fix: require your closing status and turn on Only if Status is modified, or an ordinary edit can send the review email again.

Rule one, the quiet estimate. Starter three already runs two days after the status changes. Edit it, or build the same rule, so it gives the salesperson a review task. Say the homeowner replied Tuesday: does this include repainting the trim? That's the next conversation. A second "did you get our quote?" makes it look like nobody read the reply.

Anchor it to the date the status changed, not the last edit, so a note added Tuesday doesn't quietly push the task later. If you text, Engage is a separate subscription, and replies to automated texts land in Engage's Unassigned tab, not with the salesperson. Start with a task until someone owns those replies.

Rule two is the one to build: when a job moves to Sold, a production reviewer gets a task. Event-based, on the job, Created or Modified. Condition: your actual Sold status, with Only if Status is modified turned on. Action: create a task assigned to the reviewer, kept linked to the job.

The task names the missing item and who gets it. Not "job incomplete." This: color selection is missing. Alex confirms the color with the homeowner. Don't release the material order until the package is approved.

And that's the one to skip: letting Sold release the material order on its own. A status can't prove the selections are complete. Monday at nine, the signed color arrives and the reviewer clears the package. At eleven-twenty, the homeowner asks for a different color. An updated attachment can't tell you which siding the supplier will deliver. Reopen the review, check whether an order already went out, and if it did, a person settles it with the supplier.

Test it before the office trusts it. Add an ordinary note while the job stays in Sold: you should still have one task. And don't let a completed task create another task of the same type without another condition. JobNimbus warns that's how loops start.

Outside JobNimbus, the Zapier connector is narrow. Its two triggers start on a contact or a job. Its actions create contacts, jobs and attachments, and update contacts. Nothing updates a job, changes its status or creates a task. So Zapier can bring a form lead in as a contact and a job, and send job changes out to a sheet. Anything written back to a job needs the API.

Angi leads connect directly, without Zapier. Create an API key with an admin access profile and paste it into Angi. Without admin access, the leads quietly never arrive. And a key keeps the permissions it was made with, so fixing the profile later doesn't fix the key. Make a new one.

One date to put on a calendar. New API keys expire one year after they're created, and keys made before September eighteenth are legacy keys that expire too. That day, every Zap using the key stops reaching JobNimbus, and Angi leads stop arriving.

That's the whole setup: four starters checked, a task when an estimate goes quiet, a review when a job is sold, a person between Sold and the order, and a calendar date for every key. The starters you can switch on this afternoon. The review and the changed selection are where offices stall, and that's what we build.

GoodHandoff sets these up inside your JobNimbus, writes the tasks and messages with you, and runs it. Every month you get a report of what got done: estimates followed up, jobs handed off, invoices collected.

Here's the price, up front. A workflow build runs from fifteen hundred to five thousand dollars, depending on how much it covers. Then fifteen hundred a month for the Care plan, month to month. Anything JobNimbus charges for, like an Engage subscription for texts, is billed by JobNimbus directly to you.

If you've got a job sitting in Sold right now, book a free twenty-minute call at goodhandoff dot com. Bring your JobNimbus board and one job that stalled, and we'll show you what JobNimbus can already do.

Example with made-up customers. Narration is an AI voice.