Three field service software vendors announced new products in the first weeks of November 2026. BuildOps introduced AI agents for quoting, job follow-up and billing at its Forge 2026 conference. Zuper added custom agents to its Agent Studio, so contractors can set up agents for their own office routines. ServiceJan published new figures for its platform, which puts field service management, CRM and a customer marketplace in one system.

The announcements go in two directions. BuildOps and Zuper are using AI for office work that tends to slip, such as quotes nobody followed up and jobs nobody invoiced. ServiceJan is adding a source of new jobs to the same system where those jobs get scheduled. Below we look at what each company announced, how the approaches differ and what service leaders should ask before they buy.

Key takeaways

  • BuildOps launched Revenue, Service Coordinator and Billing agents for commercial contractors on November 5, 2026. A person approves each action before it reaches a customer.
  • Zuper now lets customers create their own AI agents in plain English, test them on their Zuper data and switch them on when they are ready.
  • ServiceJan reports more than 285,000 U.S. service providers in its network. Marketplace bookings arrive on the same work-order board as existing jobs.
  • Both agent launches focus mainly on office work: quotes, invoices, collections and follow-ups.

BuildOps: three agents for the commercial contractor’s back office

BuildOps sells software to commercial HVAC, electrical, plumbing and fire and life safety contractors. It announced its Service Agents at Forge 2026, its annual customer conference. According to the BuildOps announcement, the agents run inside the platform and use the job, quote and customer data it already holds.

  • Revenue Agent reads technician visit notes and tracks quotes, service agreements and equipment. It flags repairs that were written up but never quoted, equipment on a serviced site that is not under contract, quotes that were never sent or went quiet, and approved work with no date on the schedule.
  • Service Coordinator Agent looks for stalled jobs and moves them toward completion.
  • Billing Agent applies each customer’s billing rules, builds the invoice and flags low markups or negative margins before it goes out. It also catches finished jobs that were never invoiced.

Each agent drafts a next step, such as a quote or a follow-up email, and routes it to the person who owns the decision. BuildOps says nothing an agent writes reaches a customer until that person approves it. Each finding shows the evidence behind it, and rejected suggestions are logged with a reason. The company also previewed a Collections Agent and AP automation for vendor bills.

Zuper: agents that contractors set up themselves

Zuper, which sells a dedicated product for roofing and exterior contractors, already offers pre-built agents for common tasks, including CSR, Field, Weather, Reputation and Sales Coach agents, with an AR agent listed as coming soon. In November it added custom agents to Zuper Agent Studio. A user sets up an agent in four steps without writing code:

  • describe the task in plain English, the way you would brief an office manager
  • choose when it runs, for example every evening or every Monday morning
  • add the checklists and documents the team already works from
  • run a test before turning it on

The agents work on what is already in Zuper, such as jobs, customers, quotes and invoices. Zuper’s examples include an invoice catcher that flags finished jobs with no invoice, a quote chaser for quotes with no answer after 14 days, a list of signed jobs that still have no install date, and a Monday report of jobs that slipped the week before. According to Zuper, nothing goes live until the user has tried it.

Zuper’s Agent Studio page does not list pricing for custom agents, so buyers should ask how they are billed. In September we covered Zuper’s launch of four AI agents for field service teams.

ServiceJan: new jobs inside the scheduling system

ServiceJan took a different route. In its November 5 announcement, the company said more than 285,000 U.S. service providers are in its network and more than 4.2 million services have been managed through its technology as of October 2026. Both figures are company-reported.

A customer describes the job, adds photos and picks a provider and an open time. The booking then arrives as a work order next to the provider’s existing jobs. Providers choose the services and areas they cover and which technicians can receive marketplace requests, and they can pause marketplace work without pausing their account. ServiceJan says it does not sell shared leads and does not guarantee bookings.

Retailers, manufacturers, warranty companies and other commercial accounts can submit work orders through a partner portal that shows each partner only its own jobs. Providers can also embed a request form on their website, and ServiceJan records which site each request came from.

