Jobber website integration: should a new lead become a request or a booking?

A new lead asking about a bathroom renovation needs a different next step from a regular customer booking routine maintenance. Your Jobber website integration should make that difference clear to both the customer and the office.

Decide what someone can book on their own and what your team needs to review first. That decision will guide the form, the record it creates and the confirmation the customer receives.

Understand Jobber's three intake paths

Jobber's online booking starts with request forms. A form can gather information for review, include an assessment-booking question, or include a job-booking question, subject to plan and configuration. Here's what each option creates:

• Request form: a Request for the team to review and follow up.
• Assessment booking: a Request plus a scheduled assessment.
• Job booking: a converted request and a scheduled one-off job.

A form can contain one booking type, not both assessment and job booking. Jobber advises separate forms when both are needed. Check what's available in your account before offering it on your website. Jobber's online-booking guide explains the record types.

Match the button and confirmation text to what happens next. Someone clicking “Request an estimate” should be sending a request for review. For “Book an assessment,” explain what the visit covers and any agreed fee or conditions.

When a new lead needs a conversation first

Imagine a homeowner asking about a bathroom renovation. The scope, access and timing are still unclear. A request form gives them room to describe the project and lets the office work out the next step.

Ask for what you need before the first conversation: contact details, the work location, the service required and a useful description. Leave the longer list of questions until someone actually needs the answers.

Agree who handles the lead when it arrives. Someone needs to check the service area, decide whether an assessment makes sense and contact the homeowner if details are missing.

The success message should confirm receipt and explain what comes next. Include the estimate team's working hours if they affect the response. Make sure an ordinary request form can't be mistaken for a monitored emergency service.

These customer journeys are planning examples, not live Goliath case studies.

When a returning customer wants routine work

A returning customer may be booking a familiar maintenance service. Direct booking can work well when you have clear rules for the work included, duration, eligibility and available appointments.

Check the details that can change. The customer may have moved, need work at another property or have a different problem this time. Don't carry the last job's details forward just because you recognise the email address.

Let the customer confirm the work address and selected service. Send requests outside the booking rules to the office for review rather than squeezing them into the nearest free appointment.

Test the website message alongside the resulting calendar entry, including any approval settings. The customer should know whether they've requested a time or secured one.

When one customer manages several properties

A property manager makes customer matching more complicated. The contact might be the same across several work sites, while the occupant, access information and billing instructions differ.

For a custom Zapier route, there is a concrete limitation to address: Zapier's Jobber documentation says Create Request, Create Quote and Create Job use the client's first property when multiple properties exist. Read Zapier's documented Jobber limitations.

Adding another address field to the website won't necessarily fix this. Ask the builder to show how the workflow selects the correct property using supported tools. If it can't, keep the request for office review or use another approach that has been verified.

Test with a customer who has at least two properties. Confirm the actual linked work site, not just an address copied into a note. This catches a mistake that an ordinary single-property test would miss.

Native form or custom intake workflow?

Use native Jobber forms when their questions, record behavior and booking settings fit the process. Keeping intake close to the system your office uses can reduce the number of separately maintained steps.

A custom form and connection may make sense when another system needs the lead details, enquiries need extra routing or the website needs a different form experience. Be specific about the gap. “We want every request checked against our commercial-service rules before assignment” is more useful than “we need a better integration.”

Ask the builder to show how each lead detail reaches Jobber:

• What identifies the client, and what happens when the match is uncertain?
• What identifies the property where the work will happen?
• Which Request, assessment or job record should exist afterward?
• Where do the original description and attachments go?
• Who receives a request that cannot be processed?
• What prevents another submission or replay from creating duplicate work?

The general principles are covered in our website, CRM and field-service integration guide. The property relationship is a Jobber-specific detail your design must resolve.

Give the office a way to recover

Connections can stop working when access changes. Zapier specifically notes that deactivating the Jobber team member who connected the accounts disconnects that integration. Include that connection in the handover checklist when someone leaves or their access changes.

Write down who owns the connection and who receives failure alerts. They need to be able to tell whether a request never arrived or only part of the workflow failed.

If the booking was created but a later notification failed, replaying everything could create a second booking. Check the record before retrying, and give staff a recovery checklist they can follow without guessing.

Test the promise, not just the form

Before launch, run a short acceptance check:

1. A new customer submits a request without booking.
2. An eligible customer books the intended assessment or service.
3. A returning customer requests a different address.
4. A multi-property client requests work at the second property.
5. Someone submits twice or corrects an earlier request.
6. No suitable appointment is available.
7. A connection fails after one step has already succeeded.

For each test, check the customer message, client, property, created record and schedule. Make sure someone knows what to do next. Resolve anything the team can't explain before accepting real leads.

Then measure how quickly requests receive a useful response. Our speed-to-lead guide separates acknowledgements from actual conversations.

Build around how you accept work

Start with Jobber's own forms, check the records and properties they create, and add custom steps where you find a real gap. The customer should know what they've requested, and the office should have the details it needs to act.

If leads are arriving in Jobber with missing details or the wrong next step, explore Goliath's automation and integration services. If customers struggle with the form before they get that far, start with our website design services.