Plan the work.
Create the job, keep the customer context nearby, and assign the people and time it needs.
A product by VSBLTY Tech
A connected workspace for field service
Every job.
One connected record.
Bring service requests, technician visits, parts and invoices into one connected workspace. Keep the office and the field working from the same job record.
The work between the handoffs
A visit is one part.
The job has a whole story.
Someone takes the request. Someone plans the day. A technician does the work. The office follows through.
Each handoff needs context: what the customer asked for, which equipment needs attention, who is assigned, what happened on the visit, and what should be invoiced.
ServiceGuru joins those records and actions in one field-service workspace. The next person can pick up the job with its schedule, customer history and progress in view.
Carry the context.
See assigned work, the service address, equipment and complaint. Record progress and the work performed.
Follow it through.
Keep stages, parts and completion visible, then connect finished work to an invoice and its payment record.
From request to record
One job.
Four connected steps.
A schedule gives the work a place in the day. Assignment gives it an owner. The record carries what happened into the next step.
Example job flowIllustrative workflow
What needs attention?
Start with the customer and the job.
Connect the request to its customer, service address and equipment. Record the complaint and service type so the person planning the visit has the context they need.
Customer → equipment → service request
-
01 / REQUEST
Know the job.
Link the customer, equipment, complaint and service address.
-
02 / ASSIGN
Give it an owner.
Connect the technician, scheduled time and current stage.
-
03 / COMPLETE
Keep what happened.
Record stage progress and work done. Finalize the job explicitly.
-
04 / INVOICE
Follow the record.
Create the invoice from completed work, then record payments against it.
The context stays connected
A customer record.
A working history.
The work around a customer includes more than a phone number. Addresses, equipment, service visits and invoices each belong to the same operational story.
The customer
Contact details, service addresses and notes give each job its starting context.
The equipment
Linked devices carry their type, brand, model and serial details into the service record.
The service history
Related tickets show previous and current work, their status and the people assigned.
The invoice
The job and customer stay linked to line items, the amount due and recorded payments.
Keep the parts beside the job.
Manage shared stock and engineer inventory, request the parts needed for a visit, and record what was used. The job keeps those parts connected to the work and the invoice.
See the work across the operation.
Review service activity, engineer performance, revenue and parts consumption. Job records give the wider operation a basis for its next decision.
Engineering the handoffs
The interface joins it.
The system keeps it.
The job, its stages and its invoice have their own responsibilities. Connecting them gives the team a clearer path through the work.
Build around the relationships.
A React web interface works with an Express API and MongoDB records. Jobs link customers, devices, service types and people; invoice records keep the job and customer relationship.
Give progress a shape.
Brand and company settings can define the service stages. Each stage keeps its assignment, schedule and completion history. Completing a stage can pass the job into the next stage.
Keep the finish deliberate.
A finished stage and a finalized job are separate decisions. The job retains a finalization step; creating an invoice from it requires completed status and checks for an existing invoice.
Match access to the work.
Director, staff and engineer roles have module permissions. Ticket actions check the company and assignment; an engineer’s ordinary view follows their own jobs, with additional access controlled by explicit grants.
VSBLTYTECH
Thoughtfully made by VSBLTY Tech.
Meet the makersThe people behind the product
Software shaped
around the work.
VSBLTY Tech is ServiceGuru’s parent company. We build products around the connections that make them useful: how a request moves, how its context is carried, and how the work is followed through.
ServiceGuru brings that thinking into field service. The office, the technician and the customer record are parts of the same job, with deliberate handoffs between them.
Explore the product familyA few useful answers
The details
around the job.
What does ServiceGuru connect?
ServiceGuru connects job schedules, technician assignments, customer and equipment records, service history and invoice workflows in one field-service workspace.
Who is the workspace designed around?
Office staff planning and coordinating jobs, technicians carrying out assignments, and directors following the wider operation. The available modules and actions depend on each person’s role and granted access.
What travels with a technician’s job?
The assignment can include the customer, service address, equipment, complaint, service type and scheduled time. The technician’s job view groups assigned work for today, upcoming work and completed tickets.
Can a job have more than one stage?
Yes. Brand or company settings can define service stages, each with its own assignment, schedule and completion history. Finishing one stage can move the job into the next, with a new assignment and schedule.
Does finishing a stage close the whole job?
Stage completion and job finalization are separate. The work record keeps the stage progress and work performed; the job has an explicit finalization action before it is treated as completed for invoicing.
How does invoicing follow the work?
An invoice generated from a job requires completed status and checks whether an invoice already exists. Its line items can draw on recorded parts, labour and additional charges. Payments are then recorded against the invoice, with partial and paid status tracked.
Is ServiceGuru part of VSBLTY Tech?
Yes. VSBLTY Tech is ServiceGuru’s parent company. ServiceGuru keeps its own product identity and applies the family’s connected approach to field-service operations.
Where can I open ServiceGuru?
Open the ServiceGuru web app (opens in a new tab), or use its sign-in page (opens in a new tab) if you already have an account. Available modules and actions depend on the workspace and each person’s access.
Every handoff carries the job forward
Keep the office
and the field connected.
From the first request to the final record,
carry the work through one connected workspace.