Independent work sample, built for one real business

Fabian Oil: a place for every promised callback, bid response, or part-arrival follow-up to live until it's kept

Fabian Oil's own BBB complaint file and its BBB customer reviews page describe the same repeated shape: a customer is given a specific promise, a callback time, a bid response date, a call when a part arrives, and the promise silently fails with no proactive follow-up, so the customer has to re-chase the company from zero. The company already has a full account portal for billing and request intake and an internal dispatch system for routing trucks and technicians. Neither one shows what happens to a promise after it is made. This example shows a small tool that gives every open promise a due time, an automatic overdue flag, and a place a rep or customer can check without starting the whole conversation over.

Fabian Oil, Inc. Oakland, ME, since 1988 10 branches, heating oil, propane & HVAC service across Maine

Independent work sample, not affiliated with or endorsed by Fabian Oil, Inc. All customer names, tickets, and promises inside the tool below are fictional and clearly for illustration only. The business description and complaint pattern referenced here are drawn from the company's own published site and from its public BBB complaint and customer review pages.

Fabian Oil carries a strong overall reputation, not accredited but BBB A+ rated with 5 complaints in the last 3 years and every one answered or resolved, plus 3.9 out of 5 across 84 aggregated Google reviews. The gap this tool targets is narrow and specific, not a sign of a company in trouble: a January 2024 BBB review from a 25-year customer describes requesting a furnace bid, being told he'd hear back by a set date, and getting nothing for four months despite follow-up calls; a January 2026 BBB complaint describes an emergency no-heat call promised a callback "by 5pm" that never came, with the company later saying no ticket had been put in for emergency service; a December 2025 BBB complaint describes a technician who diagnosed a part, promised a call when it arrived, and then went silent through a week of daily follow-up calls even after the manufacturer confirmed the part was in stock. The company already runs a MyFuelPortal account portal for billing and request submission and an internal Cargas Energy dispatch system for routing; neither surfaces a live ticket stage or an overdue flag once a promise has been made.

Log a new promise

Open queue, most overdue first

Check the status of a promise

The same lookup a customer-care rep uses on an incoming call to answer "is there actually a ticket for this," or that a customer could use directly, by the reference number already given out.

Try FBO-1001, FBO-1002, FBO-1003 or FBO-1004 from the office view's sample queue.

How this gets built for real

This sits beside MyFuelPortal and the internal Cargas Energy dispatch system, not instead of them. A real build tracks the specific promise a rep or technician makes, it does not replace how requests get submitted or how trucks and techs get routed.
The reference code is whatever dispatch or customer care already writes down. A real build reads from an existing work order, delivery ticket, or service call number instead of inventing a new one.
The status lookup shows only customer-safe wording. Internal notes typed in the office view stay in the office view, so a rep can look up a call without exposing internal handling notes.
Back to the general template: Follow-up promise tracker.