FieldproxyAI-native field service software

Scheduling

How do I get warned about other open jobs at the same site when I schedule a visit?

Run one check at two moments, when a job is created and when a visit is put on the schedule: look up every job at the same site record that is not completed or cancelled, and show the list before the user can save. Then make the user pick one of three outcomes: merge it into the existing job because it is the same request, add it to the visit that is already planned so one technician does both, or keep it separate with a reason. The check only works if every job is tied to one site record, not to a typed address, and if email, phone and portal requests all pass through it.

  • Match on the site record ID, never on address text. Two spellings of one address defeat the check.
  • Check twice: at job creation (duplicates) and at scheduling (visits that could be combined).
  • Three outcomes only: merge, combine into one visit, or keep separate with a reason.
  • Warn, do not block. A second job at a busy site is often legitimate.
  • Include recently completed jobs (e.g. the last 30 days) so a recall is not booked as new work.

Book your demo

A video call with our team

Number of employees

This page is about catching a second job or visit at a site before it is booked. Cleaning up duplicate customer records is a different task and most tools handle it with a merge screen.

Facts checked as of November 2026. Sources at the end of the page.

Step by step

How the same-site check works, step by step

The rule is simple to describe and easy to get wrong in the details. These are the parts that decide whether dispatchers trust the warning or learn to click past it.

1. Make the site the key

Every job needs a link to one site record: the store, building, facility or property, with its own ID, under the customer that pays. If jobs carry only a typed address, '14 Mill Rd' and '14 Mill Road, Unit B' are two places to the software and no check will find them. Clean the site list first and merge the duplicates.

2. Define what open means

Write the statuses down. Open usually means everything that is not Completed, Cancelled or Invoiced: new, waiting to schedule, scheduled, in progress, on hold, waiting for parts, quote needed. On-hold and waiting-for-parts jobs matter most, because they are the ones a dispatcher forgets are there.

3. Check when the job is created

As soon as the site is picked on a new job, list the open jobs at that site with job number, trade, short description, status, assigned technician and next visit date. This is the duplicate check. It catches the customer who emailed at 8 am and phoned at 10 am, and the client portal work order that someone already keyed from a phone call.

4. Check again when the visit is scheduled

When a visit is dragged onto the board or given a date, list the other visits planned at that site within a window (e.g. 7 days either side), with the technician and date. This is the combine check. The question it answers is whether one technician can do both on one trip.

5. Narrow the match so it stays useful

At a site with one job a year, any open job is worth showing. At a hospital or a distribution center with 20 open jobs, rank them: same asset first, then same trade or problem type, then everything else. Facilities platforms do this with trade, problem code and equipment filters.

6. Look back as well as forward

Add jobs completed at the site in a recent window (e.g. 30 days) to the list, marked as recent. A new call about the same unit two weeks after a repair is probably a recall or a warranty return, and should be linked to the first job and priced differently.

7. Force one of three outcomes

Merge: the new request is the same work, so its notes, photos and caller are added to the existing job and no new job is created. Combine: it is different work, so a second job is created and its visit is placed with the same technician on the same day as the first. Keep separate: different trade, different skill, different urgency or different payer, with a reason picked from a short list.

8. Run every intake channel through it

The check has to run for jobs created from email, phone, a customer portal, an integration with a client's work order system and recurring maintenance schedules, not only for jobs typed on the booking screen. Automated intake is where most duplicates are born, because nobody is looking at the screen.

9. Keep the decision on the record

Store who saw the warning, what they chose and why. When a customer asks why two technicians came in one week, or why two requests became one invoice, the answer is on the job.

Failure modes

Why it goes wrong

The other job exists but is not visible at the moment of scheduling

A commercial electrical contractor doing 30 to 40 visits a day told us two jobs at one site could have gone to the same technician at the same time, but the scheduling screen did not show the second one. The site page listed both. Nobody opens the site page while dragging a visit onto a board.

The customer emails, then calls

The same contractor said they end up putting the job in twice. One person turns the email into a job. Another person answers the phone an hour later and books it again. Both jobs get a technician.

Several people work the same request

The same contractor described several people looking at the same job because nobody was sure who it was assigned to. Without an owner on the job from the first minute and a visible open-jobs list, each person assumes they are the only one handling it.

A client work order arrives through two doors

A commercial facility maintenance company with about 1,300 open work orders gets work from client systems and from a dispatch inbox. The same client work order can arrive as an integration record and as an email. If the client's work order number is not stored in its own field and checked for uniqueness, it becomes two jobs.

The maintenance visit and the service call never meet

A contractor serving restaurant chains runs planned maintenance visits per location on a contract, with reactive calls on top. If the two are scheduled from different lists, a technician can be sent for a walk-in cooler fault on Tuesday while another does the quarterly maintenance at the same restaurant on Thursday. One trip could have covered both.

The warning fires on everything

If the check lists every open job at a large site with no ranking, dispatchers dismiss it within a week. A warning that is right one time in ten trains people to ignore it.

Options

Ways to do it

What each kind of tool does, as its own help pages describe it in November 2026. The useful split is between tools that warn you at the moment of booking and tools where the information exists but you have to go and look.

