Digital Transformation Partner Let's talk →
Field Service Management

Connect Your Field Workforce, Assets and Customers

Field service becomes difficult when technicians, dispatchers, customers, inventory, equipment, and service information operate across disconnected systems.

Etiquette helps businesses build connected field service experiences that bring scheduling, dispatch, work orders, assets, mobile workers, customer information, AI, automation, and analytics together.

SchedulingDispatchMobile WorkforceWork OrdersAssetsAIIoTPredictive Maintenance
CustomerServiceRequestDispatchTechnicianAssetResolutionCustomer AI & Data layerService history • Knowledge • IoT signals • Scheduling intelligence • Analytics Every completed visit feeds data back into the next one
The shift

Field Service Is Becoming Intelligent

Traditional field service often depends on manual coordination. Modern field service connects the complete lifecycle.

Where many field teams still start

  • Phone calls
  • Spreadsheets
  • Manual scheduling
  • Paper work orders
  • Repeated data entry
  • Dispatcher coordination
  • Technician callbacks
  • Manual status updates
  • Disconnected inventory
  • Delayed reporting

Reactive to Intelligent

Reactive Service→Connected Service→Predictive Service→Intelligent Service

Etiquette positions field service as Intelligent Field Operations — from service request to resolution, not simply software for scheduling technicians.

1Request
2Diagnose
3Schedule
4Dispatch
5Travel
6Service
7Complete
8Invoice
9Analyze

Every service visit should create data that improves the next one.

Definition

What Is Field Service Management?

Field Service Management coordinates employees, contractors, equipment, customers, schedules, work orders, inventory, and service activities performed outside an organization’s primary facility.

A modern FSM platform connects the people, assets and systems involved into one operational workflow.

Etiquette builds on its digital transformation and custom software experience to make that workflow practical.

One operational workflow can connect

  • Customers
  • Contact center
  • Dispatchers
  • Technicians
  • Managers
  • Assets
  • Inventory
  • Vehicles
  • CRM
  • ERP
  • Billing
  • IoT
  • Analytics
End-to-end journey

From Service Request to Resolution

Eight connected stages, one continuous record.

  1. Service Request

    Customer raises a support, maintenance, repair, installation or inspection request.

  2. Triage

    Understand the customer, asset, issue, priority, SLA and location.

  3. Scheduling

    Weigh technician, skill, location, availability, parts and priority.

  4. Dispatch

    Assign the right worker, with dispatcher oversight.

  5. Mobile Service

    The technician receives complete job context on their device.

  6. Work Completion

    Capture work performed, parts used, photos, notes and customer confirmation.

  7. Billing / Follow-Up

    Trigger the relevant downstream process automatically.

  8. Analytics

    Use service history to improve future operations.

Work order management

One Work Order. Complete Service Context.

Every work order carries what the technician, dispatcher and customer need, so nobody has to chase information.

  • Customer
  • Site
  • Asset
  • Problem
  • Priority
  • SLA
  • Technician
  • Scheduled time
  • Required skills
  • Required parts
  • Service history
  • Instructions
  • Checklist
  • Photos
  • Notes
  • Status
  • Resolution
  • Customer approval

Status flow

New→Triage→Scheduled→Dispatched→In Progress→Completed→Verified→Closed

Exceptions handled: On Hold • Parts Required • Reschedule • Escalated

Work Order · Sample layoutIn Progress
Customer
Customer name
Site
Site address
Asset
Asset ID · Model
Priority / SLA
High · Response SLA timer
Technician
Skill-matched worker
Parts
Reserved from van stock
Problem
Reported issue, error code and service history appear here.
Checklist
☑ Safety check   ☑ Diagnose   ☐ Repair   ☐ Photos   ☐ Customer sign-off
Intelligent scheduling

Get the Right Technician to the Right Job

Scheduling should weigh the full picture, not just who has a free slot.

  • Availability
  • Location
  • Skills
  • Certification
  • Priority
  • SLA
  • Travel time
  • Customer preference
  • Parts availability
  • Job duration
  • Working hours