How the three approaches compare

BuildOpsZuperServiceJan
AnnouncedNovember 5, 2026, at Forge 2026November 2026November 5, 2026
Customers namedCommercial specialty contractorsRoofing and exterior contractorsIndependent providers to multi-location and enterprise organizations
What is newThree pre-built back-office agents, plus previewsCustom agents created by the customerFSM, CRM and marketplace in one system, with network figures
Main useQuotes, stalled jobs, invoicingCompany-specific office routinesWinning and routing new jobs
Who stays in controlA person approves each action before it reaches a customerThe customer defines, tests and activates each agentThe provider sets services, areas and technicians and can pause marketplace work

BuildOps and Zuper both aim at the stretch between a finished visit and a paid invoice, but they package it differently. BuildOps gives each agent a fixed role and asks for approval on every action, which makes it quicker to start and easier to supervise. Zuper gives the customer a blank page. That suits companies whose routines don’t match a template, though someone has to write the instructions and keep them current. Agents in dispatch are a separate topic, covered in our article on how AI agents are changing the dispatcher role.

ServiceJan raises other questions. If a marketplace books jobs directly into a provider’s schedule, the provider needs to know who owns that customer afterwards and how marketplace jobs compete with contract work for technician time.

What service leaders should check before turning on AI agents

For a wider shortlist, our comparison of the best field service management software in 2026 and our list of AI-powered field service management solutions cover more platforms. Whichever vendor you look at, these points are worth settling early:

  1. Measure the leak first. Pull last quarter’s unsent quotes, completed jobs without an invoice and overdue invoices, so you can test an agent against a number you already know.
  2. Ask what the agent can do on its own. Check whether it only drafts, or can also send messages, update records or change prices, and who can change that setting.
  3. Check the audit trail. You should be able to see why the agent flagged a record and what happened next, including the suggestions your staff rejected.
  4. Give custom agents an owner. If your team builds agents from its own checklists, someone has to update the instructions when the process changes and switch the agent off when it no longer fits.
  5. Clarify AI pricing. Ask whether agents are included in your plan, billed by usage or sold as an add-on.
  6. Read the routing rules for marketplace jobs. Confirm which technicians receive them, how they are prioritized against contract work and whether you can pause them in peak season.

Teams still early in their AI plans can find adoption data in our article on AI adoption in field service.

Frequently Asked Questions

What did BuildOps announce at Forge 2026?

BuildOps introduced three Service Agents: Revenue, Service Coordinator and Billing. They find unquoted work, stalled jobs and billing errors, then draft a fix for a person to approve. The company also previewed a Collections Agent and AP automation.

What are Zuper’s custom agents?

They are AI agents that Zuper customers create in Agent Studio by describing a task in plain English, choosing when it runs and adding their own checklists. The agent works on the company’s jobs, customers, quotes and invoices once it has been tested and turned on.

Do these AI agents act without human approval?

It depends on the vendor. BuildOps says nothing an agent writes reaches a customer until a person approves it. Zuper’s custom agents run on the schedule and instructions the customer sets, after a test run.

Is ServiceJan a lead marketplace?

ServiceJan says it does not sell shared leads. A customer picks one provider and an open time, and the request reaches only that provider as a booked job in its work-order system.

Which field service businesses are these launches aimed at?

BuildOps targets commercial specialty contractors such as HVAC, electrical, plumbing and fire and life safety. Zuper has a dedicated product for roofing and exterior contractors, and ServiceJan serves providers from independents to enterprise organizations.

Conclusion

The November launches from BuildOps and Zuper put AI agents to work on quotes, invoices and follow-ups, while ServiceJan brings new bookings into the scheduling system itself. Before a demo, write down how many quotes went unsent and how many finished jobs went unbilled last quarter. Then ask each vendor to show, on your own data, which of those its agents would have caught and who would have approved each step.