Role guide · Logistics ops · ChatGPT Business · Oct 2026
ChatGPT for logistics ops (Oct 2026): carrier email templates, exception SOPs, and lane cost summaries
Logistics ops role guide — a shared Freight SOPs project in a ChatGPT Business workspace that drafts carrier email templates from a sanitized exception-handling procedure, turns a coordinator's notes into an SOP draft, summarizes lane costs from an aggregated export, and drafts customer delay notices. ChatGPT drafts; the logistics coordinator or transportation manager marks every line that does not match your process and approves it before anyone uses it. Use Projects, not new custom GPTs — OpenAI says custom GPTs are scheduled to retire on December 11, 2026. If your visibility platform or TMS already drafts carrier follow-ups, start there: see FourKites AI or project44 AI.
Who this guide is for
Logistics coordinators, transportation managers, freight analysts, and customer service leads at a shipper, 3PL, or brokerage — the person who writes the carrier follow-up email, keeps the exception-handling procedure current, and explains last month's freight spend — at a company that already pays for ChatGPT Business or Enterprise. If your visibility platform, TMS, or broker tool already sends carrier follow-ups or drafts quotes, use that first: see FourKites AI, project44 AI, Shipwell AI, Uber Freight AI, or Parade AI. Product deep-dive: ChatGPT.
Use Projects, not new custom GPTs. OpenAI's custom GPT retirement FAQ (re-read 17 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 creators will migrate GPTs to plugins. For affected Enterprise workspaces it lists October 26, 2026 (planned) as the end of new custom GPT creation. A project keeps related chats, files, and instructions together, and OpenAI's Projects help article says project instructions apply only inside that project.
Ground rules for every section below: never paste customer PII — consignee names, emails, phone numbers, delivery addresses — and never paste driver names or driver phone numbers, live location trails, full rate files or contract rates, or carrier bank details. Passport or ID scans from a carrier onboarding pack stay out too. Work from sanitized material: the written procedure, lane-level totals, shipment counts by week. ChatGPT does not book or tender a load, accept or offer a rate, send a carrier or customer message, file a customs entry, or change a delivery appointment. The logistics coordinator owns every carrier and customer message, the transportation manager owns every lane and cost conclusion, and driver safety and hours-of-service rules stay with the carrier and dispatcher.
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 Freight SOPs: carrier email template (primary)
What it is: Select New project in the sidebar and name it Freight SOPs. Upload one sanitized exception-handling procedure — for example, what happens when a pickup is missed: who calls the carrier, how long you wait, when the customer hears, when a load is re-tendered — with no customer names, shipment references tied to a person, driver details, or contract rates. In Project settings, add instructions: draft only from the uploaded files; quote the procedure's wording exactly; mark any line you could not source. Then ask for a carrier email template for that exception. OpenAI says Business projects support up to 40 files.
The mismatches are the useful part. If the template threatens a chargeback your procedure does not allow, or promises a re-tender after one hour when your rule is four, that is a commercial decision for the transportation manager — not a writing improvement.
Primary workflow:
Create a Project called Freight SOPs. Upload one sanitized exception-handling procedure and ask for a carrier email template — have the logistics coordinator mark every line that does not match your process.
2. Exception SOP drafts from a coordinator's notes
What it is: Many exception procedures live in one coordinator's head. Ask that person to write rough notes for one exception type — a refused delivery, an OS&D (over, short, and damaged) claim, a missed delivery appointment — and add them to the project. Ask for a numbered SOP with an owner and a time limit on each step, and a list of the questions the notes did not answer. ChatGPT drafts; the transportation manager decides each time limit and who owns each step.
The open questions list is the point. “Who decides whether to re-tender?” is a decision for a person, and the draft should leave it blank until one is named.
List what's missing:
Upload one coordinator's notes on a refused delivery to Freight SOPs and ask for a numbered SOP with an owner and a time limit on each step, plus a list of open questions. Have the transportation manager answer each question before the SOP is used.
3. Lane cost summaries from sanitized exports
What it is: Export lane-level totals from your TMS or freight audit tool — origin region, destination region, mode, shipment count, and total freight cost by month — with no shipment-level detail, no contract rate tables, and no carrier names if your contracts restrict sharing. Upload it and ask for cost per shipment by lane, month over month, with the calculation shown and the ten biggest changes listed. ChatGPT summarizes; the transportation manager checks two of the lanes against invoices before anything is said in a carrier review.
A summary is a lead, not a finding. Fuel surcharges, accessorials, and a one-off expedite can all move a lane's average; the person who owns carrier relationships decides what the number means.
Check two lanes by invoice:
Upload a sanitized monthly lane export (lane, mode, shipment count, total cost) and ask for the ten biggest month-over-month changes in cost per shipment, with the calculation shown. Check two of them against invoices.
4. Customer delay notices a person sends
What it is: Write one approved fact sheet for customer communication — what you say when a shipment is late, what you never promise (an exact delivery time the carrier has not confirmed), who the customer can call, and how you handle claims — and ask for three templates: a short delay notice, a revised delivery window, and a damage claim acknowledgement. Ask it to leave blanks for dates, reference numbers, and names. A named coordinator fills the blanks from the carrier's confirmed update and sends each one.
An ETA is a prediction until the carrier confirms it. The template should say “we expect” and leave the date blank; the coordinator fills it from the carrier's update or the visibility platform.
No promised times:
Write one approved customer communication fact sheet and ask for three delay templates with blanks for dates and references. Have the customer service lead strike any delivery promise that is not on the sheet.
5. Who can see the project
What it is: OpenAI's Projects help article says Business users can share a project with individuals or workspace groups at Edit or Chat access. Edit lets members update instructions, upload or remove files, and invite others; Chat lets them see and use the project's chats, files, and instructions. A workspace project can include up to 100 collaborators, and shared projects automatically use project-only memory — so anything uploaded is visible to everyone you add.
Give edit access to the people who own the procedures (transportation manager, lead coordinator). Give coordinators and customer service chat access.
Two editors, everyone else chat:
Open Share on your Freight SOPs project. Give edit access to the transportation manager and lead coordinator and chat access to everyone else, then list who can see the uploaded files.
6. Plan the move before December 11, 2026
What it is: OpenAI says existing custom GPTs remain usable until retirement on December 11, 2026, that migration is to plugins, that custom actions do not transfer automatically, and that existing GPT conversations stay accessible. If your team already has a custom GPT for carrier emails or exception replies, save a few requests it handles well, put its instructions into a project, and compare results before anyone switches. Do not use the new-custom-GPT flow for freight work — use a project. See OpenAI's retirement FAQ.
Write the comparison down: five familiar requests, the old answer, the project answer, and the lines the coordinator had to fix. A GPT that called your TMS through a custom action needs a separate plan — that connection does not move on its own.
Compare before you switch:
Before December 11, 2026, save five carrier or customer email requests your freight GPT already handled. Move its instructions into a project, rerun them, and compare every line your coordinators mark before anyone switches.
Pricing context (October 2026)
As listed on openai.com/business/pricing and OpenAI's ChatGPT Business overview (checked 17 October 2026): ChatGPT Business Standard seat $20 per user per month billed annually, $25 billed monthly; Premium seat $100 per month billed annually, $125 billed monthly. Business is for teams of 2–200, and a workspace needs at least two seats. OpenAI notes pricing may vary by country and currency. Enterprise is custom pricing through sales. The pricing grid lists Projects and shared projects on Business with no separate line item.
Budget from your invoice. Never put customer PII, driver details, or rate files into a personal ChatGPT account used for freight work.
Uncertainty: OpenAI list prices and seat types change; use the live pricing page and your invoice. Custom GPT retirement dates follow the help center FAQ re-read 17 Oct 2026 (Dec 11, 2026 standard; Feb 11, 2027 approved Enterprise deferral; Oct 26, 2026 planned creation cutoff for affected Enterprise workspaces) — OpenAI says the Enterprise dates are subject to change and your in-product notice wins. OpenAI's Business overview still lists GPTs among Standard seat features; the retirement FAQ is the newer and more specific page.
When it’s useful (honest take)
Useful when your team already pays for ChatGPT Business and needs carrier and customer templates, SOP drafts, and lane summaries with a named coordinator or transportation manager approving.
Less useful when your visibility platform or TMS already drafts carrier follow-ups and exception replies (FourKites AI, project44 AI, Loadsmart AI), or nobody will mark the lines that do not match the procedure.
Paying for ChatGPT and a few other AI tools? The $9 AI toolkit spreadsheet lists every AI subscription you have, what each one costs, and how fast it pays for itself, so you can see which ones are worth the money.
Want someone to do it for you? AI toolkit audit — $19
Related options (educational)
| Need | Better home | Why |
|---|---|---|
| Carrier templates + SOP drafts in a Project | ChatGPT for logistics ops (this page) | Business seats |
| Lane trackers in Sheets, carrier briefs in Docs | Gemini for logistics ops | Workspace Standard+ |
| Carrier follow-ups inside the visibility platform | project44 vs FourKites | Quote-only |
| Exception agents on your loads | Loadsmart AI | Quote-only |
| Ecommerce twin guide | ChatGPT for ecommerce ops | Business seats |
FAQ
Should we build a custom GPT for freight SOPs?
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 ChatGPT email carriers, book loads, or accept rates for us?
Not in this guide. ChatGPT drafts templates, SOPs, and summaries; a named person approves them; carrier and customer emails are sent by a coordinator, and bookings and rates stay in your TMS or broker tool with the transportation manager or carrier sales lead approving.
What goes in the Freight SOPs project?
Sanitized procedures, coordinator notes, approved fact sheets, and aggregated lane exports — no customer PII, driver names or phone numbers, live location trails, full rate files or contract rates, or bank details. Every member you share with can see the files.
How does this differ from ChatGPT for ecommerce ops?
Same Projects pattern; logistics examples are carrier email templates, exception SOPs, lane cost summaries, and customer delay notices — not returns macros or product copy. See ChatGPT for ecommerce ops.
Who approves outputs?
The logistics coordinator for every carrier and customer message; the transportation manager for every SOP time limit, lane conclusion, and anything said in a carrier review; the customer service lead for every customer template.
Optional next step (if seats overlap)
If logistics ops pays for ChatGPT, Gemini, a visibility platform with its own AI analyst, and a TMS assistant that all answer “where is my freight”, map 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).