AI and optimization can recommend better schedules by evaluating these constraints together and surfacing options. Dispatchers stay in control: they review, adjust and approve, and apply local knowledge that no model has.

Better scheduling is not simply filling calendars — it is matching the right resources to the right work.

Recommended assignments (illustrative) Job A · Priority: HighSkill: certified • Parts: in vanTechnician 1 Job B · SLA at riskSkill match • nearest • parts reservedTechnician 2 ✓ Suggested Job C · StandardCustomer window 2–4 pmTechnician 3 Dispatcher reviews, adjusts or approves every suggestion
Dispatch management

Give Dispatchers Real-Time Operational Visibility

A dispatcher console concept: the map, the people, the work and the risks in one view.

Live panels

  • Technicians & availability
  • Current and next jobs
  • Unassigned work
  • Delayed jobs
  • SLA risks and priority
  • Traffic where available

Actions

  • Assign
  • Reassign
  • Reschedule
  • Escalate
  • Contact technician
  • Contact customer
  • View route
  • Check inventory
Field service map

See Every Territory, Technician and Site

An interactive-style map layers technician locations, customer sites, current jobs, upcoming jobs, high-priority work and service territories, so coverage gaps and overloaded regions are visible at a glance.

Filter by

  • Technician
  • Team
  • Region
  • Status
  • Priority
  • Skill
  • Technician location
  • Customer sites
  • Current and upcoming jobs
  • High-priority jobs
  • Service territories
Region ARegion BHigh priority TechnicianCustomer sitePriority job

Illustrative map concept, not live data.

Mobile technician experience

Give Technicians Everything They Need in the Field

A mobile-first workspace that puts the full job context in the technician’s hand.

See

  • Today’s jobs
  • Route
  • Customer details
  • Asset
  • Problem
  • Service history
  • Parts
  • Knowledge articles
  • Instructions
  • Checklist

Do

  • Start travel
  • Arrive
  • Start job
  • Pause
  • Add note
  • Add photo
  • Scan asset
  • Record parts
  • Capture signature
  • Complete job

Offline-ready where architecture allows: jobs, checklists and notes can be captured without a signal and synchronize automatically when connectivity returns.

AI technician assistant

An AI Assistant for Every Field Worker

Ask in plain language. Get answers grounded in your authorized work orders, asset history, notes and approved knowledge.

What it can help with

  • Summarize service history
  • Retrieve manuals
  • Find troubleshooting instructions
  • Suggest relevant knowledge
  • Draft completion notes
  • Summarize work performed
  • Help identify required parts

Recommendations are grounded in authorized information and respect user permissions. The technician reviews and decides.

AI Should Give Technicians Better Context — Not Replace Their Expertise.

Industry signal: in Salesforce’s Field Service and Operations Guide (Jan 2026; 6,500 service professionals), 96% of field service teams said they plan to use AI for knowledge retrieval. Source. Vendor survey; results vary by organization. Learn about our Artificial Intelligence services.

Agentic field service

From Field Service Automation to Agentic Field Operations

Traditional automation executes predefined actions. AI agents can potentially coordinate a sequence of permitted field-service actions toward an objective.

Objective: resolve tomorrow’s scheduling conflicts

  1. Review upcoming appointments
  2. Identify conflicts
  3. Check technician availability
  4. Check required skills
  5. Check location and travel time
  6. Identify alternative technicians
  7. Recommend reassignment
  8. Notify dispatcher
  9. Update approved appointments after confirmation
  10. Notify customers

Objective: handle a technician cancellation

Technician unavailable→Find affected jobs→Identify alternative resources→Check skills & parts→Optimize route→Request approval→Update schedule→Notify customers

AI Agents Should Coordinate Within Rules, Permissions and Human Oversight.

Predictive maintenance

Move From Repairing Failures to Predicting Service Needs

Traditional

Equipment fails→Customer contacts service→Technician dispatched

