Your invoicing desk
Invoices · payments · customers
Bill customers directly, add your own line items and due dates, and record payments against the balance. A service job does not need to happen first.
A product by VSBLTY Tech
Start with the work you need
Bring invoicing, people, stock, sales and team communication into your workspace—or connect them with field service. Choose the modules that fit the work.
Different work. The same product.
Keep the workspace focused on billing, people or stock. Bring modules together when the business needs a wider view.
Invoices · payments · customers
Bill customers directly, add your own line items and due dates, and record payments against the balance. A service job does not need to happen first.
Employees · attendance · leave · payroll
Manage employee records, the working day and time off. Calculate monthly salaries and produce payslips without running a service desk.
Catalogue · stock history · bundle rules
Keep track of what you have and how quantities move. Issue and return stock with employee records; connect job-linked parts when the operation needs them.
Leads · follow-ups · reviews · pipeline
Keep enquiries, owners and next conversations together. Shape pipeline stages and review rules without starting from a repair operation.
Chats · shared files · calls · coordination
Bring direct and group conversations, shared files, one-to-one calls and colleague coordination into the team's working day.
Jobs · visits · engineers · customer records
Plan visits and engineer handoffs with customer, equipment and job context. Add parts and billing when they fit the operation.
Your mix of sales, jobs, stock, billing and people
Combine the modules your business needs. Keep one workflow in focus or bring more of the operation together, with access shaped around each person's work.
Available modules and access depend on your plan, organization setup and assigned permissions.
When the work reaches the field
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.
Create the job, keep the customer context nearby, and assign the people and time it needs.
See assigned work, the service address, equipment and complaint. Record progress and the work performed.
Keep stages, parts and completion visible, then connect finished work to an invoice and its payment record.
From request to record
A schedule gives the work a place in the day. Assignment gives it an owner. The record carries what happened into the next step.
What needs attention?
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
Link the customer, equipment, complaint and service address.
Connect the technician, scheduled time and current stage.
Record stage progress and work done. Finalize the job explicitly.
Create the invoice from completed work, then record payments against it.
The context stays connected
The work around a customer includes more than a phone number. Addresses, equipment, service visits and invoices each belong to the same operational story.
Contact details, service addresses and notes give each job its starting context.
Linked devices carry their type, brand, model and serial details into the service record.
Related tickets show previous and current work, their status and the people assigned.
The job and customer stay linked to line items, the amount due and recorded payments.
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.
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 job, its stages and its invoice have their own responsibilities. Connecting them gives the team a clearer path through the work.
A React web interface works with an Express API and MongoDB records. Jobs link customers, devices, service types and people; invoices retain customer context; job-generated invoices also retain the job link.
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.
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.
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.
Thoughtfully made by VSBLTY Tech.
Meet the makersThe people behind the product
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 focused business workspaces. Start with invoices or people operations, or connect the office and the field through shared job records and deliberate handoffs.
Explore the product familyA few useful answers
Start with invoicing, HR and payslips, inventory, sales CRM or team communication. Field-service workspaces connect jobs, visits, engineers and customer records. Available modules and access depend on your plan, organization setup and assigned permissions.
The people doing the work: billing teams, people administrators, sales and stock teams, office staff and field engineers. The available modules and actions depend on each person's role and granted access.
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.
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.
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.
You can create a direct invoice for a customer without a service job, using your own line items and due dates. 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.
Yes. VSBLTY Tech is ServiceGuru’s parent company. ServiceGuru keeps its own product identity and applies the family’s connected approach to modular business workspaces and field-service operations.
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.
A workspace shaped around your business
Start with the modules you need,
and connect more of the work as you grow.