How it works
One job, six steps, one set of records
No module diagram. Here is the actual path a job takes through SkillBison, and who can see what along the way.
Three logins, three different views
What somebody can see is decided by the database, not by hiding menu items.
Technician
Opens on the time clock. Sees today's jobs, the reason for the call, on-my-way, call, text and map. Scans equipment, takes photos, gets a signature, sees their own hours and their own pay. No invoices, no payroll, no other people's customers.
Dispatcher / scheduler
Owns the board: the calendar, dispatch, customers, crew and the price book. Cannot see invoices, payables, payroll, reporting or the owner dashboard, and typing those addresses directly does not get them in.
Owner / admin
Everything. The dashboard, invoices, payments, vendor bills, payroll, the general ledger and the reports built from it.
The path a job takes
- 1
1. Call to job
A short form captures the customer, the service address and the reason for the call. A brand-new customer can be created in the same step. The job appears on the board immediately with its own job number.
- 2
2. Job to technician
Assignment checks the roster for that day, the skill the job requires, and whether the person is already booked. A dispatcher can override and send someone anyway, but that takes a confirmation and is recorded.
- 3
3. Technician to site
On my way tells the office. At the property the technician scans the equipment data plate, takes photos and writes notes. With no signal, everything queues on the phone and syncs when the connection comes back.
- 4
4. Diagnosis to options
Three options are drafted from your own price book. A person must review them before the customer sees anything. The customer picks one, types their name and signs on the screen.
- 5
5. Approval to invoice
The signed option becomes the invoice with no retyping, so the invoice cannot disagree with what was approved. Invoice numbers run per company starting at one.
- 6
6. Payment to books
A payment is recorded only once it is confirmed. The receivable clears and the cash lands. Balanced ledger entries are written at the same moment, alongside vendor bills and payroll.
What we check before we say something works
Every step above has been run end to end in our demo build against made-up customers and test-mode payments.
- The job survives a page reload at every stage
- A technician cannot read another company's data, or the money screens
- Work captured offline reaches the server after reconnecting
- An invoice is only marked paid after the payment is confirmed
- The trial balance still balances after invoicing, vendor bills and payroll
Honest limits: text and email delivery is queued but not confirmed to a real phone or inbox; card payments run in sandbox test mode; offline behaviour is proven on one physical phone, not a fleet; and a new customer currently needs an email address before a job can be booked.
See the whole path in half an hour
We run one job live, from the phone call to the ledger entry, on made-up data.