Predictive

Asset data→Pattern detected→Risk identified→Service planned→Failure potentially avoided

Possible inputs

  • IoT sensor data
  • Temperature
  • Vibration
  • Pressure
  • Usage
  • Error codes
  • Service history
  • Age
  • Environmental data

Predictive maintenance estimates failure risk. It is not a guarantee that a failure will or will not occur.

Alert threshold (set per asset)Failure limitRisk flagged → work order createdCondition readingTime

Illustrative concept, not measured data.

Asset→IoT→Data→AI / Analytics→Risk→Work Order→Technician
Connected asset management

Know Every Asset You Service

One record per asset keeps history, entitlements and live condition together.

  • Asset ID
  • Serial number
  • Customer
  • Location
  • Model
  • Manufacturer
  • Installation date
  • Warranty
  • Service contract
  • Maintenance schedule
  • Service history
  • Parts
  • IoT status
  • Documentation

Technicians can scan a QR code or barcode to retrieve the asset record immediately.

Asset RecordQR / barcode scan CustomerLocationWarrantyContractIoT statusHistoryPartsDocuments
IoT + field service

Let Equipment Tell You When It Needs Attention

Connected equipment can generate alerts, usage data, errors, threshold events and condition data that field service can act on.

Machine detects abnormal vibration→IoT event→FSM receives event→Risk assessed→Work order generated→Technician scheduled→Customer notified→Service performed→Asset record updated

Connected assets turn field service from reactive response into proactive operations.

Parts & inventory

The Technician Needs the Right Part — Not Just the Right Address

  • Warehouse stock
  • Van inventory
  • Technician inventory
  • Reserved parts
  • Used parts
  • Returned parts
  • Reorder
  • Transfers

Scheduling considers required parts, so jobs are not assigned to technicians who cannot complete them.

Example: work order requires Part A

Before assigning a technician, check:

Skill+Availability+Location+Part availability
First-time fix

Improve the Chance of Resolving the Job on the First Visit

First-time fix depends on several things working together. No platform can guarantee a result, but each of these is within reach:

  • Accurate issue information
  • Correct technician
  • Required skill
  • Correct tools
  • Correct parts
  • Service history
  • Knowledge access
  • AI assistance

Track First-Time Fix Rate

Measure it, then analyze why repeat visits occur: missing parts, wrong skills, unclear diagnosis or unresolved root cause, and fix the cause.

UnplannedPlanned

Conceptual illustration.

Route optimization

Reduce Unnecessary Travel

Route planning can weigh technician and customer location, appointment windows, priority, travel time, traffic where available and job duration.

  • Reduce travel
  • Improve punctuality
  • Increase productive time
  • Reduce unnecessary journeys
Customer experience

Keep Customers Informed

Customers can

  • Request service
  • Choose available time
  • Track appointment
  • Receive technician ETA
  • Reschedule
  • Upload photos
  • View service history
  • Approve work
  • Sign completion
  • Make payment
  • Provide feedback

Notifications

Booking confirmation→Technician assigned→On the way→Delay→Job started→Job completed
Customer portal

Self-Service Without Losing the Human Experience

A portal where customers see their world of service, with an AI assistant where appropriate and a person always one step away.

  • Assets
  • Service requests
  • Appointments
  • Work orders
  • Contracts
  • Invoices
  • Documentation
  • Service history
  • Knowledge
  • AI assistant
Remote service

Solve Some Problems Before Sending a Technician

  • Chat
  • Video
  • Image upload
  • Remote diagnostics
  • Knowledge guidance
  • AI-assisted troubleshooting

Two possible outcomes

Remote ResolutionorField Visit Required

If a visit is needed, the diagnostic context goes directly into the work order, so the technician arrives informed.

Augmented reality

Bring Expert Knowledge Into the Field

Field-service organizations are increasingly exploring AR and visual AI to support technicians. Potential uses:

  • Step-by-step guidance
  • Equipment overlays
  • Remote expert assistance
  • Training
  • Visual diagnosis

