gestao

Field Service Job Scheduling and Dispatch Software

Learn how to schedule and dispatch field service jobs, assign technicians, track progress, notify customers, and connect completed work to invoices and reviews.

Aisha Benevente

Write

27 min de leitura

Schedule and Dispatch Field Service Jobs Without Spreadsheets or Endless Text Messages

Scheduling one service job is simple.

Managing several technicians, addresses, customers, time windows, job statuses, and last-minute changes is where the confusion begins.

A typical field service company may need to coordinate:

  • new service requests;
  • estimate visits;
  • approved work;
  • technicians;
  • service addresses;
  • appointment windows;
  • travel time;
  • customer access instructions;
  • job progress;
  • cancellations;
  • rescheduling;
  • invoices;
  • review requests.

Without a central scheduling system, this information is often spread across:

  • text messages;
  • paper calendars;
  • spreadsheets;
  • personal phones;
  • Google Calendar;
  • WhatsApp groups;
  • email;
  • handwritten notes.

The owner may know that a technician has three jobs tomorrow but still need to ask:

  • Which customer is first?
  • What is the correct address?
  • What work was approved?
  • Has the customer confirmed?
  • Is the technician already driving?
  • Was the previous job completed?
  • Who needs to be invoiced?

DunaHub Job Scheduling gives contractors and local service businesses one place to create, assign, dispatch, track, and complete field service jobs.

The workflow becomes:

Lead → Proposal → Approval → Scheduled Job → On the Way → In Progress → Completed

Instead of sending job details through disconnected messages, the company keeps the customer, approved service, address, technician, schedule, and status connected.

What is field service scheduling?

Field service scheduling is the process of deciding:

  • which work will be completed;
  • when it will happen;
  • where it will happen;
  • which technician will perform it;
  • what the customer should expect.

Dispatching is the process of sending the correct technician to the correct job with the information needed to complete it.

A complete field service workflow includes more than putting a customer’s name on a calendar.

The company also needs to manage:

  • job details;
  • customer history;
  • assigned technician;
  • job status;
  • arrival communication;
  • changes;
  • completion;
  • billing;
  • follow-up.

When these steps are connected, the office can see what is happening without calling every technician individually.

Why do service businesses struggle with job scheduling?

Many contractors begin with a basic calendar.

That may work when the owner performs every job.

As the company grows, scheduling becomes more complicated.

The business may add:

  • an office manager;
  • an estimator;
  • several technicians;
  • different service areas;
  • recurring customers;
  • commercial accounts;
  • longer projects;
  • urgent calls.

The same calendar now needs to answer several operational questions.

Which technician is available?

A job should not be assigned to someone who is:

  • already booked;
  • too far from the property;
  • unavailable;
  • missing the required experience;
  • waiting for materials;
  • working on a longer project.

What did the customer approve?

The technician needs more than the address.

They may need:

  • approved scope;
  • customer notes;
  • service value;
  • access information;
  • special instructions;
  • property details;
  • contact information.

What is happening right now?

The office should know whether a job is:

  • scheduled;
  • on the way;
  • in progress;
  • completed;
  • cancelled.

Has the customer been updated?

Customers often call because they do not know:

  • whether the appointment is confirmed;
  • when the technician is coming;
  • whether the technician has left;
  • whether the job needs to be rescheduled.

A connected job workflow helps answer these questions before they become customer complaints.

What is the difference between a lead and a job?

A lead represents a sales opportunity.

A job represents work that will be performed.

Lead example

A homeowner requests an estimate for pressure washing.

The lead record may include:

  • name;
  • phone number;
  • email;
  • address;
  • requested service;
  • conversation history;
  • pipeline stage;
  • proposal.

Job example

After the homeowner approves, the company creates a job containing:

  • service date;
  • appointment time;
  • property address;
  • approved service;
  • assigned technician;
  • price;
  • operational notes;
  • status.

The customer remains the same, but the purpose of the record changes.

The lead helps the company win the work.

The job helps the company deliver it.

With the DunaHub CRM Pipeline, the sales opportunity remains connected to the scheduled service.

What information can be included in a DunaHub Job?

A job can contain the main information the office and technician need, including:

  • customer;
  • lead;
  • date;
  • time;
  • address;
  • service type;
  • value;
  • assigned technician;
  • administrative notes;
  • current status.

