How to Use ServiceDesk: A Practical Setup Guide for Service Businesses

ServiceDesk gives you a lot of flexibility in how you run your business, but that flexibility works best when the foundation is set up correctly.

You don't need to configure every setting before you book your first job. You should, however, take a little time to decide how you want ServiceDesk to organize your customers, properties, jobs, scheduling, estimates, invoices, and reporting.

This guide walks through the setup we recommend for most service businesses and explains how to keep your workspace useful as your company grows.

1. Start with the structure of your business

Before adding a lot of customers or creating automations, start with the basic structure of your workspace.

A good order is:

1. Business Units

2. Job Types

3. Job and Prospect stages

4. Fields

5. Team roles and permissions

6. Customers and Properties

7. Scheduling and Dispatch

8. Estimates and Invoices

9. Automations

10. Integrations and reporting

You don't have to finish all of this in one sitting. The important part is setting up the categories that will affect your data before you start creating hundreds of records.

2. Set up Business Units without overcomplicating them

Business Units should represent meaningful parts of your operation.

For a company that offers several trades, the setup might be simple:

Business Units

• HVAC

• Plumbing

• Electrical

Then your Job Types explain what kind of work is actually being performed.

For a company that only provides one service, you don't need to invent several Business Units just because the field exists.

A window cleaning company could simply use:

Business Unit

• Window Cleaning

A house cleaning company could use:

Business Unit

• House Cleaning

A lawn company could use:

Business Unit

• Lawn Care

As the company grows, you can separate Business Units when there is a real operational reason to do it.

For example, a lawn care company that later adds landscaping and snow removal might eventually use:

• Lawn Care

• Landscaping

• Snow Removal

The best rule is simple: Business Units should tell you what part of the business generated the work.

Don't turn every individual service into a Business Unit.

That is what Job Types are for.

3. Use Job Types to describe the work being performed

Job Types are one of the most important fields to configure early because they can help organize jobs, estimates, invoices, reporting, and future automations.

ServiceDesk starts with general options such as Repair, Installation, Maintenance, Inspection, Estimate Visit, Warranty, and Emergency Call.

Those are useful defaults, but we recommend adjusting them to match the work your company actually performs.

HVAC

A typical HVAC company might use:

• No Cooling

• No Heat

• HVAC Repair

• AC Maintenance

• Furnace Maintenance

• AC Installation

• Furnace Installation

• Full System Replacement

• Indoor Air Quality

• Thermostat

• Estimate Visit

• Warranty

You do not necessarily need separate Job Types for every possible repair.

For example, creating Job Types like "Bad Capacitor," "Contactor Replacement," and "Low Refrigerant" usually becomes too specific. Those details belong in the job itself.

Plumbing

Possible Job Types:

• Plumbing Repair

• Drain Cleaning

• Leak Repair

• Toilet Repair

• Faucet Repair

• Water Heater Repair

• Water Heater Installation

• Sewer Service

• Sump Pump

• Fixture Installation

• Estimate Visit

• Emergency Plumbing

Electrical

Possible Job Types:

• Electrical Repair

• Troubleshooting

• Outlet or Switch

• Lighting

• Panel Upgrade

• Generator

• EV Charger

• Ceiling Fan

• New Circuit

• Electrical Inspection

• Estimate Visit

• Emergency Electrical

Window Cleaning

Possible Job Types:

• Exterior Window Cleaning

• Interior and Exterior

• Commercial Window Cleaning

• Recurring Window Cleaning

• Screen Cleaning

• Track Cleaning

• Hard Water Removal

• Estimate Visit

Lawn Care

Possible Job Types:

• Lawn Mowing

• Spring Cleanup

• Fall Cleanup

• Fertilization

• Weed Control

• Aeration

• Mulch Installation

• Shrub Trimming

• Yard Cleanup

• Estimate Visit

If the company also performs landscaping, you may eventually create a separate Landscaping Business Unit instead of putting every landscaping service underneath Lawn Care.