AR is a forward-looking opportunity. Etiquette can help evaluate where it fits and integrate suitable third-party tools with your field service workflow. We do not offer proprietary AR hardware.

Service contracts & SLA

Manage Service Commitments

Jobs are prioritized automatically using SLA rules your organization approves.

  • Contract
  • Warranty
  • Service plan
  • Response SLA
  • Resolution SLA
  • Entitlements
  • Covered services
  • Expiration
Preventive maintenance

Schedule Maintenance Before Problems Occur

Recurring work can be generated from time, usage, meter reading, operating hours, service contract or manufacturer recommendation.

Maintenance Rule→Work Order→Schedule→Service→Next Maintenance
AI visual assistance

Use Images as Another Source of Service Context

Technicians can capture equipment, damage, error displays, installations and parts. AI may assist with classification, information extraction, knowledge lookup and documentation.

AI image analysis is an aid, not a definitive technical diagnosis. The technician’s judgment decides.

Field service + CRM

Connect Service With the Customer Relationship

When field service connects to CRM, the customer record shows sales history, products, assets, contracts, support cases, service history and opportunities. Service interactions feed back into CRM.

Sales + Service + Field Operations around one customer.

  • Sales history
  • Products
  • Assets
  • Contracts
  • Support cases
  • Service history
  • Opportunities
Salesforce Field Service

Extend Field Operations With Salesforce

Where applicable, Etiquette can help organizations implement or extend Salesforce-related service processes, including:

  • CRM
  • Service Cloud
  • Field Service
  • Work orders
  • Service appointments
  • Assets
  • Scheduling
  • Mobile workers
  • Customer history
  • Automation
  • Integration
  • Agent-assisted experiences

Salesforce as one possible platform

Salesforce can be a strong fit when your service model aligns with it. Etiquette also builds custom and hybrid solutions, so the architecture follows your requirements.

ERP integration

Close the Loop With Finance and Supply

Connect field service with customer, inventory, purchase, finance, billing, asset and contract data.

Job completed→Parts consumed→Inventory updated→Invoice created→ERP synchronized
Field service automation

Automate the Work Around the Work

  • Work-order creation
  • Assignment
  • Notifications
  • Reminders
  • Escalations
  • Customer updates
  • Documentation
  • Inventory transactions
  • Follow-ups
  • Invoicing triggers

Field service workflows connect naturally to workflow orchestration. Explore our Digital Process Automation capabilities.

Analytics

Measure the Complete Service Operation

Turn field activity into operational insight with Data & Analytics.

Open work orders—
Completed work orders—
Jobs per technician—
First-time fix rate—
Average response time—
Average resolution time—
SLA compliance—
Travel time—
Technician utilization—
Repeat visits—
Customer satisfaction—
Parts usage—
Asset reliability—
Preventive vs reactive—
Cost per service visit—

Dashboard layout only. Values populate from your own operational data; no figures are shown here.

AI operations dashboard

See What Is Likely Next, Not Just What Happened

Predictions & recommendations

Estimates that need human judgment

  • Jobs at risk
  • Likely SLA breaches
  • Scheduling conflicts
  • Repeat failure patterns
  • Inventory risks

Confirmed facts

Recorded operational state

  • Asset alerts received
  • Technician availability
  • Work-order status
  • Parts on hand

The dashboard clearly labels what is predicted or recommended and what is confirmed.

Industries

Field Service Across Industries

Manufacturing

Equipment maintenance, installation and repair.

Healthcare

Medical equipment service and facility maintenance.

Energy & Utilities

Distributed asset maintenance and inspection.

Telecommunications

Installation, maintenance and network service.

HVAC

Installation, preventive maintenance and repair.

Automotive & EV

Vehicle service, charging infrastructure and equipment support.

Real Estate & Facilities

Building, equipment and facility maintenance.

Retail

Store equipment and distributed-site maintenance.

Logistics

Fleet and operational equipment.

