ChatGPT for field service ops (Oct 2026): quote drafts, dispatch notes, and job-checklist help

Who this guide is for

Field-service coordinators — the dispatcher who cleans notes before the next tech rolls, the office lead who drafts quote outlines from the pricebook, the service manager who wants a checklist from an approved SOP — whose company already has ChatGPT Business (formerly ChatGPT Team; OpenAI renamed it on August 29, 2025) or Enterprise. If your FSM already drafts quotes and summaries inside the product, see Dynamics 365 Field Service AI, Salesforce Field Service AI, Jobber AI, or ServiceTitan AI. For fleet coaching, see Samsara vs Motive. Product deep-dive: ChatGPT.

Use Projects, not new custom GPTs. OpenAI’s help center (read 12 October 2026) says custom GPTs are scheduled to retire on December 11, 2026 (February 11, 2027 for Enterprise workspaces with an approved deferral), that the change affects all ChatGPT plans, and that it plans to help creators migrate GPTs to plugins. For affected Enterprise workspaces it lists October 26, 2026 (planned) as the end of new custom GPT creation. Putting field-service instructions in a project keeps related chats, files, and instructions together and costs nothing extra on qualifying plans.

Ground rules: ChatGPT never invents prices. Quote outlines come only from a sanitized pricebook page you upload, and any line not on that page is marked, not filled in. Never paste customer PII — names, phone numbers, addresses, payment details, or a tech’s notes about a named household. The service coordinator or manager approves every quote outline and every customer-facing dispatch note before it leaves the office. An AI-drafted checklist is not a licensed technician’s judgment.

Major features (with how someone uses them)

Examples at a glance: each feature has a concrete example from a real job plus a short Try this you can run this week.

1. Project field-service drafts: quote outline (primary)

What it is: Select New project in the sidebar and name it Field-service drafts. Upload one sanitized pricebook page — SKUs, descriptions, and list amounts only; no customer names. In Project settings, add instructions: write quote outlines only from the uploaded page; put the SKU or line label after each item; if a line is not on the page, mark it “Not on the pricebook — do not quote” and do not invent an amount; never add a discount, tax, or fee that is not on the page. OpenAI says project instructions apply only within that project and override your global custom instructions, and Business projects support up to 40 files.

The marked lines are the useful part. If ChatGPT wants to add a “trip charge” that is not on the page, that is not a quote problem — it is a pricebook gap the manager should know about before anyone sends numbers to a customer.

Concrete example (office coordinator at a plumbing shop) She uploads one sanitized drain-clearing pricebook page and asks for a quote outline for a standard main-line clear. Four lines match SKUs on the page; a fifth “camera inspection add-on” is marked not on the pricebook. The service manager adds that SKU to the pricebook first, then approves a four-line outline for the FSM.

Try this

Primary workflow:

Project field-service drafts. Upload one sanitized pricebook page. Ask for a quote outline and mark any line it invents that is not on the page.

2. Dispatch note cleanup without PII

What it is: Paste a sanitized dispatch note — job type, site type (commercial/residential), symptoms, parts on the truck — with names, phones, and street addresses removed. Ask ChatGPT to rewrite it as a clear handoff for the next tech: what was tried, what is still open, and what to bring. The coordinator checks every fact against the FSM work order before the note is saved.

If the model adds a part, time, or promise that is not in the sanitized note or the work order, delete it. Cleanup is not license to invent.

Concrete example (dispatcher) A tech leaves a messy note about a no-cool call. The dispatcher removes the customer name and address, pastes the rest, and gets a clean handoff. ChatGPT added “capacitor replaced” — it was not in the note — so she deletes that line before saving to the FSM.

Try this

Sanitize first:

Take one messy dispatch note, remove names and addresses, and ask for a clean handoff. Delete any part or promise the model adds that was not in the note.

3. Job checklists from an approved SOP

What it is: Upload one approved, current SOP or inspection procedure (the version the service manager signed off). Ask for a job checklist with a source step for each item, and a list of anything a tech would need that the SOP does not cover. The service manager reviews the checklist before it is added to a work-order template in the FSM.

Cross out any checklist step without a source in the SOP. Gaps go back to the procedure owner — sometimes the honest answer is that the SOP needs writing first.

Concrete example (service manager building templates) He uploads the approved rooftop startup SOP and asks for a 10-step checklist. Eight steps cite SOP sections; two about lockout tagout are marked not in the SOP. He updates the SOP first, then publishes the checklist to the FSM.

Try this

Source every step:

Upload one approved SOP and ask for a job checklist with a source step for each item. Have the service manager cross out anything it cannot source.

5. What never goes in: customer PII and live prices from memory

What it is: OpenAI says it doesn’t train on ChatGPT Business, Enterprise, or Edu workspace data by default, and its Business pricing page lists SAML SSO and SOC 2 Type 2. That does not make a project the right place for customer data. Keep out names, phones, street addresses, payment details, gate codes, and a tech’s free-text about a named household. Also keep the model from “remembering” prices — every amount must come from the uploaded pricebook page for that chat. The pricing page lists SCIM, role-based access controls, the Compliance API, and data residency for Enterprise, not Business.

Concrete example (compliance-minded service manager) He writes three rules at the top of the project instructions: only sanitized pricebook pages and approved SOPs go in; no customer PII ever; and no outline reaches a customer until a named coordinator checks every line against the pricebook. When a tech asks to “paste the whole ticket,” he redirects them to the FSM.