ApproachWhat it doesWatch for
Spreadsheet or whiteboard, plus memoryThe dispatcher filters the job list by site before booking, or remembers. Works while one person books every job.Fails the day two people book, or when jobs start arriving by email and portal without a person typing them.
Contractor field service software: look it up on the site pageJobber's property details page gives an overview of all upcoming and past work at the address, with tabs for requests, quotes, jobs and invoices. BuildOps has a Jobs & Visits tab on the Property page with all past and current jobs and visits, and recommends starting a new job from the Property page. In ServiceTitan the customer record comes up when the office clicks the incoming call.The help pages we read for these three describe where to see the other jobs, not a warning when you book or schedule. Ask each vendor to show the warning on the dispatch board, not on the site page.
A client's work order platform (ServiceChannel)ServiceChannel checks for possible duplicates per location before a work order is created. Its API call takes the location ID and, optionally, trade, problem code, problem type and equipment. The client sets days of history, filters and excluded categories and statuses on the dashboard's Request tab. When a provider enters a second work order close to the first, it is linked to the first, marked In Progress - Possible Duplicate CIWO, and its not-to-exceed amount is set to $0.This protects the client's side. As the contractor you still need your own check, because the same site also sends you work by phone and email that never touches the client's system.
Facilities and maintenance systems with a built-in checkAccruent vxMaintain lists possible duplicates on the Create Work Order screen: work orders on the same asset created in the last 183 days or completed in the last 30, with a recall-period match highlighted in red. The user can still create the work order. Expansive FM shows a banner when another work order exists at the same site with the same service type. FMX matches on request type, request name and building, switched on per request module.The rule is the vendor's. Expansive's article says the criteria cannot currently be customised. Check whether the rule can use your own fields, such as trade or the client's work order number.
Text matching on the descriptionLimble compares the wording of a new work request with open work orders on the asset and warns the requester, who can submit anyway or cancel. An admin sets how many phrases must match. Limble's article says Enterprise customers can enable it. Asset Essentials Enterprise groups likely duplicates per site on a Review Duplicates page that refreshes daily.Text matching finds the same problem described twice. It does not find two different jobs at one site that could share a trip. A daily review page finds duplicates after the technician may already be booked.
Enterprise platforms you configure yourselfSalesforce Field Service has appointment bundling, which groups service appointments into one bundle under a bundle policy. A restriction policy can use any default or custom Service Appointment field, and bundling has to be enabled in Field Service Settings. Microsoft's Dataverse, which Dynamics 365 Field Service runs on, ships default duplicate detection rules for accounts and contacts only. Rules for other record types have to be created, and only five can be published per record type.Both are toolkits. Someone has to design the rule, build it and maintain it, so budget for an admin or a partner.
Field service software set up around your rule (Fieldproxy)The check is configured to your own definition of site, open and related, and runs at job creation and at scheduling for every intake channel, including jobs created by AI agents from emails and calls.It is set up for you, not a switch you flip yourself on day one. Bring your status list and three real examples of doubled jobs to the first call.

Vendor behavior changes. Ask for a live demo of the warning with two jobs at one site before you rely on any row above.

Worked example

A worked example

Say an electrical contractor runs 35 visits a day across 600 commercial sites, so about 175 visits in a five-day week. The numbers below are an illustration, not a benchmark. Run the same count on your own job list for last month.

On Monday morning the office exports open jobs and groups them by site. 14 sites have two or more open jobs. Reading them, 3 pairs are the same request entered twice: one from an email and one from a call. 8 pairs are different work that one technician with the right skill could do in one trip. 3 pairs are properly separate: a lighting retrofit crew and an urgent no-power call.

The 3 duplicates would each have sent a second technician to a job already done. The 8 combinable pairs would each have cost a second trip. If a trip to site averages 45 minutes each way, that is 11 avoidable trips and about 16 hours of driving in one week, before counting the customer who asks why two vans turned up.

With the check in place, the same week looks like this. The 3 duplicates are merged at creation, and the caller's notes are added to the first job. The 8 pairs show up when the second visit is scheduled, and the dispatcher places it with the same technician on the same day. The 3 separate pairs are kept apart with the reason 'different crew'. The weekly report shows 14 warnings, 3 merges, 8 combines and 3 keeps, which is the number to watch over time.

Before you buy

What to check before you buy

Good signs

  • The warning appears on the booking screen and on the dispatch board, at the moment of saving.
  • It matches on the site record, and can narrow by trade, asset or problem type.
  • You decide which statuses count as open, and how many days of completed jobs are included.
  • Merge keeps the notes, photos, caller and client work order number from both requests.
  • Jobs created from email, a portal, an integration or an AI agent go through the same check.
  • The client's work order number is its own field and cannot be saved twice for the same customer.
  • There is a report of warnings and what was decided, by user and by site.

Red flags

  • The vendor's answer is that you can see all jobs on the customer or property page.
  • Duplicate detection means duplicate customer records, not duplicate jobs.
  • The check blocks the save with no override, so staff work around it with a fake site.
  • It only runs for jobs typed by a person, and automated intake skips it.
  • The rule is fixed by the vendor and cannot use your own fields.
  • Duplicates are found by a nightly or daily review, after the visit is already assigned.

