Everything you need to get your shop off the whiteboard and onto the board — from your first import to your first dispatched job, plus the concepts and API behind it all.
Set up your workspace
A workspace is your shop inside Jobwright — one place for your customers, technicians, price book, and the dispatch board. When your account is provisioned you'll land on an empty board with three things to do before you can dispatch a real job.
Confirm your shop details. Your business name, service area, time zone, and tax rate. The tax rate flows into every quote and invoice, so get it right up front.
Add your first technician. Invite a tech by mobile number. They'll get a text with a link to the Jobwright tech app — no app-store hunting required.
Set your business hours. The board only offers dispatch slots inside the hours you keep, plus any on-call window you define for after-hours emergencies.
Tip: Dispatchers and office staff don't count as billable seats. Invite your whole front office — only technicians running jobs in the field use a paid seat.
Import your customers
Bring your existing customer list over so you're not typing addresses on day one. Jobwright accepts a CSV export from most CRMs, spreadsheets, and accounting tools.
Go to Settings → Data → Import and upload your CSV.
Map your columns to Jobwright fields — name, service address, phone, and email at minimum.
Review the preview. Rows with a missing address are flagged so you can fix them before they land.
Each imported customer becomes a record that holds their service history, equipment, and every past work order. When a call comes in, your dispatcher searches by name, phone, or address and the whole history is right there.
Load your price book
The price book is your catalog of services and parts with prices, costs, and default tax treatment. It's what turns a quote from a guess into a number your tech can stand behind at the door.
Services — flat-rate tasks like Cooling diagnostic or Drain clearing, each with a price and an expected labor time.
Parts — physical items like a 45/5 µF run capacitor, with a cost and a markup so margin is calculated for you.
Bundles — a service plus its common parts, added to a work order in one tap.
When a technician builds a quote in the field, they pull straight from the price book — so pricing is consistent whether it's your senior tech or a second-year apprentice at the door.
Dispatch your first job
With a customer, a technician, and your hours in place, you're ready to run a real service call.
Book the call. Create a job from a customer record, pick the job type, and drop it on the board — or let Jobwright suggest the best open slot.
Assign a tech. Drag the job onto a technician's row. Jobwright checks their skills and drive time and warns you if the day is getting tight.
Roll the truck. When the tech taps On my way, the customer gets a text with the tech's name, photo, and live ETA.
Close it out. The tech logs parts and labor, collects a signature, takes payment, and the work order becomes an invoice — before they leave the driveway.
Jobs & work orders
These two words get used interchangeably in the field, but in Jobwright they're related and distinct:
JobA scheduled visit on the board — a time, a place, and an assigned technician. One customer can have many jobs over the years.
Work orderThe record of what actually happened on a job — the diagnosis, parts, labor, photos, signature, and invoice. It's the paper trail.
A job that never gets worked (a cancellation, say) has no work order. A big install might be one work order spread across several jobs on the board over multiple days.
The dispatch board
The board is the heart of Jobwright: a timeline with one row per technician and one column per hour of the day. Each job is a block you can drag between techs and times. Color tells you status at a glance — scheduled, in progress, urgent, or done.
A dashed line marks the current time so your dispatcher always knows who's behind and who has room for one more call. Everything on the board is live: move a job and the affected ETAs, the customer notification, and the technician's app all update together.
Technicians & skills
Every technician has a set of skills — the trades and certifications they're qualified for, like EPA 608, gas, or panel work. When you assign a job, Jobwright checks the required skill against the tech's profile and flags a mismatch before the truck rolls, so you don't send an apprentice to a job that needs a license.
Quotes & invoices
A quote is a priced proposal a customer approves; an invoice is the bill for work that was done. In Jobwright the two share the same line items, so an approved quote becomes an invoice without re-keying a thing.
Build a quote from the price book and send it to the customer's phone.
The customer approves and signs — you get notified on the board.
The tech completes the work and converts the approved lines to an invoice.
Collect card or ACH on site, and the invoice is marked paid and reconciled.
API quickstart
Every Fleet workspace can automate Jobwright over a REST API. Authenticate with a workspace API key as a Bearer token, then create and read work orders, jobs, and invoices as JSON.
# Create a work order for an existing customercurl https://api.jobwright.app/v1/work-orders \
-H "Authorization: Bearer $JOBWRIGHT_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"customer_id": "cus_8Kd2",
"type": "no_cooling",
"priority": "urgent",
"scheduled_for": "2026-08-18T10:00:00-05:00"
}'# → 201 Created{ "id": "WO-4822", "status": "scheduled", "customer_id": "cus_8Kd2" }
Responses are JSON, times are ISO 8601, and money is returned in cents to keep rounding honest. Rate limits are returned in the X-RateLimit-Remaining header.
Webhooks
Subscribe to events so your other systems react in real time. Point a webhook at your endpoint and Jobwright will POST a signed payload whenever things happen on the board.
job.dispatched — a technician was assigned and notified
work_order.completed — the tech closed out and captured a signature
invoice.paid — payment cleared for an invoice
Every delivery is signed with your endpoint secret in the Jobwright-Signature header. Verify it before you trust the payload.