field-service

Jobber

Business management platform for small home service businesses

Take the CRM Scorecard Check Jobber fit

What Jobber does

Jobber is field service management software for small home service businesses. It helps operators capture requests, quote work, schedule crews, invoice customers, collect payments, and keep client history in one system instead of juggling spreadsheets and disconnected tools.

Where Jobber falls short

Jobber is strong at operational workflows after a lead is in the system, but it is not a full website, SEO, or conversion platform. Its native website tools focus on request and booking capture, so businesses still need an external site stack when they want richer page control, search visibility, stronger qualification logic, or more tailored on-site conversion paths.

How we set Jobber up

If you use Jobber's native website tools, a visitor submits a request or booking form and Jobber records that intake immediately as a Request in the account. If you use a custom website flow, the integration starts with Jobber's OAuth 2.0 authorization-code flow, then uses the bearer token against Jobber's GraphQL API. The most clearly documented write path is clientCreate, which creates a Client and stamps the app as the lead source inside Jobber. From there, the office team works that intake forward into the next Jobber workflow, usually a request, quote, or job, without waiting on a manual inbox handoff.

Integration method: graphql-api

Operating system

What Jobber already owns

Jobber is field service management software for small home service businesses. It helps operators capture requests, quote work, schedule crews, invoice customers, collect payments, and keep client history in one system instead of juggling spreadsheets and disconnected tools.

Primary users: Owners, office managers, dispatchers, and field supervisors at home service businesses

Typical fit: Small home service businesses, typically owner-operator through multi-crew teams

Core functions

  • Capture online requests and bookings
  • Create and send quotes
  • Schedule jobs, visits, and assessments
  • Dispatch crews and track work status
  • Invoice clients and collect payments
  • Manage client and property records
  • Automate reminders and follow-up messages

What still has to happen around Jobber

Jobber is strong at operational workflows after a lead is in the system, but it is not a full website, SEO, or conversion platform. Its native website tools focus on request and booking capture, so businesses still need an external site stack when they want richer page control, search visibility, stronger qualification logic, or more tailored on-site conversion paths.

It does not replace a full marketing site, CMS, or content system for SEO and answer-engine visibility.

Native website capture is centered on request and booking forms rather than fully custom landing-page experiences.

The strongest native embed path is through Jobber's own shared links plus WordPress and Wix plugins, not every custom front-end stack.

Complex pre-qualification, multi-step routing, and industry-specific intake logic usually need a custom website layer before Jobber.

API integrations require app setup, OAuth scopes, and GraphQL implementation rather than a lightweight public API key flow.

Reviewers still call out operational gaps around routing, reporting, pricing tiers, and limited functionality in some workflows.

Website and CRM integration surface

Native website path

Jobber can publish branded request and booking forms for customers, share those forms by direct link, surface the default request form inside Client Hub, and embed booking or request forms through its WordPress and Wix plugins.

request formonline booking formclient hub link

Developer surface

Public API
Yes
API style
graphql
Auth
oauth2-authorization-code
Webhooks
Yes
Rate limits
Documented
Sandbox
Yes

Jobber applies two limiters: 2500 requests per 5 minutes per app/account plus GraphQL query-cost throttling with a maximumAvailable of 10000 points and a restoreRate of 500 points per second.

Integration patterns that make sense

Native First

Fit

Use Jobber's native request or booking path when the business can live inside Jobber's form model and mainly needs fast lead capture into the operating system.

The website links to, or embeds, Jobber's request or booking experience. Submissions are processed as Jobber requests or bookings without a custom middleware layer.

Api First

Limited

Use an API-led approach when the site needs custom qualification, richer multi-step intake, or tighter data control before anything reaches Jobber.

A custom site or middleware application runs Jobber's OAuth 2.0 authorization-code flow, stores bearer and refresh tokens, and sends GraphQL queries or mutations to Jobber on the account's behalf.

Hybrid

Fit

Use a hybrid approach when the business wants Jobber as the system of record but needs a custom website layer to qualify, route, or reshape intake before handoff.

The website handles the front-end experience and qualification logic, then passes the approved data into Jobber through native forms where possible or through the GraphQL API when custom writes are needed.

Data objects your stack has to preserve

Create

Client, Request

Read

Account, Client, Request, Assessment, Job, Visit, Invoice, Quote

Update

Client

Webhooks

CLIENT_CREATE, CLIENT_UPDATE, CLIENT_DESTROY

Who usually fits a Jobber-centered website rebuild

Use this section to decide when Jobber's request form path is enough and when the website should qualify harder before it hands off through the GraphQL API.

Best fit

  • - Teams already running Jobber as the system of record
  • - Operators who need stronger qualification before data reaches Jobber
  • - Businesses that need a public site and intake flow shaped around field service demand