The address can be populated from the connected lead information.

This reduces repeated data entry and the risk of sending the technician to an incomplete or incorrect location.

A job may look like this:

Customer: Sarah Miller Service: Driveway and patio pressure washing Date: July 9, 2026 Time: 9:00 AM Address: 125 Lake Avenue Assigned technician: Daniel Value: $425 Notes: Side gate will be unlocked. Customer requested that the pool area remain closed. Status: Scheduled

The technician sees more than a customer name.

They see the context required for the appointment.

How do the four scheduling views help?

DunaHub’s Jobs module currently documents four ways to review scheduled work:

  • table;
  • calendar;
  • list;
  • timeline.

Each view supports a different management need.

Table view: review structured job information

The table view is useful when the office needs to compare several jobs and their main details.

It can support tasks such as:

  • reviewing upcoming work;
  • checking assigned technicians;
  • finding incomplete records;
  • comparing service values;
  • confirming addresses;
  • identifying jobs that need updates.

A structured table is helpful when the office manager is preparing the next workday or reviewing a larger number of appointments.

Calendar view: understand the schedule visually

The calendar helps the company see how work is distributed across dates.

It can be used to identify:

  • busy days;
  • open days;
  • scheduling conflicts;
  • overloaded periods;
  • gaps between appointments;
  • future capacity.

A visual calendar gives the dispatcher a better understanding of the workload than a disconnected list of text messages.

List view: focus on the jobs that need attention

A list is useful when the team wants a straightforward sequence of appointments.

The office can review jobs in order and check:

  • customer;
  • time;
  • technician;
  • status;
  • service.

Technicians may also find a simple ordered list useful when reviewing their assigned work from a mobile browser.

Timeline view: understand work across time

The timeline view helps the company understand how jobs are positioned over a period.

This may be useful for:

  • longer appointments;
  • work that spans several hours;
  • understanding schedule overlap;
  • reviewing technician allocation;
  • visualizing the sequence of service activity.

The best view depends on the task.

A dispatcher may move between views throughout the day rather than relying on only one format.

How should a company plan by day, week, and month?

Even when the system offers several display formats, the management routine should operate on three planning levels.

Daily planning

Daily planning focuses on execution.

Review:

  • today’s jobs;
  • assigned technicians;
  • first appointment times;
  • incomplete addresses;
  • access instructions;
  • customer phone numbers;
  • materials or equipment;
  • jobs carried over from yesterday.

The daily question is:

Can every technician complete today’s schedule with the information provided?

Weekly planning

Weekly planning focuses on capacity and balance.

Review:

  • technician workload;
  • open appointment windows;
  • geographic distribution;
  • commercial commitments;
  • recurring work;
  • longer projects;
  • weather-dependent jobs;
  • jobs waiting for confirmation.

The weekly question is:

Is the work distributed realistically across the team?

Monthly planning

Monthly planning focuses on future demand.

Review:

  • total booked work;
  • open capacity;
  • recurring jobs;
  • seasonality;
  • revenue expected from scheduled services;
  • staffing needs;
  • upcoming maintenance;
  • commercial account commitments.

The monthly question is:

Do we have enough work scheduled, and can the team deliver it?

How do you create a field service job in DunaHub?

The basic process is:

  1. Open Jobs;
  2. Select New Job;
  3. Choose the customer or lead;
  4. Add the date;
  5. Add the appointment time;
  6. Confirm the address;
  7. Select the service;
  8. Add the value;
  9. Assign the technician;
  10. Add relevant notes;
  11. Save.

The job appears in the available scheduling views.

Before saving, verify that the record answers:

  • Who is the customer?
  • Where is the service?
  • What work is expected?
  • When should it happen?
  • Who is responsible?
  • What does the technician need to know?

How are jobs linked to CRM leads?

Each job can remain connected to the original lead.

That connection gives the team access to the broader customer history.

Depending on the records available, the company can review:

  • initial inquiry;
  • messages;
  • notes;
  • proposal;
  • approved value;
  • previous jobs;
  • invoices;
  • customer details.

This helps prevent a common field-service problem:

The salesperson knows what was promised, but the technician does not.

When the job remains connected to the lead and proposal, the approved information is easier to preserve.

How does a proposal become a job?

