Field service ticket software is the office's view of a call: it opens when the phone rings, carries the customer, the problem, the tech and the window, collects the hours and the parts as the visit happens, and closes when the invoice goes out and the report is filed. A field service ticketing system for a small company is that lifecycle and nothing more elaborate, and field service time tracking is the part of it that turns the tech's hours on site into the labor line. This page says what a ticket has to carry for a company of one to a dozen techs, works the labor and the invoice from the hours on an example, and points at the free tools on this site that work them. It publishes no labor rate; the rate is the company's own.
The ticket opens with the call and carries the customer's history
A ticket is the customer, the address, the problem as described, the tech assigned and the window promised, opened while the caller is still on the phone and carrying the last visit's report so the tech arrives knowing what was done. For a dozen techs it is a list with a status; the ITSM ticketing platforms built for help desks carry SLAs and escalations a small field service company does not need, and this site names them only to say they are another product.
Time tracking: the hours on site become the labor line
Field service time tracking is the tech's hours on site, per tech, written on the ticket. Two techs for three hours each is six technician hours and, at the company's $90 rate, $540 of labor on the worked example; with $120 of parts the visit is $660. The free field service report on this site works that from the techs, the hours and the rate the company enters, and estimates the follow-up visit's labor from the hours the tech expects it to take. The rate is the company's and this site publishes none.
The ticket closes on the invoice and the report
A ticket that closes without an invoice is revenue the company forgot. The free field service invoice works the call from the ticket's figures: 1.5 hours at $90 is $135, $60 of parts at 40% markup is $84, tax at 8% on the parts is $6.72, a $49 trip charge makes $274.72. The report records what was done and what the follow-up needs. Both are kept against the customer and the job on FlatRateBook Pro; the free tools work them with no account.
Why a field service ticketing system should not be a help desk
Field service ticketing system searches lead to IT help-desk platforms, because the word ticket is theirs. Those tools track requests and SLAs for an IT team; a field service ticket tracks a van, a tech's hours, parts and an invoice. The record a small company needs is the second kind, and the charter of this site draws the line there: the call from ring to invoice, priced from the company's own figures.
Mobile field management: the ticket on the tech's phone, closed before the van leaves
Mobile field management is the ticket in a pocket rather than a second system. The tech opens the job, reads what the office wrote when the phone rang, adds the hours on site, the parts fitted and what was found, prices it at the rate the job was booked at, and closes it with the customer's signature before pulling away. The office does not retype any of it. What matters is the order: the ticket is the record and the invoice is produced from it, so a product that asks the tech to fill in a job sheet and then asks somebody to create an invoice has two records that can disagree, and they will.
Mobile field management: the ticket on the tech's phone, closed before the van leaves
Mobile field management is the ticket in a pocket rather than a second system. The tech opens the job, reads what the office wrote when the phone rang, adds the hours on site, the parts fitted and what was found, prices it at the rate the job was booked at, and closes it with the customer's signature before pulling away. The office retypes none of it. What matters is the order: the ticket is the record and the invoice is produced from it, so a product that asks the tech to fill in a job sheet and then asks somebody in the office to create an invoice has two records that can disagree, and in time they will.
Questions people ask about field service ticket software
What is field service ticket software for a small company?
The record of a call from the phone ringing to the invoice: customer, problem, tech, window, hours on site, parts, invoice and report, kept against the customer. Not an IT help desk.
How does field service time tracking work on the ticket?
The tech's hours on site, per tech, are written on the ticket and become the labor line at the company's rate. The free field service report works the technician hours, the labor and the visit total from those figures.
Does the ticket produce the invoice?
On this site the field service invoice works the call from the same figures the ticket carries: hours at your rate, parts at your markup, tax on the parts at your rate, the trip charge. The paid plan keeps both against the job.
Which apps for field service does a two-van company actually need?
One, and it has to do three things: carry the ticket, price the call and keep the customer. Everything sold separately beyond that, a routing app, a separate inventory app, a separate time clock, adds a second place for the same facts to live. Start with the ticket that produces the invoice, and add nothing until something it cannot do is costing you real time.
Which apps for field service does a two-van company actually need?
One, and it has to do three things: carry the ticket, price the call and keep the customer. Anything sold separately beyond that, a routing app, an inventory app, a time clock, adds a second place for the same facts to live. Start with the ticket that produces the invoice and add nothing until something it cannot do is costing you real time.