IT that keeps bobtails rolling, homes warm, autopay running.IT that keeps bobtailsrollinghomeswarmautopayrunning
Delivery software, telemetry and customer payments ready for the cold snap, with backups tested before the first freeze.
Propane dealer IT
Winter doesn't wait for your server to reboot
Most of the year your office runs at a steady pace. Then the temperature drops, call volume jumps, and every delivery route depends on software, telemetry and a phone system working at full load. Here's what propane dealers depend on, how things go wrong, what we put in place and what next winter looks like.
01 · The pressure
Every route starts with a tank reading and a customer record
Your dispatcher builds routes from telemetry readings, degree-day forecasts and will-call orders. Drivers carry tablets that print delivery tickets and record safety checks. The office answers a flood of calls from customers who think they're running low, while billing processes autopay drafts and budget plan payments. During a cold snap, losing delivery software or the phone system for a day means homes without heat, a backlog you can't catch up on and customers who switch dealers.
- Telemetry and degree-days drive every route
- Call volume spikes the moment temperatures drop
- Autopay and budget billing hold card and bank data
Cargas EnergyADD SystemsTank UtilityOtodataAnovaSamsara
02 · How it breaks
One office PC, one password, one bad click
Propane offices are often small, and that's where the risk hides. The billing server lives in a closet and its backup is a USB drive nobody has tested. Several staff share one login to the delivery software. A customer service rep opens an attachment pretending to be a tank telemetry alert. The customer portal vendor's admin account has no MFA. Old card numbers sit in a spreadsheet someone made years ago to handle declined autopay drafts.
- Untested backups of the billing server
- Shared logins to delivery and billing software
- Stray card numbers kept outside the payment system
Cargas EnergyADD SystemsTank UtilityOtodataAnovaSamsara
03 · What we change
Named access, clean card handling, tested restores
We give each person their own account with MFA in Microsoft 365 and, where supported, in your delivery and billing software. Card data moves out of spreadsheets and into your payment processor's tokenized storage, with the office network segmented from payment devices. Bobtail tablets get device management. Billing and delivery data get immutable offsite backups that we restore as a test each fall, before heating season. Endpoint detection and email filtering cover every office PC.
- Tokenized autopay instead of stored card numbers
- Managed bobtail tablets that can be wiped remotely
- A pre-season restore test every fall
Cargas EnergyADD SystemsTank UtilityOtodataAnovaSamsara
04 · The after
Heading into winter knowing recovery works
Once this is in place, the busy season is about gallons and routes, not technology. If the billing server fails in January, you know how long a restore takes because you watched one in October. A lost tablet doesn't expose customer addresses. When your insurer asks about MFA and backups, or your processor asks about card storage, you answer with facts. Your customers' payment details sit with the processor, not in a forgotten file on someone's desktop.
- Known recovery time before the first freeze
- Customer card data held only by the processor
- Clear answers for insurers and your processor
Cargas EnergyADD SystemsTank UtilityOtodataAnovaSamsara