After a customer approves a DunaHub Visual Proposal, the company can convert it into a job.

The new job can use information already connected to the proposal.

This reduces the need to manually recreate:

  • customer;
  • services;
  • items;
  • value;
  • basic scope.

The office still needs to confirm:

  • date;
  • time;
  • address;
  • technician;
  • operational notes.

The workflow becomes:

  1. Customer requests service;
  2. Lead enters the pipeline;
  3. Proposal is prepared;
  4. Customer approves;
  5. Proposal converts into a job;
  6. Technician is assigned;
  7. Service is completed;
  8. Invoice is sent.

This connection reduces manual copying between sales and operations.

How should technicians be assigned?

Assigning a technician is not only about finding an empty time slot.

The dispatcher may also consider:

  • service area;
  • technician availability;
  • skills;
  • certifications;
  • equipment;
  • vehicle;
  • job duration;
  • previous customer relationship;
  • distance from earlier appointments;
  • job complexity.

For example, an electrical contractor may assign a panel-related job to a technician with the appropriate qualifications.

A landscaping business may assign a larger crew to an installation while one technician handles smaller maintenance visits.

A cleaning company may send the same team to a recurring customer because they already understand the property.

The job record should identify one clear responsible user.

Avoid sending one appointment to a group chat and assuming someone will claim it.

How can jobs be filtered and reviewed?

Dispatchers commonly need to narrow the schedule according to operational priorities.

A useful review routine includes checking work by:

  • current status;
  • assigned technician;
  • service date;
  • date range;
  • incomplete information;
  • upcoming appointments.

Even when the company changes views, the purpose is the same:

  • isolate the jobs that matter;
  • identify problems;
  • prepare the team;
  • update the customer.

Examples include:

Review by status

Find jobs that are still Scheduled after their expected start time.

Review by technician

Confirm each technician’s appointments before the workday begins.

Review by date range

Prepare the next day, week, or service period.

Review completed work

Confirm which jobs are ready for invoicing and review requests.

The schedule should be treated as an active operational tool, not a calendar that is created once and forgotten.

What is the DunaHub job-status workflow?

DunaHub uses a progressive job-status flow:

Scheduled → On the way → In progress → Completed

A job can also be marked:

Cancelled

Each status communicates a different operational reality.

Scheduled

The appointment has been created and assigned.

The office should confirm:

  • customer;
  • date;
  • time;
  • address;
  • technician;
  • service;
  • notes.

A Scheduled job is not necessarily underway.

On the way

The technician has departed for the property.

Changing the status to On the way can automatically send an SMS to the customer.

This keeps the customer informed without requiring the technician to write the same message manually.

In progress

The technician has arrived and begun the work.

This helps the office distinguish between:

  • a technician still driving;
  • a technician waiting for access;
  • a job actively being performed.

Completed

The service is administratively finished.

After completion, the company may need to:

  • confirm final items;
  • create or send the invoice;
  • record payment;
  • request a review;
  • schedule recurring work;
  • update the sales pipeline.

Marking a job Completed should mean the operational team has finished the defined workflow.

Cancelled

The appointment will not proceed.

The office should also record why it was cancelled.

Possible reasons include:

  • customer request;
  • weather;
  • technician availability;
  • access problem;
  • material delay;
  • scope change;
  • duplicate appointment.

A cancelled job may need to be:

  • rescheduled;
  • returned to the pipeline;
  • closed;
  • followed up later.

How does the automatic “On my way” SMS work?

When the technician or administrator changes the job status to On the way, DunaHub can send an automatic SMS to the customer.

The message informs the customer that the assigned professional has departed.

A simple example is:

Your technician is on the way to the service address.

This helps customers prepare by:

  • unlocking gates;
  • moving vehicles;
  • securing pets;
  • contacting building security;
  • making equipment accessible;
  • meeting the technician.

The feature reduces calls such as:

Is your technician still coming?

or:

When will someone arrive?

Does the “On my way” text guarantee an arrival time?

No.

“On the way” confirms that the technician has started traveling.

It does not necessarily guarantee:

  • an exact arrival minute;
  • traffic conditions;
  • travel delays;
  • parking availability;
  • building access;
  • road conditions.

Avoid writing:

We will arrive in exactly 10 minutes.