What operators complain about

  • We are frustrated that pricing feels expensive once operators need higher-tier features or more advanced workflow coverage.
  • We are frustrated that some users say mobile functionality still trails the desktop product in important day-to-day workflows.
  • We are frustrated that routing and route-management workflows are a recurring complaint for operators with repeat field routes.
  • We are frustrated that reviewers call out reporting and job-costing gaps, especially when third-party integrations do not pass enough financial detail through.
  • We are frustrated that users complain that some communication details, like clear visit-level service lists in confirmations, are still too limited.
  • We are frustrated that customer support quality is inconsistent in reviews, with some users describing it as slow or patronizing after the sale.

Technical trust before you connect the stack

Native path

request form

The website should only promise the Jobber handoff paths that are publicly documented.

Auth model

OAuth2 Authorization Code

If a custom handoff is needed, authorization into Jobber has to stay explicit and documented.

API surface

GraphQL API

Jobber still has to compete with ServiceTitan, Housecall Pro, Workiz while keeping the website handoff cleaner.

Auth: Jobber uses OAuth 2.0 authorization code flow for third-party apps. An admin user approves scopes in Jobber, the app exchanges the authorization code for an access token and refresh token, and the access token is then used as a bearer token on GraphQL requests.

Data flow: On the native path, the visitor fills out Jobber's own request or booking experience and the submission lands in Jobber right away. On a custom path, the website sends the captured data into an integration layer that calls Jobber's GraphQL API and then stores the resulting record in the Jobber account.

Webhooks: Jobber webhooks are configured per app and fire when subscribed topics occur on accounts that installed the app. Delivery is at-least-once, responses must return within one second, and duplicate deliveries need idempotent handling.

Security: Access is scope-based and granted by a Jobber admin during app authorization. Access tokens expire after about 60 minutes, refresh tokens must be stored carefully, and refresh-token rotation can invalidate older refresh tokens if apps are not written defensively.

Also in the evaluation set

If Jobber is on the table, these adjacent systems usually come up too. Use the CRM Scorecard to decide whether you need a horizontal CRM, a vertical operating system, or a cleaner connection between both.

ServiceTitanHousecall ProWorkizFieldPulseService Fusion

Jobber by industry

How Jobber gets configured for specific operating patterns.

appliance-repair

Jobber teams usually see the leak when dispatch has to rebuild the story from scratch. We keep getting repair requests, but the website still hides the appliance, brand, and warranty context until aft

See the setup

asphalt-paving

Jobber teams usually see the leak when dispatch has to rebuild the story from scratch. We keep getting vague paving inquiries with no clue how big or urgent the job is. When patching, maintenance, and

See the setup

auto-detailing

Jobber teams usually see the leak when dispatch has to rebuild the story from scratch. We get a dozen texts asking how much, but the website still sends us a vague message with no vehicle detail. When

See the setup

AV-installation

Jobber teams usually see the leak when dispatch has to rebuild the story from scratch. We keep getting project inquiries, but the website still makes every service call and theater consult look the sa

See the setup

chimney

Jobber teams usually see the leak when dispatch has to rebuild the story from scratch. We get buried during the fall rush, but the website still sends every sweep, leak, and rebuild inquiry through th

See the setup

commercial-cleaning

Jobber teams usually see the leak when dispatch has to rebuild the story from scratch. We keep getting 'need cleaning' messages, but the website still skips building type, frequency, and scope. When o

See the setup

commercial-equipment

Jobber teams usually see the leak when dispatch has to rebuild the story from scratch. We keep getting equipment service requests, but the website still hides the asset, site, and urgency until after

See the setup

concrete-epoxy

Jobber teams usually see the leak when dispatch has to rebuild the story from scratch. We lose jobs because I'm on the grinder and cannot answer the phone, and our website just sends us tire-kickers w

See the setup

deck-building

Jobber teams usually see the leak when dispatch has to rebuild the story from scratch. We get spring demand, but the website still makes us call back just to learn whether this is a new build or a tin

See the setup

electrical

Jobber teams usually see the leak when dispatch has to rebuild the story from scratch. We keep running into this problem: an emergency panel call and a remodel quote land in the same inbox. The electr

See the setup

energy-contractors

Jobber teams usually see the leak when dispatch has to rebuild the story from scratch. We keep getting energy project inquiries, but the site does not tell us enough to know what kind of project this

See the setup

excavation-grading

Jobber teams usually see the leak when dispatch has to rebuild the story from scratch. We're getting excavation inquiries, but the website still does not tell us what kind of site work this actually i

See the setup

fence-installation

Jobber teams usually see the leak when dispatch has to rebuild the story from scratch. We're wasting gas driving out to give free quotes to tire kickers who have zero budget, while the real jobs slip

See the setup

fire-and-security

Jobber teams usually see the leak when dispatch has to rebuild the story from scratch. We keep getting website inquiries, but the site still hides whether this is inspection work, a service fault, or

See the setup

garage-door

Jobber teams usually see the leak when dispatch has to rebuild the story from scratch. We spend real money on emergency demand, but the website still treats every request like the same form fill. When

See the setup

general-contractors