House Cleaning

Possible Job Types:

• Recurring Cleaning

• Standard Cleaning

• Deep Cleaning

• Move-In Cleaning

• Move-Out Cleaning

• One-Time Cleaning

• Post-Construction Cleaning

• Office Cleaning

• Estimate Visit

The goal is to make your Job Types specific enough to be useful without creating a list that employees have to scroll through every time they book a job.

4. Customize your fields around information you actually use

ServiceDesk lets you customize the information stored throughout your workspace.

Core fields can be renamed, reordered, hidden, and restored. You can also create your own custom fields.

Custom fields are available across areas including:

• Prospects

• Customers

• Properties

• Jobs

• Estimates

• Invoices

• Dispatch

• Tasks

Custom field options include text, long text, phone numbers, email addresses, numbers, currency, dates, dropdowns, multi-select fields, checkboxes, addresses, URLs, file fields, and fields that link records together.

You can also create dependent dropdowns.

For example:

System Type

• Furnace

• Air Conditioner

• Heat Pump

If Furnace is selected, a second dropdown could contain furnace-specific options.

The biggest mistake with custom fields is creating too many of them.

Before adding a field, ask:

Will someone actually use this information later?

A field usually makes sense if it will help with:

• Dispatching

• Preparing for the job

• Customer communication

• Estimates

• Reporting

• Automation

• Future service

If the answer is no, it may be better as a note instead.

5. Good field ideas by trade

Different trades should collect different information.

HVAC

Useful Property or Job fields might include:

• System Type

• Fuel Type

• Equipment Age

• Manufacturer

• Model Number

• Filter Size

• Maintenance Plan

• Number of Systems

Plumbing

Possible fields:

• Water Heater Type

• Water Heater Age

• Sewer or Septic

• Shutoff Location

• Recurring Drain Issue

• Preferred Fixture Brand

Electrical

Possible fields:

• Panel Brand

• Panel Amperage

• Generator Installed

• EV Charger Installed

• Electrical Service Type

Window Cleaning

Possible fields:

• Number of Windows

• Number of Stories

• Screens Included

• Interior Access Required

• Hard Water Present

• Recurring Frequency

Lawn Care

Possible fields:

• Lot Size

• Lawn Size

• Gate Access

• Irrigation System

• Pets on Property

• Service Frequency

House Cleaning

Possible fields:

• Bedrooms

• Bathrooms

• Square Footage

• Pets

• Entry Instructions

• Cleaning Frequency

• Supplies Provided By

• Preferred Cleaning Team

You do not need all of these. Pick the ones that would actually change how your team handles the job.

6. Understand Customers and Properties

ServiceDesk separates the person you work with from the place where the work happens.

That distinction becomes especially useful for service businesses.

A Customer is the person or contact.

A Property is the service location.

For a homeowner with one house, the relationship is simple.

Customer: Sarah Johnson
Property: 123 Main Street

But this structure becomes much more valuable when one customer has multiple service locations.

For example:

Customer: ABC Property Management

Properties:

• 100 Oak Street

• 225 Market Avenue

• 810 Lake Drive

Instead of creating the same customer three times, keep one customer and attach the appropriate properties.

This gives you cleaner service history and makes it easier to understand exactly where previous work was completed.

7. Use Prospects before creating Customers when appropriate

Prospects are useful when someone has contacted the business but has not become a customer yet.

A Prospect can contain information such as:

• Name

• Phone

• Email

• Service address

• Stage

• Lead source

• Service type

• Urgency

• Request details

The default Prospect stages include:

• New

• Contacted

• Qualified

• Unqualified

• Converted

These stages can be adjusted for your workspace.

One thing to keep in mind is that Converted has a special purpose in ServiceDesk because the Prospect conversion process uses it.

A company with a more involved sales process might use stages such as:

• New

• Attempting Contact

• Contacted

• Estimate Scheduled

• Estimate Sent

• Follow-Up

• Won

• Lost