unless the company can support that promise.

A safer message is:

Your technician is on the way. Please make sure the service area is accessible.

Does the “On my way” SMS cost extra?

Each automatic “On my way” SMS uses one prepaid SMS credit.

The Jobs feature is included according to the selected plan, but carrier-delivered text messages have a usage cost.

The company should maintain enough SMS credits for:

  • arrival notifications;
  • missed-call text-back;
  • SMS follow-up;
  • customer reminders;
  • review requests.

The business can decide which messages are important enough to send by SMS.

Who should update job status?

The company should define one clear process.

Possible options include:

  • technician updates their own status;
  • dispatcher updates based on technician communication;
  • office manager confirms completion;
  • supervisor reviews certain jobs.

A practical process is:

Technician

Updates:

  • On the way;
  • In progress;
  • Completed.

Office

Handles:

  • creation;
  • assignment;
  • rescheduling;
  • cancellation;
  • invoicing follow-up.

The exact workflow depends on the company.

The important requirement is consistency.

When nobody is responsible, statuses quickly become outdated.

Can technicians use DunaHub from a phone?

DunaHub works through a responsive mobile browser.

A technician can access permitted information without needing a desktop computer.

They may use the mobile interface to:

  • review assigned jobs;
  • check addresses;
  • read notes;
  • update status;
  • open customer information.

DunaHub should not currently be described as a native iOS or Android field-service app unless an official app has been released.

It is a browser-based responsive system.

Does DunaHub include GPS tracking?

DunaHub should not be described as a live GPS fleet-tracking platform.

The status workflow tells the office what stage the technician selected.

It does not automatically prove the technician’s location.

Similarly, the system should not be presented as advanced route-optimization software.

A company needing:

  • live vehicle locations;
  • automated route sequencing;
  • fuel tracking;
  • fleet telematics;
  • geofencing;

may need a complementary fleet-management tool.

DunaHub focuses on connecting:

  • customer;
  • lead;
  • proposal;
  • schedule;
  • assigned technician;
  • job status;
  • invoice;
  • review.

How should a dispatcher prepare the next day?

A strong dispatch routine begins before the first appointment.

Step 1: Review every job

Confirm:

  • date;
  • time;
  • address;
  • technician;
  • service.

Step 2: Look for missing information

Identify jobs without:

  • complete address;
  • customer phone;
  • access instructions;
  • service details;
  • value;
  • assigned user.

Step 3: Check technician workload

Make sure the schedule is realistic.

Step 4: Confirm unusual appointments

Examples include:

  • commercial properties;
  • locked buildings;
  • long-distance travel;
  • large projects;
  • services requiring special equipment.

Step 5: Review weather-dependent work

Outdoor contractors may need to adjust:

  • pressure washing;
  • gutter services;
  • painting;
  • landscaping;
  • roofing-related inspections.

Step 6: Confirm customer communication

Make sure the customer knows the appointment date and expected window.

Step 7: Prepare possible changes

Identify who can cover a job when:

  • a technician becomes unavailable;
  • weather changes;
  • materials are delayed;
  • an earlier appointment runs long.

How should same-day dispatch be managed?

During the day, the dispatcher should monitor:

  • jobs still Scheduled;
  • technicians On the way;
  • work In progress;
  • completed appointments;
  • cancellations;
  • incoming urgent requests.

A same-day review may reveal:

  • a technician who forgot to change status;
  • a job that started late;
  • a customer who cannot provide access;
  • an appointment ready for reassignment;
  • space for an additional job.

The goal is not to monitor every movement.

The goal is to maintain enough visibility to support the team and customer.

How should rescheduling be handled?

A job may need to move because of:

  • weather;
  • illness;
  • equipment problems;
  • customer request;
  • access issues;
  • material delays;
  • an earlier job taking longer than expected.

A consistent rescheduling process should include:

  1. Inform the customer;
  2. Agree on a new date;
  3. Update the job;
  4. Confirm the assigned technician;
  5. Record the reason;
  6. Send the updated appointment information.

Avoid creating a second duplicate job while leaving the original active.

The central schedule should reflect the latest agreement.

How should cancellations be handled?

A cancellation should not simply disappear.

Record:

  • who cancelled;
  • why;
  • whether the job should be rescheduled;
  • whether a deposit or fee applies;
  • whether the lead returns to the pipeline;
  • whether the opportunity is lost.