Industrial Equipment

Installation, commissioning, inspection and service.

Maturity model

How Mature Are Your Field Operations?

Most organizations move through these stages at their own pace. Not every organization needs Level 6.

  1. Level 1

    Reactive

    Customer reports problem.

  2. Level 2

    Digitized

    Work orders become digital.

  3. Level 3

    Connected

    Customers, assets, technicians and systems are connected.

  4. Level 4

    Optimized

    Scheduling, routes and resources are optimized.

  5. Level 5

    Predictive

    Data helps identify likely service needs.

  6. Level 6

    Agentic

    Governed AI coordinates approved service workflows.

Architecture

Modern Field Service Architecture

Customers

  • Portal
  • Mobile
  • Contact Center
  • AI Assistant

Field Service Platform

  • Work Orders
  • Scheduling
  • Dispatch
  • Mobile
  • Assets
  • Inventory
  • SLA

Intelligence

  • AI Agents
  • Predictive Analytics
  • Optimization
  • Knowledge
  • Automation

Connected Systems

  • CRM
  • Salesforce
  • ERP
  • Inventory
  • Billing
  • IoT
  • Maps
  • Payments
  • HRMS
  • APIs

Analytics & Governance

  • Dashboards
  • Audit
  • Permissions
  • Monitoring

Workforce data can connect with our Human Resource Management System; healthcare facility service with our Hospital Management System; and smart-space deployments with SpaceOS. Retail service can connect to Digital Commerce.

Mobile workforce trend

The Technician Experience Matters

Field-service transformation is also a workforce challenge. Technicians continue to lose meaningful time to administrative work and often lack complete customer context.

Example: Salesforce’s January 2026 field service research reports technicians spend about 18% of working hours (over 7 hours a week) on administrative tasks. Source. Vendor survey of 6,500 service professionals.

Technology should reduce the burden, not just measure utilization.

Reduce

  • Data entry
  • Repeated calls
  • Searching for manuals
  • Searching for customer information
  • Searching for parts
  • Manual reports

Increase

  • Context
  • Knowledge
  • Coordination
  • Safety
  • Productivity
Trends

Field Service Trends Shaping 2026 and Beyond

Our reading of where the industry is heading, based on public research and our project experience.

1

Agentic Field Service

AI agents increasingly assist with scheduling, administrative work, information retrieval and workflow coordination.

2

Predictive Maintenance

Organizations are moving from scheduled and reactive maintenance toward condition-aware service supported by IoT and analytics.

3

Unified Service Data

Connected CRM, asset, scheduling, inventory and customer information is becoming essential for effective AI.

4

Technician AI Assistants

Technicians increasingly expect instant access to knowledge, history and troubleshooting information.

5

Visual AI & AR

Images, computer vision and augmented reality are emerging as technician support tools.

6

Mobile-First Operations

The mobile application becomes the technician’s primary workspace.

7

Remote Service

Organizations increasingly attempt remote diagnosis and resolution before dispatch.

8

Outcome-Based Service

Customers increasingly value uptime and outcomes rather than simply service visits.

9

Connected Assets

IoT allows service organizations to understand equipment condition between visits.

10

Field Service Automation

Administrative processes around field service increasingly become automated.

Research reference: Salesforce, Field Service and Operations Guide (January 2026). Related reading: our Digital Transformation practice.

Why Etiquette

Why Etiquette for Field Service Management?

1

Process-First Thinking

Start with how field operations actually work.

2

AI + Automation

Introduce intelligence where it creates practical value.

3

Integration Expertise

Connect CRM, ERP, inventory, maps, IoT and enterprise applications.

4

Mobile Engineering

Build practical experiences for technicians in the field.

5

Data & Analytics

Turn field activity into operational insight.

6

Flexible Architecture

Use standard platforms, Salesforce, custom engineering or hybrid solutions depending on requirements.

Our approach

How We Transform Field Operations

