Dispatch technicians from ServiceNow incidents, with work notes and state written back
Keep ServiceNow as the system of record for incidents and requests, and send the ones that need someone on site to Fieldproxy. A record assigned to a field group, or flagged for a site visit, becomes a job with the affected configuration item and location attached. Fieldproxy dispatches it, the technician works it on the phone with GPS check-in, photos and a checklist, and scheduled, on site and complete are written back as work notes with the visit report linked. On completion the record moves to the state you choose, such as Resolved, while the SLA timers keep running in ServiceNow.
Fieldproxy is AI-native field service software, set up around your process and live within a day. It replaces the dispatch spreadsheet and any separate field app. ServiceNow stays your ITSM platform.
See your ServiceNow incidents dispatched
Tell us which assignment groups send people on site. We show it running on your own CIs and locations.
How it works
From ServiceNow incident to finished visit, step by step
A typical setup. The condition that sends a record, the job types and the states written back are agreed with your ServiceNow admin.
- 1
An incident or request needs a visit
Service desk, or a rule
The record is assigned to a field assignment group, or a site-visit flag is set. A business rule or outbound REST call sends it to Fieldproxy. Records that are fixed remotely never leave ServiceNow. - 2
The job is created with the CI and location
Fieldproxy
The number, short description, priority, caller, location and affected configuration item are copied onto a new job. The location is matched to the site record, with its access rules, and the CI to the asset at that site with its service history. If the location doesn't match a site, the job waits for the office with the reason. - 3
The right technician is picked
Dispatcher, helped by the Dispatch agent
The Dispatch agent suggests a technician by skill, distance, load and the SLA due time shown on the job. A dispatcher approves; moves are previewed and can be undone. A work note says the visit is scheduled. - 4
The visit runs on the phone
Technician, Android or iOS app
GPS check-in on arrival (a work note says on site), the site's access rules, the CI's history, the checklist for this job type with required photos and readings, parts from van stock and a sign-off. Offline when the building has no signal. - 5
Complete, with the report linked
Fieldproxy, through the Table API
Complete is added as a work note with the visit report linked, and the record moves to the state you choose, such as Resolved. A follow-up visit stays on the same job and the same record. - 6
Time, travel and cost stay on the job
Fieldproxy
Time on site, GPS trips and parts are recorded on the job, roll into mileage claims and cost per site, and can be billed to the customer or cost centre from Fieldproxy.
What syncs
What moves between ServiceNow and Fieldproxy, which way and when
Built on the ServiceNow Table API and business rules or outbound REST, with an integration user whose roles your ServiceNow admin approves.
| What | Direction | When | Detail |
|---|---|---|---|
| Incidents and requests | ServiceNow โ Fieldproxy | When assigned to a field group, or a site-visit flag is set | Number, description, priority, caller, location and the record's sys_id become a job. |
| Configuration item and location | ServiceNow โ Fieldproxy | With the record | Matched to the asset and site in Fieldproxy, so the technician knows what to fix and where. |
| SLA due time | ServiceNow โ Fieldproxy | With the record | Shown on the job. The SLA timers keep running in ServiceNow. |
| Scheduled | Fieldproxy โ ServiceNow | When dispatch confirms | Work note with the technician and time. |
| On site | Fieldproxy โ ServiceNow | At GPS check-in | Work note, so arrival comes from the phone's location. |
| Complete and visit report | Fieldproxy โ ServiceNow | On completion | Work note with the report linked: photos, checklist, readings and sign-off. |
| State | Fieldproxy โ ServiceNow | On completion | The incident or request moves to the state you choose, such as Resolved. |
| Time on site, mileage, parts | Fieldproxy โ ServiceNow | On completion; mileage per trip | Recorded in Fieldproxy. Writing time worked or close notes to the record is set up per account. |
| Later updates to the record | ServiceNow โ Fieldproxy | When the record changes after the job exists | Which changes (priority, reassignment, cancellation) update the job is set up per account. |
One record links to one job, so updates never create a second job.
See your own ServiceNow incidents turn into jobs before you commit.
Get DemoWhat stays, what moves
ServiceNow keeps the incidents. Fieldproxy replaces the field tools.
ServiceNow runs the service management process: intake, assignment, SLAs, CMDB and reporting. The part that happens in a van, at a site, with a phone, often runs on spreadsheets, emails and a separate field app that nobody in IT owns. Fieldproxy replaces those field tools, not ServiceNow.
Stays in ServiceNow
- Incident and request intake, assignment groups and the service catalogue.
- SLA definitions and the timers that measure them.
- The CMDB as the record of configuration items.
- ITSM reporting and the record the service desk works from, with the field story on it as work notes.
Moves to Fieldproxy, and what it replaces
Dispatch and the schedule
The spreadsheet or whiteboard beside ServiceNow goes. Every technician and job is on one board and map, the Dispatch agent suggests who should go, a dispatcher approves, and any move can be undone.
The technician app
Any separate field app goes. Technicians use the Fieldproxy Android and iOS app, offline, with the site notes, asset history, your checklist, photos, signature and GPS check-in.
Sites, assets and QR codes
Each location on a incident is a site record with its address, access notes and contacts, and the assets installed there with their history. A QR code per site and per asset opens the same record on the phone.
Mileage sheets and timesheets
GPS check-in and check-out sit on the job, and drives between jobs roll into a mileage claim a manager approves. See GPS timesheets and mileage.
Stock, quotes and invoices
Parts come off van or warehouse stock and are reordered on purchase orders. Quotes, invoices, payment links through Stripe and Tap to Pay run from the job, with two-way sync to QuickBooks Online, Desktop and Enterprise, Xero and Sage.
Ask it from Claude, ChatGPT or Copilot
Fieldproxy has its own MCP server: anything you can do in the app, such as finding the jobs waiting on a visit or raising the invoice, can be done from Claude, ChatGPT or Copilot, with a confirm step before any change.
Worked example, demo data
A network switch at a branch office, incident to resolved
Say Northgate Credit Union runs 22 branches, with IT on ServiceNow and four field technicians plus a contractor for the far branches.
- 1
The incident
INC0041872: "Branch 7 teller PCs offline." The service desk checks remotely, sees the access switch is unreachable, and assigns the incident to the Field IT group, priority 2. - 2
Into Fieldproxy
A business rule sends it. The location matches the Branch 7 site (alarm code with the branch manager, comms room key at the front desk) and the CI matches switch SW-B07-01 on the site's asset list, with its two earlier visits. The SLA due time shows on the job. - 3
Dispatch
The Dispatch agent suggests Mei, 25 minutes away with a spare switch in her van stock. The dispatcher approves and a work note says scheduled: Mei, ETA 14:10. - 4
The visit
Mei checks in at 14:06 (work note: on site), scans the QR code on the rack to open the switch's history, swaps the failed power supply, photographs the link lights and gets the branch manager's sign-off. - 5
Back in ServiceNow
Complete goes in as a work note with the visit report linked, and the incident moves to Resolved. The service desk's SLA report reads the timers it always has. - 6
Cost and travel
The part comes off Mei's van stock and is reordered on a purchase order, and her trip is added to her mileage claim.
Result: The service desk never phoned the field, Mei had the alarm code and the switch history before she arrived, and the incident record carries the proof of the visit.
Names, sites and ticket numbers in this example are made up to show the flow. They are not a customer and not a result.
The options
Ways to run field visits from ServiceNow
Described by kind of tool. Each fits some organisations.
| Approach | Fits when | What you give up |
|---|---|---|
| ServiceNow alone, with assignment groups and email | Technicians are on site already, or visits are rare | No dispatch map, technician app with required photos, van stock or mileage. |
| ServiceNow's own field service module | You want everything on the Now Platform and have the budget and admin time for it | Check the licence cost for every technician and contractor who needs it, and the admin time to configure it. |
| A configurable field service system connected to ServiceNow (Fieldproxy) | Field work has its own checklists, sites have access rules, contractors do some visits, and you want it running within a day | A second system to run. It replaces your field tools, so plan the switch-off of the spreadsheet and any old app. |
Setup
Connected, set up around your queues, live within a day
Your ServiceNow admin does the ServiceNow side. The rest is done by Fieldproxy's team.
- 1
A 30-minute call
Which assignment groups or conditions send people on site, which CIs and locations matter, which states are written back. - 2
Create the integration user
Your admin creates the integration user with the roles they approve. - 3
Choose what creates work
The assignment group or condition that sends a record to Fieldproxy, through a business rule or outbound REST. - 4
Map fields and states
Record fields, locations and CIs to the job, site and asset; job stages to the work notes and states written back. - 5
Build the field side, test, go live
Job types, checklists, technicians and skills, van stock. Sites and assets come across with free, assisted migration. Run real incidents through, check the record, go live.
Moving off a spreadsheet or another field app? Sites, assets, customers and open jobs come across with free, assisted migration. Fieldproxy is one price per company with unlimited users, so support agents, dispatchers, technicians and contractors can all log in. See pricing.
Fit
Who this is for, and when it isn't the right fit
A good fit when
- IT or facilities teams on ServiceNow that send technicians to branches, stores, offices or customer sites.
- Contractors do some of the visits and shouldn't need ServiceNow licences.
- You need required photos, checklists and sign-off on the record, and proof the technician was on site.
- The field side runs on spreadsheets, email or a separate app today.
Probably not the right fit when
- Every incident is resolved remotely.
- You have already rolled out ServiceNow's own field service module and it covers your visits.
- Your policy requires every field workflow to run inside the Now Platform.
- You want to replace ServiceNow itself. Fieldproxy keeps it as the ITSM platform.
Straight answers
ServiceNow and field service: questions we get asked
Which ServiceNow records can create a field job?
What is written back to ServiceNow?
Do configuration items come across?
What happens to ServiceNow SLAs?
Is this a replacement for ServiceNow Field Service Management?
What does the ServiceNow admin need to do?
Will an updated incident create a second job?
Do technicians or contractors need a ServiceNow login?
How long does it take to set up?
Can we query field work from Claude, ChatGPT or Copilot?
Related
Where to go next
Every helpdesk Fieldproxy connects to follows the same pattern: the incident stays where it is, the visit runs in Fieldproxy, and the result goes back. The same flow for Freshservice, Freshdesk, Zendesk and Zoho Desk.
Keep ServiceNow. Give the visit a proper home.
Tell us which incidents send someone on site today. We show it running on your own groups and CIs.
Get DemoLive within a day. Free, assisted migration. Unlimited users on one price per company.