Skip to content

Track your small business field service jobs with Claude or ChatGPT (2026)

A small business’s field jobs are often tracked with a spreadsheet schedule, calls to the technician and paper job sheets typed up in the evening. Your AI can build you a tool where the technician sees their day on their phone, takes photos, gets the customer to sign, and the report goes out on its own. Here is how.

By Aloïs Oddon, co-founder of Nextmap. Facts checked on November 18, 2026.

View as Markdown

Field service management for a small business with a tool built by Claude or ChatGPT: the technicians' schedule, the job on the phone with photos and the customer’s signature, and the service report sent, on while

In many small businesses, field service management lives in a spreadsheet schedule, calls to the technician to find out where they are, and paper job sheets typed up in the evening. Photos stay on phones, the customer’s signature gets lost, and the invoice goes out two weeks late.

Your AI can now build you a tool where the technician sees their day on their phone, takes photos and gets the customer to sign, and the report goes out on its own.

The short version. Describe your job types, what the technician records and what the customer receives to Claude or ChatGPT, and ask it to put the tool on while. The office schedules, the technician fills in everything from their phone, and the report goes to the customer with the photos.

What a field service tool needs to track

A job fits in a few things, which is what lets the technician fill it in on site, in two minutes.

What you trackWhat goes in
The jobThe customer, the address, the type, the date and the technician
On siteArrival and departure times, what was done, the parts used
The proofBefore and after photos, the customer’s signature
What comes nextThe report sent, the job to invoice, a new visit if needed

Reuse the paper job sheet you already have: your AI turns it into a form, and your technicians find the boxes they know.

Build the tool with your AI, in five steps

The tool takes one conversation, and you have no code to write.

  1. Describe your jobs. The types, what the technician must record, the usual parts.
  2. Ask for the technician’s screen. Their day on their phone, the address, the photos and the customer’s finger signature.
  3. Ask for the office schedule. The week’s jobs by technician, with drag and drop to reassign.
  4. Put the tool on while. Your AI puts it there, and it has its address in a few minutes. Without a while account, it does so as a trial, for free, and gives you a link to keep it.
  5. Add the sends. The report to the customer at the end of the job, and the next day’s schedule to each technician, every evening.

You, to your AI: Build us a field service tool: the office schedules, each technician sees their day on their phone, records what they did and the parts, takes photos and gets the customer to sign. The report goes to the customer with the photos. Put it on while, kept for the team.

The path of a field service job in a tool built with AI: the office schedule, the technician's day on their phone, photos and the customer's signature, then the service report sent and the job ready to invoice
From schedule to invoice, the job follows a single path.

What while brings to your field service

Field jobs go through phones, customers and photos. This is the kind of tool we built while for.

  • Each technician signs in from their phone. With a while account for up to 3 people, or, on the Pro plan, with their email account, Google or Microsoft, with no per-person price. See keep a tool for your colleagues.
  • The customer follows their jobs. They view them with an access link and a password, valid for 1, 7 or 30 days, with no account to create.
  • Photos stay with the jobs. The data is backed up every day, with a way back over 14 days, once a person approves.
  • Sends go out on their own. The tool runs its automations at set times, and can alert the team in Slack.

If the tool needs to read your invoicing software, like Axonaut, its credentials stay in while, out of your AI’s sight. Your tools are hosted in France by Nextmap.

When off-the-shelf field service software is a better fit

A tool built with AI suits a small business with a few technicians. If you need to optimize routes, work offline in dead zones, track each van’s stock or coordinate dozens of technicians, off-the-shelf field service software will save you time.

For more small business tools built with AI, see the production schedule and the inventory tracker.

Try it on your field jobs

Give this message to your AI, then describe your jobs. The trial is free, with no sign-up, and your tool has its address in 3 minutes.

The message to give your AI
Read while.sh/agents and help me get started with while.

Questions

Can you build field service software with ChatGPT or Claude?

Yes. You describe your job types, what the technician must record and what the customer receives, and your AI builds the tool. On while, each technician uses it from their phone.

Can the technician take photos and get the customer to sign?

Yes. Ask your AI for before and after photos, and a finger signature on the screen: they are kept with the job.

How does the customer receive the service report?

An automation sends the report at the end of the job, with the photos. The customer can also follow their jobs with an access link and a password.

How do you prepare the invoice from the jobs?

The tool counts the time spent and the parts used, and your AI exports the completed jobs at the end of each month for invoicing, or sends them to your invoicing software.

When is off-the-shelf field service software a better fit?

When you need route optimization, working offline in dead zones, each van’s stock or dozens of technicians. A tool built with AI suits a small business with a few technicians.

Give your AI the message, and it takes care of the rest

Give this to your AI

Read while.sh/agents and help me get started with while.

Copy the message

In 3 minutes, with no sign-up, the tool has its own address. To keep it, create your account.

For a company project, write to the while team: hello@while.sh