# 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.

- Workflow type: agent
- Services: JobNimbus, Google Forms, Slack
- Categories: Sales
- Published: 2026-08-04

## What it does

- Watches your website intake form and picks up each new roof inspection request within about a minute of it being submitted.
- Checks your existing JobNimbus contacts by email and phone first, so a repeat customer gets the new request attached to their current record instead of a second one.
- Books the inspection job and creates a first call task for the right rep, chosen by the homeowner's zip code with a fallback when no rule matches.
- Posts the lead to your sales channel with the homeowner's name, address, their own description of the problem, and whether they are new or returning.

## What you'll need

- A JobNimbus account you can connect
- A Google account that owns the roof inspection request form on your website
- A Slack workspace with the channel your sales team watches
- The workflow and status names your JobNimbus account uses for contacts, jobs and tasks
- A list matching zip codes to reps, plus one fallback rep for anything unmatched

## Prompt

Watch my Google Form for new roof inspection requests submitted through my website, using the List Responses operation, and turn each new response into a real lead in JobNimbus within a minute. Speed matters here more than anything else: a homeowner contacted in the first minute converts dramatically better than one contacted an hour later, so do not batch these up or wait.

For each new response, read the homeowner's name, street address, phone number, email address, and their description of the roof issue. Keep their description word for word, because I want the rep to see the problem in the homeowner's own words rather than a summary.

Before creating anything, always run the duplicate check first. This is a first-class step, not an afterthought. Use the JobNimbus List Contacts operation to search my existing contacts for a match on the email address or the phone number from the form. Normalize phone numbers before comparing so that formatting differences do not cause a false miss.

If a matching contact already exists, do not create a second contact record. Attach the new request to the contact you found, recording the homeowner's description of the issue and the submission date against that existing record so their history stays in one place. If no match is found, use Create a Contact to add them as a new contact.

Either way, then use Create a Job to open the roof inspection job against that contact, whether it was found or newly created.

Important JobNimbus requirement: contacts and jobs both require a record_type_name, which is a workflow name from my account settings, plus a status_name, which must be a status that belongs to that workflow. Tasks require a record_type_name matching a task type. Read the valid names from my account settings rather than guessing them, and use the ones that match how my office already files new leads and inspections.

Next, use Create a Task so the assigned rep makes a first call to the homeowner within 30 minutes of the request arriving. Set the due time accordingly and make the task title make the urgency obvious.

Assign the rep by zip code. Take the zip from the homeowner's address and match it against my zip code to rep assignments. If no zip rule matches, assign the fallback rep rather than leaving the lead unassigned. Never let a lead land with nobody responsible for it.

Finally, use the Slack Send a Message operation to post the lead to my sales channel. The message must include the homeowner's name, their address, the problem in their own words, which rep it was assigned to, and clearly whether this is a new or returning customer. Call out returning customers loudly, with an obvious visual flag at the top of the message, because returning customers convert best and I want a rep to jump on those first.

Process each form response only once so the same request never produces two leads, two jobs, or two Slack alerts.

## How to customize

- Change the first call window, which is set to 30 minutes by default, to match your team's promise
- Update the zip code to rep assignments and pick who the fallback rep is
- Choose which channel gets the alert and how prominently returning customers are flagged
- Adjust which job and task types get used so they match how your office already files work

## Example output

🔁 RETURNING CUSTOMER (these close best, call first)

Dana Whitfield
412 Ridgeline Dr, Akron OH 44312

In her words: "Big leak over the garage after last night's storm. The ceiling is sagging and there is water sitting in the light fixture."

Matched an existing JobNimbus contact by phone, so no new record was created. Inspection job opened on her existing contact.
Assigned to Marcus Reed (zip 44312 rule). First call due by 2:41pm.

## FAQ

### How quickly does a new request show up in JobNimbus?

The form is checked continuously, so a request submitted on your website usually becomes a real JobNimbus lead within about a minute. That speed is the whole point, since contacting a homeowner in the first minute converts far better than waiting an hour.

### Will this create duplicate contacts for customers who come back?

No. Before anything is created, your contact list is searched by email and phone. If the homeowner already exists, the new request is attached to that record and a fresh inspection job is opened against it, so you keep one clean history per customer.

### What happens if the homeowner's zip code is not in my routing list?

The lead is assigned to your fallback rep instead of being dropped or left unassigned. Nothing sits in limbo waiting for someone to notice it.

### Do I have to change how my JobNimbus account is set up?

No. It uses the workflow and status names your account already has for contacts and jobs, so new records land in the same places your team is used to looking.

### What if my website form is not a Google Form?

This version listens to a Google Form, which is the most common setup for contractor websites and the one that can be watched for new submissions. If you collect requests another way, the rest of the workflow still applies once the responses reach a form or sheet.

Use this prompt in General Input: https://www.generalinput.com/prompts/turn-website-roof-inspection-requests-into-jobnimbus-leads