For a business that mostly books customers immediately over the phone, you may not need an elaborate Prospect process.

Don't add steps just because you can.

8. Keep Job Statuses easy for the team to understand

Your Job Status should answer a simple question:

Where is this job in its lifecycle?

A practical setup might include:

• Scheduled

• Dispatched

• Arrived

• In Progress

• Completed

• Canceled

Your exact workflow may be different.

ServiceDesk uses the Job Status as an important part of the job lifecycle, and your Dispatch workflow works alongside it.

Statuses should be clear enough that an owner, dispatcher, CSR, and technician all understand what they mean without needing a manual.

Avoid creating several statuses that mean almost the same thing.

For example:

• Finished

• Completed

• Work Complete

• Job Done

should probably be one status.

9. Build Jobs around the customer and property

When creating a Job, connect it to the correct Customer and Property whenever possible.

Then select the appropriate:

• Business Unit

• Job Type

• Priority

• Assigned Technician

• Description

• Internal Notes

• Attachments

ServiceDesk can use the Business Unit and Job Type as part of the way the job is identified, which is another reason to configure those fields before your team begins creating large numbers of jobs.

Keeping this information consistent also makes future reporting much more useful.

If half of your AC repairs are labeled "HVAC Repair" and the other half are called "AC Fix," your reporting will eventually become harder to trust.

Consistency is more valuable than creating dozens of choices.

10. Use Dispatch as the operational schedule

The Dispatch Board is where scheduled work can be organized across technicians and days.

Dispatches can be moved between team members and dates, allowing a dispatcher to adjust the schedule without rebuilding the job.

ServiceDesk also supports technician assignment, arrival windows, service locations, notes, dispatch statuses, and workload information.

A simple best practice is to keep your Dispatch Board focused on work that someone actually needs to perform.

Your technician should be able to look at their schedule and immediately understand:

• Where they are going

• What job they are doing

• When they are expected

• What they need to know before arriving

Avoid burying critical instructions inside unrelated notes.

If something affects how the technician performs the job, consider giving it a dedicated field.

11. Use arrival windows instead of unrealistic exact times

Service businesses don't always know exactly how long the previous appointment will take.

Instead of promising every customer an exact arrival time, many businesses operate more successfully with arrival windows.

For example:

• 8:00 AM to 10:00 AM

• 10:00 AM to 12:00 PM

• 12:00 PM to 2:00 PM

• 2:00 PM to 4:00 PM

Your exact windows should match how your company operates.

ServiceDesk supports scheduling windows so your team can give customers realistic expectations while still keeping the schedule organized.

12. Use Estimates and Invoices as part of the same workflow

Estimates and Invoices should not feel disconnected from the rest of the customer record.

When possible, keep the Business Unit and Job Type consistent between the Job, Estimate, and Invoice.

That gives you better context when reviewing the customer's history later.

For example:

Business Unit: HVAC
Job Type: AC Installation

should generally remain consistent as the work moves from estimate to job to invoice.

An estimate can include the scope of work, pricing, tax, expiration date, internal notes, attachments, and other fields you choose to configure.

Invoices can track the amount due, due date, status, tax, notes, attachments, and payment information.

The cleaner this information is at the beginning, the easier accounting and reporting become later.

13. Configure roles before adding a large team

ServiceDesk supports detailed roles and permissions.

Instead of giving everyone administrator access, build roles around what each person actually does.

Common roles might include:

Owner / Administrator

Full workspace access.

Dispatcher or CSR

Typically needs access to:

• Customers

• Properties

• Prospects

• Jobs

• Dispatch

• Calendar

• Communications

They may need to create and edit Jobs but probably don't need access to every financial or workspace setting.

Technician

Typically needs:

• Assigned Jobs

• Dispatch

• Job Status updates

• Photos and attachments

• Job notes

• Time tracking

They may not need access to company-wide financial reporting.

Office Manager

May need broader access to:

• Customers

• Jobs

• Estimates

• Invoices

