Jobber

What your receptionist can do with Jobber, action by action — and what still has to be proven before it is announced.

7 days, 20 answered calls, no card

The software, its edition, the trades concerned

Jobber is field service management software used by trade businesses: clients, requests, quotes, jobs, invoices. It is available in Canada, and it is one of the most common tools among plumbers, electricians, landscapers and roofers in the province.

What Zenvox wants to do with it is narrow: attach a call to the right client, file a structured request, and find the quote being discussed when the customer calls back. Nothing more until each write has been proven on a real account.

Access is granted through an authorisation you give from your own Jobber account. Past a small number of paying accounts, the vendor requires a review on its side — that is its rule, not ours, and it is named here because it can delay an installation.

Read, create, update, cancel

The status below is technical qualification at the time of checking. It changes when an authenticated test makes it change, not before.

ActionStatusWhat that means
ReadTo qualifyThe client, request and quote model is documented by the vendor. Reading is described; no authenticated test from Zenvox has been recorded yet.
CreateTo qualifyCreating a request and a quote is described. It has to be proven with attachments, options and behaviour on repeated sends before it is announced.
UpdateTo qualifyUpdating an existing object depends on webhook events whose exact list still has to be checked in the vendor developer area.
CancelTo qualifyCancelling and refusing touch payment reconciliation and statuses changed by hand inside Jobber. Until those cases are tested, the receptionist does not perform them.

What is included, what needs an add-on

Answering, qualifying and sending you the request is in your base: Jobber changes none of that. A connection exists to avoid double entry, not to unlock a feature. Preparing and following up a quote is a separate add-on, with or without Jobber.

Add-ons for working with this software

Assisted estimates

The estimate file and the follow-up. The Jobber connection helps find the right quote; it does not replace the add-on.

Dispatch and field work

Assigning a job to a crew. The system of record still has to be settled: two tools assigning the same person create conflicts.

The authorisation, and what holds the truth

A connection is granted, reviewed and revoked. These four points are the condition of a clean installation.

  • You authorise from your Jobber account; Zenvox does not ask for your password
  • The authorisation is limited to the qualified operations in the matrix above
  • A system of record is chosen per object — client, request, quote — so one piece of data has one truth
  • You revoke the authorisation whenever you want; the receptionist returns to Zenvox native mode and nothing stops

A known customer calls about a second job. The Jobber account is authorised, reading is qualified, writing is not.

CustomerHi, you came last year for my drain. It is happening again.

ReceptionistLet me find you. I will take your name and a callback number first, then check what was done last time.

ReceptionistSame address? I am logging this as a return on a past job, and passing the request along with the file attached.

The request reaches the owner with the customer recognised and the past job as a reference. No write happens in Jobber while creation is unproven: the owner opens the file and decides.

If the connection is not there

A missing connection blocks nothing. The receptionist then works in native mode, and you pick the request up where you work.

  • The request is created in Zenvox, with the same fields and the same qualification
  • You find it in your workspace, and copy it into Jobber if you want to
  • No base capability depends on third-party software
  • The day an operation becomes qualified, it is added without changing your setup

Questions about this connection

Does she write into Jobber, or only read it?

Neither is announced as settled today. Reading and writing are both described by the vendor and both remain to be proven from Zenvox; until an authenticated test is recorded, the request is written into Zenvox and you open the file yourself.

What happens if I do not connect Jobber?

Nothing stops. The receptionist works in native mode and creates the request inside Zenvox with the same fields and the same qualification; you find it in your workspace and copy it into Jobber if you want to. No base capability depends on third-party software.

Does Zenvox ask for my Jobber password?

No. You authorise from your own Jobber account, and the authorisation is limited to the qualified operations in the matrix. You revoke it whenever you want; the receptionist returns to native mode and service carries on.

Does my team have to change how it works?

No. Jobber keeps the truth of the client, the request and the quote, and a system of record is chosen per object so one piece of data has one truth. The receptionist answers, qualifies and hands the request over; your team carries on in the tool it knows.

Why might an installation take longer?

Because past a small number of paying accounts the vendor requires a review on its side. That is its rule, not ours, and it is named here because it can delay an installation. Nothing in your service waits on it meanwhile.

Where to next

See the trade concerned, or the full software list.

Jobber

What your receptionist can do with Jobber, action by action — and what still has to be proven before it is announced.

Start your free trial7 days, 20 answered calls, no card