Examples:

Temporary cancellation

The customer needs to wait until next month.

Move the sales opportunity into a future follow-up process.

Permanent cancellation

The customer hired another company.

Record the lost reason.

Operational cancellation

The contractor cannot complete the service.

Contact the customer, explain the situation, and define the next action.

Cancellation data can help the business improve scheduling and sales.

How does online booking connect to Jobs?

The DunaHub Online Booking page allows customers to select an available service and time.

A confirmed booking creates:

  • a lead;
  • a job.

This eliminates the need for the office to recreate the appointment manually.

Online booking works best for services with:

  • defined duration;
  • clear pricing or purpose;
  • predictable requirements;
  • controlled availability.

Examples include:

  • estimate visit;
  • consultation;
  • recurring cleaning;
  • maintenance visit;
  • inspection;
  • standard service package.

Complex work may use booking for the initial visit rather than the full project.

How do completed jobs connect to invoicing?

After the job is completed, the company can create a DunaHub Invoice.

The invoice can include:

  • customer;
  • line items;
  • quantities;
  • prices;
  • total;
  • payment status.

The workflow may be:

  1. Technician marks the job Completed;
  2. Office reviews the approved scope;
  3. Additional approved items are confirmed;
  4. Invoice is created;
  5. Customer receives the payment link;
  6. Payment is tracked.

This reduces the delay between completing the work and requesting payment.

How do completed jobs trigger review requests?

When the DunaHub Google Review Engine is enabled, marking a job Completed can begin the review-request process.

The documented delay is 30 minutes.

The customer can receive a request through an available channel such as:

  • email;
  • WhatsApp;
  • SMS.

The delay gives the company time to confirm that the job was closed correctly before asking for feedback.

A completed job can therefore trigger two important post-service actions:

  • invoice;
  • review request.

Example: pressure washing company

A homeowner approves a driveway-cleaning proposal.

  1. The proposal becomes a job;
  2. The office selects Thursday at 9:00 AM;
  3. A technician is assigned;
  4. The address and access notes are confirmed;
  5. On Thursday, the technician changes the status to On the way;
  6. The customer receives an SMS;
  7. The technician changes the status to In progress;
  8. The work is completed;
  9. Status changes to Completed;
  10. The invoice is sent;
  11. The Review Engine requests feedback.

The office can follow the entire process without searching through text messages.

Example: HVAC contractor

An HVAC company schedules six maintenance visits for one day.

The dispatcher:

  1. Reviews the schedule;
  2. Confirms each service address;
  3. Assigns jobs between two technicians;
  4. Checks the expected appointment windows;
  5. Adds equipment details to the notes;
  6. Monitors status throughout the day;
  7. Reassigns one afternoon job when a technician becomes unavailable;
  8. Reviews completed work for invoicing.

The schedule becomes an operational dashboard rather than a static appointment list.

Example: landscaping company

A landscaping company manages:

  • weekly maintenance;
  • one-time cleanups;
  • planting projects;
  • estimate visits.

Recurring maintenance jobs appear alongside project work.

The dispatcher can review future capacity and avoid assigning a large installation to a day already filled with maintenance stops.

Each crew sees its assigned work and property information.

Example: electrical contractor

A customer approves an EV charger installation.

  1. The approved proposal converts into a job;
  2. The office schedules the installation;
  3. A qualified electrician is assigned;
  4. The job includes the customer, address, charger information, and approved scope;
  5. The electrician updates the status;
  6. The customer receives an arrival text;
  7. The completed job moves to invoicing.

Technical permits, safety records, and electrical documentation remain in the appropriate professional systems.

Example: cleaning company

A residential cleaning company has three teams.

The office uses the schedule to:

  • assign homes;
  • balance daily workload;
  • record access instructions;
  • identify recurring clients;
  • monitor completed visits;
  • prepare invoices;
  • request reviews.

The calendar reduces the need to ask each team where they are and which property is next.

What should be included in job notes?

Notes should help the team complete the service.

Useful notes include:

  • gate code;
  • parking instructions;
  • contact person;
  • property access;
  • pets;
  • approved service details;
  • areas excluded;
  • equipment information;
  • special customer request;
  • commercial check-in procedure.