Try this

Write the three rules:

Write three rules for your field-service project — what may go in, what never goes in, and who approves anything that reaches a customer — and paste them at the top of the project instructions.

6. If you already have a field-service GPT

What it is: OpenAI says existing custom GPTs keep working until retirement on December 11, 2026, that migration is to plugins (My GPTs → Migrate to plugin when it reaches your account), and that the GPT’s instructions become a skill and its knowledge files become reference files. The selected model, custom actions, and sharing settings don’t carry over; migration uses the latest published version; the original becomes read-only; and the new plugin starts private. Chats created with a GPT can’t be moved into a project. Existing conversations stay accessible after retirement.

For a quote-outline GPT, the simplest move is often a project: copy its instructions into Project settings and upload the same sanitized pricebook. Test with the same requests and check that the “Not on the pricebook” rule survived — a replacement that invents trip charges is worse than the GPT it replaced.

Concrete example (office lead with an old quote GPT) An office lead has a Quote helper GPT from last year. She saves five outline requests it handled, copies its instructions into Field-service drafts, uploads the current sanitized pricebook, and reruns them. One outline now invents a Saturday fee; she tightens the instruction and reruns before telling colleagues to switch.

Try this

Test the replacement:

Before December 11, 2026, save five quote-outline requests your field-service GPT already handled. Move its instructions into a project, rerun them, and compare every marked line before anyone switches.

Pricing context (October 2026)

OpenAI’s Business pricing page (as listed 12 Oct 2026, USD): Standard seat $20 per user per month billed annually or $25 billed monthly; Premium seat $100 per user per month billed annually or $125 billed monthly, with 5x the usage of Standard and no 5-hour limit. A Business workspace needs at least two seats and is for teams of 2 to 200; API usage is billed separately. Enterprise is priced through sales.

OpenAI’s Projects help article says projects cost nothing extra on qualifying plans. Pricing may vary by country and currency. Full dated notes are on the ChatGPT deep-dive.

Uncertainty: OpenAI says its retirement dates are subject to change and that migration may reach accounts at different times; the October 26 creation cutoff is listed for affected Enterprise workspaces. Project limits (40 files, 100 collaborators on Business) and memory behaviour come from the help center and can change. Skills is labelled beta on the pricing page. Nothing here replaces your pricebook: if a line is not on the uploaded page, the service manager decides, not ChatGPT.

When it’s useful (honest take)

Useful when your company already pays for ChatGPT Business or Enterprise, you have a sanitized pricebook and approved SOPs with named owners, and someone owns the project’s instructions and files.

Useful when coordinators want first-draft quote outlines and checklist drafts they can check against a source, without putting customer PII into a general chat tool.

Less useful when your FSM already drafts quotes and summaries from the live pricebook (Dynamics 365 Field Service AI, Jobber AI), the pricebook is not written down, the team cannot keep customer PII out, or anyone expects ChatGPT to invent a price.

Related options (educational)

FAQ

How should a field-service team set up ChatGPT?

In a Business or Enterprise workspace, create a project (for example, Field-service drafts), upload one sanitized pricebook page, and add project instructions: outline only from the page, cite the SKU, mark anything not on the page, and never invent a price. Share it at chat access and have the service manager approve every outline.

Should we build a custom GPT for quote outlines?

Not a new one. OpenAI says custom GPTs are scheduled to retire on December 11, 2026 (February 11, 2027 for Enterprise workspaces with an approved deferral) and plans migration to plugins. Use a project instead; if you already have a GPT, save test requests and compare the replacement before switching. See OpenAI’s retirement FAQ.

Can we paste customer tickets into the project?

Don’t paste names, phones, addresses, payment details, or gate codes. Sanitize dispatch notes first. Customer records belong in your FSM and CRM, not in a general chat tool.

Who can see files in a shared project?

Everyone you add can view and download the uploaded files, whether they have edit or chat access, OpenAI says. Edit access also allows changing the instructions and files and inviting people; chat access only allows using the project, which keeps its own project-only memory. See Projects in ChatGPT.

What does ChatGPT Business cost in October 2026?

As listed on 12 October 2026: Standard seats $20 per user per month billed annually or $25 monthly, and Premium seats $100 annually or $125 monthly with 5x the usage, for teams of 2 to 200. Projects cost nothing extra. See openai.com/business/pricing.

Optional next step (if seats overlap)

If field ops pays for ChatGPT, an FSM with its own Copilot or Agentforce, and a separate quoting tool that all draft from different copies of the pricebook, fix that overlap before adding another seat. Map the overlap with the $19 AI toolkit audit or the $9 AI toolkit spreadsheet. Email Audit $19 or Toolkit spreadsheet $9.

Checkout is live via Stripe. After you pay, we email delivery (spreadsheet) or intake next steps (audit).

Related: ChatGPT · ChatGPT for ops · Dynamics 365 Field Service AI · MaintainX vs UpKeep · Samsara vs Motive · Dynamics 365 Field Service AI · Jobber AI · ServiceTitan AI · Claude Projects · Custom GPTs · What’s new in ChatGPT (Sep 2026) · MaintainX vs UpKeep · Samsara vs Motive · Stack map for IT ops · Three checks before another AI seat · ops hub