From dispatch to done — without the chaos

Field service teams lose hours every week to scattered tools — calendars in one place, time sheets in another, customer updates in email, and job status in someone's head. ServiceIQ pulls all of it into a single view so dispatchers, technicians, and managers are always working from the same truth.

Every job is a first-class record with its own pipeline stage, assigned technicians and contractors, geocoded site address, linked drawings and submittals, checklist, time entries, append-only status history, and HubSpot deal sync. Whether you run 10 jobs a week or 500, the same workflow scales without re-architecting.

Scheduling in ServiceIQ is a single source of truth shared across the calendar, the dispatch map, and the technician's mobile view. When a dispatcher assigns a job, the system writes the assignee, scheduled window, and any contractor association in one transaction — every downstream surface (the tech's schedule, the customer's pending update, the kanban column, the HubSpot deal stage) reflects the change immediately.

Addresses are geocoded on save through Mapbox, including for jobs created via CSV import, so a job is dispatch-ready the moment it lands. Conflict detection runs against the assignee's existing scheduled blocks before a new assignment is committed, and the dispatch map respects the same persisted filters used on the kanban board so the dispatcher never has to re-apply context when switching views.

A customer update starts life as a job note written by the technician on site. When that note is promoted to an update, the system creates a separate record with its own draft → approved → sent state machine, leaving the original note untouched as the source of truth for internal context. The approver — typically a manager or office lead — reviews every pending message in a single queue at /customer-updates, edits the wording if needed, and either approves or rejects it.

Once approved, the update is sent to the customer and simultaneously synced to HubSpot as an engagement on the linked contact or company. The system records the approver, the approval timestamp, and the HubSpot sync status against the update record so there is a complete chain of custody from the field note to what the customer actually received. Failed syncs are surfaced for retry rather than silently dropped, and every state change is captured in the audit trail.

Quality control shouldn't depend on memory. Build a checklist template once for an HVAC start-up, an electrical inspection, or a plumbing call-out — then apply it to every matching job automatically. Templates are organization-scoped, drag-to-reorder, and log per-tech attribution on every completed item.