• Dispatch

• Timecards

• Reporting

Accounting

May need:

• Invoices

• Payments

• Finance

• Reports

• Accounting integrations

ServiceDesk lets you control both whether a module is visible and whether specific actions are allowed.

Configure these before inviting a large team. It is much easier than fixing permissions after everyone already has access.

14. Set up time tracking based on how your company actually pays employees

ServiceDesk supports employee clock in and clock out, breaks, timecards, and job labor timers.

These solve different problems.

Clock In / Clock Out tracks the employee's workday.

Job Labor Time tracks how much labor was spent on a specific job.

A technician might be clocked into work for eight hours while only having six hours of actual job labor.

Keeping those separate gives you much better information.

You can also configure overtime rules and determine which roles can view, edit, approve, lock, or export timecards.

15. Start automating after your basic workflow is clean

Automations are much more useful when your underlying process is consistent.

If your team isn't using Job Types or statuses consistently, automating around those values will only make the inconsistency happen faster.

ServiceDesk can build automations from plain-English instructions using Nova.

For example:

When an invoice becomes overdue, create a task for the office manager to follow up.

Or:

When a new prospect is created, create a follow-up task.

ServiceDesk validates automations before allowing them to go live. If an automation contains something the system cannot actually perform, it will not activate it as though it works.

Nova-generated automations may also remain in Draft until they are reviewed and activated.

That gives you the opportunity to confirm what the automation will do before it starts changing records or contacting people.

16. Good starter automations for service businesses

You do not need twenty automations on your first day.

Start with a few that solve repetitive problems.

Useful for almost every trade

New Prospect Follow-Up

When a Prospect is created, create a follow-up task or notify the team.

Useful for HVAC, plumbing, electrical, cleaning, lawn care, and window cleaning.

Completed Job Follow-Up

When a Job reaches your completed status, create a follow-up task for anything your office needs to handle next.

Overdue Invoice

When an Invoice becomes overdue, notify the office or create a collection follow-up task.

Estimate Follow-Up

When an Estimate is created, create a future follow-up task so it doesn't get forgotten.

New Customer Notification

When a Customer is created, notify the appropriate team member or create the next task in your onboarding process.

17. HVAC automation ideas

HVAC companies could consider automations such as:

Maintenance Follow-Up

After a maintenance-related Job is completed, create a future task for the office to contact the customer when the next maintenance visit should be scheduled.

Estimate Follow-Up

When an Estimate is created for an installation or replacement, create a sales follow-up task.

Emergency Lead Alert

When a new Prospect comes in with emergency urgency, notify the team immediately.

You can continue to add more advanced workflows once your basic process is working consistently.

18. Plumbing automation ideas

Possible plumbing automations:

Emergency Prospect Notification

Notify the office when an emergency plumbing Prospect is created.

Water Heater Estimate Follow-Up

Create a follow-up task when a water heater Estimate is created.

Completed Job Review Task

After a plumbing Job is completed, create a task for someone to review the Job for invoicing or follow-up.

19. Electrical automation ideas

Possible electrical automations:

Estimate Follow-Up

Create a follow-up task after an Estimate for a panel upgrade, generator, or EV charger.

New Prospect Assignment

When a new Prospect is created, assign a follow-up task to the appropriate employee.

Completed Installation Follow-Up

After an installation Job is completed, create a task for any remaining documentation or customer follow-up.

20. Window cleaning automation ideas

Window cleaning businesses often rely heavily on recurring customers.

Possible automations include:

Recurring Service Follow-Up

When a recurring cleaning Job is completed, create a future scheduling task.

Estimate Follow-Up

Create a follow-up task after a larger residential or commercial Estimate is created.

New Lead Notification

Notify the office when a new Prospect enters ServiceDesk.

21. Lawn care automation ideas

Lawn companies can use automation to help manage seasonal work.

Possible examples:

Seasonal Follow-Up

After a fall cleanup or seasonal service is completed, create a future task for the next relevant service.