In Fieldproxy

Setting it up in Fieldproxy

Fieldproxy is set up around your process, so the check is built to your own rule during setup. Settings marked e.g. are examples to change.

Sites as their own record

Each customer has its sites, and every job, visit, asset and contract links to a site. Your site list is imported and duplicates are merged during the free, assisted migration, so the check has a clean key from day one.

Open jobs at this site, on the booking screen

When a site is picked on a new job, the screen lists that site's open jobs: number, trade, status, technician and next visit (e.g. statuses other than Completed, Cancelled and Invoiced, plus jobs completed in the last 30 days marked Recent). The user picks Merge, Combine or Keep separate, and Keep separate asks for a reason.

The same list when scheduling

On the dispatch board, a visit at a site with another visit planned nearby in time (e.g. within 7 days) shows the other visit and its technician, so the dispatcher can put both on one trip. The Dispatch agent (/agents/dispatch-agent) assigns by distance, skills and certifications, so the combined visit goes to someone qualified for both jobs.

Email and PDF work orders

The Document intelligence agent (/agents/document-intelligence-agent) turns incoming emails, PDFs and client work orders into jobs. Before it creates one, the same site check runs and the client's work order number is compared (e.g. unique per customer), so an email that repeats an existing job is attached to it instead.

Calls and texts

Front Desk holds calls, texts and chats in one inbox, answered by AI agents against your real job data. When a known contact gets in touch, their site's open jobs are what the agent works from, so a caller asking about a job that already exists gets an update, not a second booking.

A watch on what slips through

The Watcher agent (/agents/watcher-agent) flags sites with two or more open jobs whose visits are on different days or with different technicians (e.g. checked every morning). In the Command Center (/agents/command-center) you can ask which sites have more than one open job this week and merge or reschedule from there. Every change comes as a confirm card a person approves, with Undo.

The weekly number

The Scheduler agent (/agents/scheduler-agent) can email a weekly report (e.g. warnings shown, merges, combines and keeps by user and site). One price per company with unlimited users, so every dispatcher and project manager sees the same check; see /pricing.

How switching works

How switching to Fieldproxy works

We move your data over and set the system up to the way you already work. Fieldproxy replaces the old tool; it does not run alongside it.

  1. Show us three doubled jobs

    Bring three real cases from the last month: a duplicate, a pair that should have shared a trip, and a pair that was right to keep apart. They define the rule.
  2. We clean the site list

    Customers, sites, assets and open jobs come across in a free, assisted migration, with duplicate sites merged so every job has one site ID.
  3. We set your rule

    Which statuses count as open, how many days back to look, what narrows the match (trade, asset, problem type), and the list of reasons for keeping jobs separate.
  4. Your team goes live

    Live within a day: the office books and schedules with the warning on, and technicians get the Android or iOS app.

FAQ

Questions people ask

Can field service software warn me when other open jobs exist at the same site when scheduling?
Some can, and it is worth asking to see it live. Many contractor tools list a site's jobs on the site or property page but do not raise a warning at the moment of booking or scheduling. Facilities platforms more often have a built-in duplicate check.
How do I stop the same job being entered twice when a customer emails and then calls?
Run the open-jobs check when the site or caller is identified, before the job is saved, and make it run for jobs created from email as well as from the phone. The second person then sees the first job and adds the caller's notes to it.
Should the system block a second job at the same site or only warn?
Warn, and ask for a decision. Blocking fails at large sites where several jobs are normal, and staff get around it by picking the wrong site. A required choice of merge, combine or keep separate, with a reason, gives you the control without the workaround.
Can I see a customer's open visits when a call comes in from a known phone number?
Yes, if the phone system or call agent is connected to your job data, so the caller's number finds the contact, the contact finds the site and the site's open jobs are shown. Ask the vendor which phone systems they connect to.
What is the difference between a duplicate job and a related job?
A duplicate is the same request recorded twice and should be merged into one job. A related job is different work at the same site, which stays a separate job but can share a visit, a technician and a trip.
How do I combine a planned maintenance visit with a service call at the same location?
Include recurring maintenance visits in the scheduling check. When a service call is booked at a site with a maintenance visit due inside the window, the dispatcher can pull the maintenance forward or add the service call to it, if the technician has the skills and time for both.
Does a client's work order system catch duplicates for me?
Only for work that passes through it. ServiceChannel, for example, checks for possible duplicates per location on the client's side. Work the same site sends you by phone or email, and your own maintenance visits, are invisible to that check.
What if the two jobs need different technicians?
Keep them separate and record why. The check is there to make the decision visible, not to force one trip. Different trades, different certifications and different urgency are all good reasons.

Sources

Competitor details on this page come from the vendors' own pages and documentation, checked as of November 2026. Plans and prices change, so check the vendor's current page before you decide.

See it built on your workflow

Tell us how your jobs run today. We build a demo on your stages, forms and pricing before the call.