Jobber teams usually see the leak when dispatch has to rebuild the story from scratch. We keep calling people back just to figure out what kind of project they even want. When kitchen remodels, deck b

See the setup

glass-repair-installation

Jobber teams usually see the leak when dispatch has to rebuild the story from scratch. We keep getting glass requests, but the website still makes broken-glass emergencies and measured quotes look the

See the setup

gutter-cleaning

Jobber teams usually see the leak when dispatch has to rebuild the story from scratch. We are buried in leaves from October through November; the phone rings off the hook while we are on ladders, and

See the setup

holiday-lighting

Jobber teams usually see the leak when dispatch has to rebuild the story from scratch. We get overwhelmed with requests the week of Thanksgiving, but half of them expect us to hang the tangled lights

See the setup

HVAC

I keep paying for estimate requests that land in email first, then cool off while my office is already buried. CRM Coach fixes the lead-handoff repair layer so every HVAC inquiry reaches Jobber as a C

See the setup

irrigation

Jobber teams usually see the leak when dispatch has to rebuild the story from scratch. We get crushed during startup and blowout season, but the website still makes every irrigation request look the s

See the setup

junk-removal

Jobber teams usually see the leak when dispatch has to rebuild the story from scratch. We are losing jobs because we miss calls while dumping at the landfill, and our website just sends us emails with

See the setup

landscaping

Jobber teams usually see the leak when dispatch has to rebuild the story from scratch. We get form fills, but half of them are junk and the good ones sit too long before anyone can call them back. Mos

See the setup

locksmith

Jobber teams usually see the leak when dispatch has to rebuild the story from scratch. We pay for urgent demand, but the website still sends every lockout, rekey, and commercial access request into th

See the setup

mechanical-contractors

Jobber teams usually see the leak when dispatch has to rebuild the story from scratch. We keep mixing replacement opportunities with routine service requests. When service, maintenance, and replacemen

See the setup

mold-remediation

Jobber teams usually see the leak when dispatch has to rebuild the story from scratch. We keep losing urgent calls because the website still treats active water and inspection work like the same form

See the setup

moving-company

Jobber teams usually see the leak when dispatch has to rebuild the story from scratch. We keep getting move inquiries, but the website still hides the date, distance, and inventory behind a vague mess

See the setup

painting

Jobber teams usually see the leak when dispatch has to rebuild the story from scratch. We get website requests but half the time we drive across town and the homeowner just wanted a ballpark number, o

See the setup

pest-control

Jobber teams usually see the leak when dispatch has to rebuild the story from scratch. We're bleeding money on requests that do not convert, but the website still treats every pest problem the same. W

See the setup

plumbing

Jobber teams usually see the leak when dispatch has to rebuild the story from scratch. We keep running into this problem: a burst pipe call comes in through the website and lands in the same inbox as

See the setup

pool-service

Jobber teams usually see the leak when dispatch has to rebuild the story from scratch. We need the website to tell us if this is a good route-fit service account or just another one-off problem call.

See the setup

pressure-washing

Jobber teams usually see the leak when dispatch has to rebuild the story from scratch. We get quote requests, but most of them are missing the details we need to price the job without chasing people d

See the setup

property-management

Jobber teams usually see the leak when dispatch has to rebuild the story from scratch. We keep getting maintenance requests, but the website still sends them without enough property detail to know who

See the setup

remodeling

Jobber teams usually see the leak when dispatch has to rebuild the story from scratch. We keep running into this problem: kitchen, bath, addition, and whole-home inquiries arrive with no budget or sta

See the setup

roofing

Jobber teams usually see the leak when dispatch has to rebuild the story from scratch. When weather hits, the site floods us with inspection requests but half of them are missing the details we need t

See the setup

septic

Jobber teams usually see the leak when dispatch has to rebuild the story from scratch. We keep getting septic requests, but the website still makes every backup, pump, and inspection look the same. Wh

See the setup

specialty-trades

Jobber teams usually see the leak when dispatch has to rebuild the story from scratch. We keep making customers explain the same problem twice because the site captured almost nothing useful. When urg

See the setup

tree-service

Jobber teams usually see the leak when dispatch has to rebuild the story from scratch. We keep running into this problem: the good tree requests need fast triage, but the website dumps everything into

See the setup

utility-contractors

Jobber teams usually see the leak when dispatch has to rebuild the story from scratch. We keep getting messages through the site, but they are so generic that we still have to figure out whether this

See the setup

water-damage-restoration

Jobber teams usually see the leak when dispatch has to rebuild the story from scratch. We pay for urgent water-damage demand, but the website still makes every mitigation and rebuild request look the

See the setup

window-cleaning

Jobber teams usually see the leak when dispatch has to rebuild the story from scratch. We're drowning in voicemails while we're up on ladders, and by the time we get down to call back, the request alr

See the setup

Not sure if Jobber is the right fit?

The CRM Scorecard surfaces what your team actually needs from a CRM before you commit to one.

Take the CRM Scorecard