Avoid storing highly sensitive information that is unnecessary for the service.

Notes should be:

  • relevant;
  • clear;
  • professional;
  • current.

Do not use vague instructions such as:

Customer told Mike what to do.

Write:

Clean driveway and front walkway only. Do not clean rear patio. Customer will unlock the side gate.

Common field-service scheduling mistakes

Keeping jobs in several calendars

The company loses one source of truth.

Scheduling without assigning a technician

Everyone sees the job, but nobody owns it.

Sending only the address

The technician does not know what was approved.

Failing to update status

The office cannot distinguish between delayed, active, and completed work.

Marking jobs Completed too early

Invoices or review requests may be triggered before the work is truly finished.

Forgetting SMS credits

Arrival notifications may fail when no credits remain.

Creating duplicate jobs during rescheduling

The old appointment stays active.

Overloading one technician

An open time slot does not always mean the route or workload is realistic.

Ignoring travel and access

A job may require additional time for parking, security, elevators, or property access.

Using shared logins

The company cannot identify who changed the schedule or status.

Treating status as GPS

A selected status is an operational update, not automatic location verification.

Failing to review completed jobs

Finished work may remain uninvoiced.

A practical daily scheduling routine

Beginning of the day

  • Review today’s Jobs;
  • Confirm technician assignments;
  • Check addresses;
  • Review access notes;
  • Identify missing information;
  • Confirm weather-sensitive work.

During the day

  • Monitor status changes;
  • Respond to cancellations;
  • Reassign jobs when necessary;
  • communicate delays;
  • review new urgent requests.

End of the day

  • Confirm completed work;
  • identify jobs still In progress;
  • review cancellations;
  • prepare invoices;
  • review tomorrow’s schedule;
  • correct outdated statuses.

A short daily routine can prevent many larger operational problems.

How much does DunaHub Job Scheduling cost?

Current DunaHub Plans and Pricing use flat company pricing.

PlanMonthly priceJob capacity
Free$010 jobs per month
Starter$9.90Unlimited jobs
Pro$49Unlimited jobs

The automatic On my way SMS uses one SMS credit per send.

Free

Free may work for:

  • owner-operators;
  • independent contractors;
  • businesses testing job scheduling;
  • companies with a smaller monthly service volume.

Public bookings also count toward the Free job limit.

Unused monthly Jobs do not roll over.

Starter

Starter may fit:

  • small teams;
  • businesses with regular appointments;
  • companies requiring more than ten jobs per month;
  • teams with up to five users.

Pro

Pro may fit:

  • larger field teams;
  • companies needing unlimited users;
  • multiple sales pipelines;
  • multi-step automations;
  • eligible online payment workflows.

DunaHub does not charge a separate monthly fee for each technician within the user allowance of the plan.

What DunaHub Job Scheduling does not replace

DunaHub should not be presented as a replacement for every specialized field-service system.

It does not currently replace:

  • live GPS fleet tracking;
  • advanced route optimization;
  • vehicle telematics;
  • fuel monitoring;
  • complex inventory management;
  • payroll;
  • safety-management software;
  • trade-specific technical documentation;
  • advanced project management;
  • construction scheduling;
  • permit systems;
  • workforce time clocks.

Its primary purpose is to connect:

  • customer;
  • lead;
  • proposal;
  • date;
  • time;
  • address;
  • technician;
  • status;
  • invoice;
  • review.

For many small service businesses, that connected workflow solves the main scheduling and dispatch problem without unnecessary complexity.

Field-service scheduling checklist

  • Create one central job calendar;
  • Connect each job to a lead;
  • Confirm the service address;
  • Add the date and time;
  • Record the approved service;
  • Add the job value;
  • Assign a technician;
  • Add useful access notes;
  • Review jobs by date;
  • Review jobs by technician;
  • Review jobs by status;
  • Confirm the next day’s schedule;
  • Keep Scheduled jobs current;
  • Change status to On the way when departing;
  • Maintain SMS credits;
  • Change status to In progress after arrival;
  • Mark Completed only after finishing;
  • Record cancellations;
  • Reschedule without duplicates;
  • Review completed jobs for invoicing;
  • Enable review requests;
  • Use individual employee accounts;
  • Test the workflow on mobile;
  • Review weekly capacity;
  • Review monthly demand.

