Skip to content
VSBLTY TECH Open ServiceGuru (opens in a new tab)
ServiceGuru A product by VSBLTY Tech

Start with the work you need

Your work.
One connected workspace.

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.

Start with what you need.
Connect more as you grow.

Keep the workspace focused on billing, people or stock. Bring modules together when the business needs a wider view.

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.

Your HR and payslip workspace

Employees · attendance · leave · payroll

Manage employee records, the working day and time off. Calculate monthly salaries and produce payslips without running a service desk.

Your inventory workspace

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.

Your sales CRM

Leads · follow-ups · reviews · pipeline

Keep enquiries, owners and next conversations together. Shape pipeline stages and review rules without starting from a repair operation.

Your team communication hub

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.

Your dispatch workspace

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 connected business workspace

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

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.

OFFICE

Plan the work.

Create the job, keep the customer context nearby, and assign the people and time it needs.

FIELD

Carry the context.

See assigned work, the service address, equipment and complaint. Record progress and the work performed.

OPERATIONS

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

  1. 01 / REQUEST

    Know the job.

    Link the customer, equipment, complaint and service address.

  2. 02 / ASSIGN

    Give it an owner.

    Connect the technician, scheduled time and current stage.

  3. 03 / COMPLETE

    Keep what happened.

    Record stage progress and work done. Finalize the job explicitly.

  4. 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.

PARTS & STOCK

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.

ACTIVITY & REPORTS

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.

CONNECTED RECORDS

Build around the relationships.

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.

WORKFLOW STAGES

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.

EXPLICIT COMPLETION

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.

PRACTICAL ACCESS

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 makers

The 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 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 family

A few useful answers

The details
around the workspace.

What does ServiceGuru connect?

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.

Who is the workspace designed around?

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.

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?

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.

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 modular business workspaces and 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.

A workspace shaped around your business

Bring the work
into your workspace.

Start with the modules you need,
and connect more of the work as you grow.