Connect. Dispatch. Resolve. Predict. Improve.

  1. 1. Discover

    Understand service model.

  2. 2. Map

    Document current workflow.

  3. 3. Connect

    Integrate business systems.

  4. 4. Mobilize

    Give field workers the right tools.

  5. 5. Automate

    Remove repetitive administration.

  6. 6. Optimize

    Improve scheduling and resource allocation.

  7. 7. Predict

    Use data to anticipate service needs where appropriate.

  8. 8. Improve

    Continuously measure outcomes.

Build vs buy

Platform, Custom FSM or Hybrid?

We do not force every customer into one architecture.

Standard Platform

Use where requirements align well with established FSM platforms. Salesforce is one possible platform where appropriate.

Custom Solution

Use when workflows, customer experience or integrations are highly differentiated.

Hybrid

Enterprise platform + custom applications + APIs + AI.

Core values

Innovation. Integrity. Impact.

Innovation

Apply AI, connected systems, automation and modern mobile experiences to solve real field-service challenges.

Integrity

Build transparent, secure and accountable service workflows.

Impact

Focus on better customer experience, better technician experience and better operational outcomes.

Innovation drives us. Integrity guides us. Impact defines us.

Get started

Turn Every Field Visit Into a Better Service Experience

Whether you are managing technicians, equipment, facilities, installations, inspections or distributed service operations, Etiquette can help connect the people, processes, assets and systems behind your field operation.

Field service is no longer just about dispatching technicians. It is about connecting customers, technicians, assets, inventory, data, AI, IoT and enterprise systems to deliver faster, smarter, more predictive service.

Request a Field Service Assessment

Tell Us About Your Field Operations

We use your details only to respond to your enquiry. See our Privacy Policy.

FAQ

Frequently Asked Questions

What is Field Service Management?

Field Service Management (FSM) coordinates workers, equipment, customers, schedules, work orders, inventory and service activities performed outside an organization's primary facility, such as repairs, installations and inspections.

What does Field Service Management software do?

It manages the service lifecycle: capturing requests, creating work orders, scheduling and dispatching technicians, giving them mobile access to job context, tracking assets and parts, and reporting on service performance.

How can AI improve field service?

AI can recommend schedules, retrieve knowledge and service history for technicians, draft notes, flag jobs at risk and help surface asset issues. It works best with unified, authorized data and with people making final decisions.

What is predictive maintenance?

Predictive maintenance uses asset data such as sensor readings, usage, error codes and service history to estimate the risk of failure, so service can be planned. It estimates risk and does not guarantee outcomes.

What is the difference between preventive and predictive maintenance?

Preventive maintenance is scheduled by rules such as time, usage or meter readings. Predictive maintenance is driven by the observed condition of the asset and estimated risk.

Can FSM integrate with CRM and ERP?

Yes. Field service can connect with CRM for customer and case context, and with ERP for inventory, purchasing, finance and billing. Integration scope depends on the systems involved.

Can field technicians use the system offline?

Offline use can be supported where the architecture allows. Technicians capture jobs, notes and photos without a signal, and data synchronizes when connectivity returns.

How does Field Service Management improve scheduling?

It considers skills, availability, location, priority, SLA, travel time, parts and customer preference together, giving dispatchers better recommendations while keeping them in control.

What is agentic field service?

Agentic field service uses AI agents to coordinate a series of permitted actions, such as resolving a scheduling conflict, within defined rules, permissions and human approval.

Can Etiquette integrate with Salesforce Field Service?

Where applicable, Etiquette can help organizations implement or extend Salesforce service processes, including Service Cloud, Field Service, work orders, assets, scheduling and integrations.

Can Field Service Management connect with IoT equipment?

Yes. Connected equipment can send alerts, usage and condition data that trigger risk assessment and work orders, subject to device and platform capabilities.

Which industries use Field Service Management?

Manufacturing, healthcare, energy and utilities, telecommunications, HVAC, automotive and EV, facilities, retail, logistics and industrial equipment, among others.

More questions? Contact Etiquette.