A customer calls Monday morning saying they never received Friday’s delivery. Your driver remembers the stop. The truck meter shows product was dropped. But the ticket is hard to read, the delivery time is unclear, and the office has to hunt through paper files while the customer is waiting.
That is how a routine question turns into a collection problem. To prevent fuel delivery disputes, you need more than a driver saying, “I was there.” You need a clean, consistent record of what was scheduled, what was delivered, where it went, and what happened at the account before and after the stop.
For fuel oil and propane dealers, good records are not extra office work. They are part of protecting revenue, keeping customers confident, and getting trucks back on the road instead of tying up staff on avoidable phone calls.
Why Fuel Delivery Disputes Happen
Most disputes do not start because a customer is trying to avoid a bill. They start because the customer sees something that does not match what they expected. A tank still looks low. A delivery shows up on a day they were not home. The invoice amount is higher than they anticipated. Or they believe they called to cancel and cannot see why the truck came anyway.
The office may have the right answer, but it is hard to give a convincing answer when information is spread across handwritten tickets, separate notebooks, dispatch boards, voicemail messages, and accounting software. Time passes, memories fade, and a simple question becomes a disagreement about facts.
There are cases where the customer is right, too. A driver may have gone to the wrong address, a dispatch change may not have reached the truck, or an account may have an outdated tank size. The goal is not to make every complaint disappear. The goal is to find the facts quickly, correct real mistakes, and stand behind valid deliveries with confidence.
Prevent Fuel Delivery Disputes With a Complete Account Record
The first defense is an account record your whole team can trust. Before a truck is dispatched, the customer record should clearly show the service address, delivery instructions, tank information, access notes, payment status, and delivery preferences.
A customer may use one mailing address and have fuel delivered to another location. A propane account may have a locked gate, a dog on the property, or a specific contact person for access. A heating oil customer may have two tanks or a fill location that is not obvious from the driveway. Those details should live in the account record, not in one driver’s memory or on a sticky note in the office.
Delivery history matters just as much. When a customer questions a delivery, the person answering the phone should be able to see recent gallons, dates, prior usage, and any notes connected to the account. If the customer says, “We just had a delivery,” you can check the history before sending another truck or creating an unnecessary emergency call.
Accurate records also help when a customer claims they were skipped. If an automatic account was scheduled based on degree days or calendar days, the scheduling history gives the office a practical explanation for why the delivery was planned. It may not settle every concern by itself, but it replaces guesswork with a clear operating record.
Make the Delivery Ticket Your Proof
The delivery ticket is often the document that decides a dispute. It should be legible, complete, and available when the office needs it. A ticket with only a customer name and a handwritten gallon number leaves too much open to question.
At a minimum, your delivery record should show the account and service address, date and time of delivery, product and gallons delivered, driver information, and any relevant notes. If your process captures a tank reading, delivery confirmation, or customer signature, make sure staff use it consistently.
Consistency matters more than adding every possible field. Requiring drivers to write detailed notes at every stop can slow down a busy route and create rushed, poor-quality entries. But when something is out of the ordinary, the driver should document it. Examples include a blocked fill, a partial delivery, an unlocked cap, a customer request at the door, or a delivery made after a gate was opened.
A printed ticket can still work if it is organized and returned to the office promptly. The weak point comes when tickets sit in a truck for days, get filed late, or must be deciphered after a customer calls. Digital dispatch and ticket records reduce that gap because the office can see delivery information without chasing paper.
Keep Dispatch Changes in One Place
A large share of disputes comes from changes, not standard deliveries. A customer calls to request a delivery, cancel one, change a credit card, or report that the driveway is inaccessible. If the message stays on a desk pad or in an employee’s personal notes, it may never make it into the day’s route.
Build a simple rule: every call-in order and every delivery change goes directly into the customer record. The dispatcher should be able to see whether the account is on automatic delivery, whether a ticket has already been printed, and whether the truck has already left for that area.
This also helps your office set honest expectations. If a customer calls at 3:30 p.m. and asks to cancel a stop scheduled for that afternoon, do not promise a cancellation until you know the truck’s status. A short, accurate answer is better than creating an expectation the driver cannot meet.
When a change is made, record who took the call and what was requested. You do not need a novel. A note such as “Customer called 10:12 a.m., requested delivery after Friday” can settle a question weeks later.
Match Scheduling to How the Account Is Served
Automatic delivery can prevent run-outs and reduce last-minute calls, but it must be managed with current account information. Degree day scheduling works well for many heating oil accounts because it responds to actual weather conditions. Calendar day scheduling may be the better choice for certain propane accounts, stable commercial usage, or customers with predictable patterns.
Neither method is set-and-forget. A new furnace, a vacant home, a seasonal property, a tank replacement, or a change in occupancy can alter usage. Review exceptions before they turn into surprise deliveries or missed deliveries.
For will-call customers, make the policy plain. If the customer is responsible for monitoring the tank, the account should be marked correctly and the office should avoid treating an old call-in pattern as an automatic delivery instruction. The distinction protects both sides: customers know what to expect, and your staff knows which accounts belong on the route.
Answer Complaints With Facts, Not Defensiveness
When a customer disputes a delivery, the first response sets the tone. Do not start by telling them the driver would never make a mistake. Start by saying you will review the delivery record and call them back with what you find.
Then check the account record, dispatch notes, ticket details, recent delivery history, and payment status. Look for the full picture. A customer who says the tank is empty may have a separate issue, such as a gauge problem, a leak, higher-than-normal usage, or a delivery that was limited by credit or access conditions.
If the delivery was correct, explain it plainly: the delivery date, number of gallons, and any relevant details from the ticket. If your records show a weak spot, own it quickly. A prompt correction is usually less expensive than a prolonged argument, a chargeback, or a lost account.
Train office staff not to speculate. Saying “Maybe the driver went to the wrong house” before checking records can make a customer more suspicious. Saying “Let me verify the ticket, route, and account notes” shows that you have a process.
Use Software to Reduce the Gaps
The right fuel delivery software keeps customer records, scheduling, call-in orders, delivery history, tickets, payments, and accounting work connected. That means the person who answers the phone is not switching between files to determine whether a delivery occurred or what the customer requested.
Degree Days Online was built around these day-to-day fuel delivery workflows. It gives dealers one place to manage automatic scheduling, print delivery tickets, record customer details, update local temperature data, handle call-ins, and reduce duplicate entry between dispatch and the office.
Software will not replace good drivers or good judgment. It does make it much harder for important details to disappear between the phone call, the dispatch desk, and the truck.
A disputed delivery is easiest to resolve when the answer is already in the record. Build that habit before the next cold snap, when the phones are ringing, drivers are moving, and nobody has time to search through yesterday’s paperwork.