Summary: dispatch every job with the correct information

A field service schedule should answer five questions:

  1. Who is the customer?
  2. Where is the service?
  3. What work was approved?
  4. When will it happen?
  5. Who is responsible?

DunaHub connects those answers in one job record.

The Jobs module provides:

  • four documented work views;
  • jobs linked to CRM leads;
  • dates and appointment times;
  • addresses;
  • assigned technicians;
  • service values;
  • progressive status tracking;
  • automatic On my way SMS;
  • proposal-to-job conversion;
  • connection to invoicing;
  • automatic review-request workflow.

The operating process becomes:

Lead is created → Proposal is approved → Job is scheduled → Technician is assigned → Customer receives an arrival text → Work is completed → Invoice and review follow

Your company spends less time asking where technicians are, which customer is next, and what work was approved.

The schedule becomes one reliable source for the office and field team.

Frequently Asked Questions

Does DunaHub include field service job scheduling?

Yes. The Jobs module is available on every plan, subject to the plan’s monthly limits.

How many scheduling views are available?

Current documentation lists four views: table, calendar, list, and timeline.

Can I create a job from a CRM lead?

Yes. Jobs can remain linked to the original lead and customer history.

What information can a job contain?

A job can include the customer, date, time, address, service, value, assigned technician, notes, and status.

Can a proposal become a job?

Yes. An approved proposal can be converted into a job with prefilled information.

Can I assign a specific technician?

Yes. Each job can be assigned to a responsible technician or team user.

What job statuses are available?

The documented statuses are Scheduled, On the way, In progress, Completed, and Cancelled.

Does DunaHub track status in real time?

The current status becomes visible after a technician or authorized user updates the job.

Is status tracking automatic?

No. A user must change the status as the job progresses.

Does On the way send a customer text?

Yes. Changing the job to On the way can send an automatic SMS.

Does the On my way message use a credit?

Yes. Each SMS uses one prepaid credit.

Does On the way provide GPS tracking?

No. The status is an operational update, not live location tracking.

Does DunaHub include route optimization?

DunaHub should not currently be presented as an advanced route-optimization platform.

Can technicians use DunaHub on a phone?

Yes. DunaHub is responsive and works through a mobile browser.

Is there a native mobile app?

A native iOS or Android application should not be assumed unless officially released.

Can customers book their own service?

Yes. Online Booking can create a lead and a job automatically.

Do Free bookings count toward the job limit?

Yes. Public bookings share the Free plan’s monthly job allowance.

How many Jobs are included on Free?

Free includes ten Jobs per month.

How many Jobs are included on Starter?

Starter includes unlimited Jobs.

How many Jobs are included on Pro?

Pro includes unlimited Jobs.

Does DunaHub charge for each technician?

No. Pricing is flat per company within the user allowance of the selected plan.

What happens when a job is completed?

The company can create or send an invoice, and the Review Engine can send a Google review request after 30 minutes when enabled.

Can I cancel a job?

Yes. Cancelled is part of the documented status flow.

Can I filter jobs by technician or date?

The scheduling workflow is designed to help teams review work by responsibility and time. Available controls should be confirmed in the current workspace as the interface evolves.

Does DunaHub replace fleet-management software?

No. Companies needing GPS, telematics, advanced routing, or fleet maintenance may need a complementary tool.

Put every technician, address, and appointment in one schedule

Stop dispatching work through scattered text messages, paper calendars, and spreadsheets.

Create your free DunaHub account, schedule your first Jobs, assign your technicians, and keep customers informed from appointment confirmation to completed service.

SEO suggested

Meta title: Field Service Job Scheduling and Dispatch Software Meta description: Schedule field service jobs, assign technicians, track job status, send On my way texts, and connect every appointment to your CRM. Slug: /blog/field-service-job-scheduling-dispatch-software Primary keyword: field service job scheduling software Secondary keywords: technician dispatch software, contractor scheduling software, field service calendar, job status tracking, On my way text for customers Excerpt: Learn how to schedule and dispatch field service jobs, assign technicians, track progress, notify customers, and connect completed work to invoices and reviews.

Pronto para organizar seu pipeline de vendas?

O DunaHub é gratuito para começar. Sem cartão de crédito.

Criar conta grátis →