Estimate Follow-Up

Create a follow-up task when a landscaping or larger lawn-care Estimate is created.

New Customer Setup

When a new Customer is created, create a task to confirm service frequency, access information, or other details your company requires.

22. House cleaning automation ideas

Cleaning companies can use automations to reduce the administrative work around recurring service.

Possible examples:

Recurring Cleaning Follow-Up

After a cleaning Job is completed, create the appropriate next scheduling task.

New Customer Setup

When a Customer is created, create a task to confirm access instructions, pets, service frequency, or other information.

Overdue Invoice Follow-Up

Notify the office when a cleaning Invoice becomes overdue.

23. Use Nova for more than answering questions

Nova can work with ServiceDesk records instead of functioning only as a chatbot.

Depending on your permissions and the action being requested, Nova can help create or update records and can help build automations from normal language.

The best prompts are specific.

Instead of:

Make an automation for customers.

Try:

When a new Prospect is created, create a high-priority task for the office to call them.

Or:

Show me completed Jobs that still need follow-up.

The clearer you are about the trigger, condition, and result you want, the better Nova can understand the workflow.

24. Connect integrations that affect your daily workflow early

If your company plans to use an integration every day, connect it before you build processes around it.

For example, if your team relies heavily on Google Calendar, set up the calendar connection before everyone starts maintaining separate schedules.

If you're accepting payments through ServiceDesk, configure your payment provider before sending live invoices.

If you're planning to use accounting synchronization, make sure your accounting setup matches the way you want invoices and payments recorded before relying heavily on the integration.

Avoid creating two separate versions of the same workflow in different systems unless there is a reason for it.

The more ServiceDesk becomes the central record of what happened with a customer, the easier it becomes for your team to understand the whole customer lifecycle.

25. Build reports after your data has structure

Reporting becomes valuable when the fields behind it are consistent.

ServiceDesk reports can use saved filters and charts, and supported records can link back to the underlying record so you can move from a report into the customer, Job, Estimate, Invoice, or other related information.

That makes your setup decisions important.

If you want to eventually answer questions such as:

• Which Job Types generate the most revenue?

• How many HVAC Estimates turn into work?

• How much work does each Business Unit produce?

• How many open Invoices do we have?

• Which services are growing?

then start collecting those values consistently now.

Good reporting starts when the record is created, not when the report is built.

26. Common setup mistakes to avoid

Creating too many Business Units

If you have one trade, you may only need one Business Unit.

Don't create a Business Unit for every individual service.

Creating too many Job Types

Your technician doesn't need to choose between fifty nearly identical Job Types.

Use Job Types for meaningful categories of work.

Use job descriptions, notes, and custom fields for the details.

Making every field required

A required field should be information that your team genuinely cannot proceed without.

If employees begin entering random information just to get past required fields, the field isn't helping anymore.

Giving everyone administrator access

Permissions exist for a reason.

Give employees access to the parts of ServiceDesk they actually need.

Using Customers and Properties interchangeably

Keep the person and service location separate.

It will save you a lot of cleanup later.

Automating a process before the process makes sense

Run the workflow manually first.

Once you know exactly how your team should handle it, automate the repetitive parts.

Ignoring naming consistency

"AC Repair," "Air Conditioning Repair," and "Cooling Repair" might all mean the same thing.

Choose one naming convention and use it consistently.

Adding fields without a purpose

Every field creates another decision for the person entering the record.

If you're never going to search, report, dispatch, automate, or make a decision from that information, consider leaving it out.

27. You don't need a perfect setup on day one

A new ServiceDesk workspace should be organized, but it does not need to be complicated.

Start with your real operation.

Set up the services you actually sell, the statuses your team actually uses, and the information your employees actually need.

Then run the business.

As you notice repetitive work, missing information, or reporting questions you can't answer, adjust the workspace.

ServiceDesk is built so your setup can grow with the business instead of forcing a small company into a complicated enterprise workflow from the beginning.