Your customer’s surface, your brand.
The customer portal is the fourth surface of the platform. Same database as the dispatch board, same database as the AR ledger, white-labeled per brand. A customer who buys propane from one of your brands and heating oil from another logs into each portal under each brand’s URL with its own logos, its own Service Plan PDFs, its own support email and phone. The operator sees one customer across both. The customer sees the brand they bought from.
Request a delivery
The +Delivery Request flow walks the customer through their own systems. Pick the system. Write a message or notes. Enter a requested volume. Choose a window. The portal shows the current quoted price. A credit-card hold amount surfaces if the brand requires one. A Charge Card toggle converts the hold to an immediate charge at submit.
The request lands on the Fuel Map in the back office and on the Customer Dashboard for the office staff. The customer sees it as a line item with Date, driver, expected gallons, delivered gallons, per-gallon price, total, and status. Unprocessed orders are cancelable from the same row.
Pay how the customer wants to pay
The Add Payment Card popup takes full billing details, card number, expiration, and CVV. The card is available in the same session, so a customer can add a card and run a deposit charge in one sitting. No invoice required for the deposit.
AutoPay toggles per service. Fuel can autopay on one card, service on another, the service plan subscription on a third. Each card lives independently. A denied card surfaces as a notification the office and the customer both see.
Quotes and Proposals
When a proposal flips to visibleAt in the back office, it appears in the portal. The customer reads the scope, reviews the materials, signs the PDF, and the office watches the status move from Sent to Signed without a phone tag chain. Optional scopes carry the upsell. Closure reasons capture the why on either outcome.
Know what they’re paying for
History
Per-system usage rates, delivery windows, the pattern that shaped the most recent fill. Customers who ask why a delivery came when it did have the answer on their own screen.
Pricing
System-specific pricing transitions, active services, contracts, and a recent delivery graph. Cap and fixed contracts surface where they apply. The customer sees the line, not the office’s spreadsheet.
Onboarding from the customer side
A customer-facing wizard mirrors the back-office Onboarding Wizard. Services, systems, credit cards, all in sequence. New customers self-serve through it. The record on the office side is real after the first step.
White-label, per brand
Per-brand company name, tagline, Portal URL, light and dark logos, favicon, support email, support phone, Oil and Propane Service Plan PDFs. The portal looks like the brand the customer bought from. If you run two brands or six, every customer sees the one they belong to.
Payments under the hood
Portal payments flow through Kozy Payments, the in-house processor with an NMI gateway underneath. The ledger integration handles partial refunds, chargebacks, and deposit reconciliation with settlement timestamps end-to-end. Read more on /payments
Who lives here
Your customers. The ones who want to pay a bill at ten at night. The ones who want a delivery without a phone call. The ones who want to know what they paid last winter before they sign a cap contract for next winter. The portal hands them that without pulling a dispatcher off the route board.
The office side of all this lives in the web back office. The field side lives in KozyServiceman.