Independent work sample, built for one real business
Barberton Tree Service: a place for every open promise to live until it's kept
The company's own BBB complaint file shows a narrow, repeated pattern behind a strong overall reputation: a crew arrives without prior notice, or damage is reported, and then a promised callback or "someone will come out" does not happen until the customer escalates. The business's own site (a Wix build) has no booking, scheduling, or CRM tool of any kind, just a phone number and two mailto links, so there is nowhere for that kind of promise to live except in someone's memory. This example shows a small tool that gives every open promise a due date and a place for a customer to check on it themselves.
Barberton Tree Service, Inc.Barberton / Norton, OH, since 1971Residential, municipal & commercial tree service
Independent work sample, not affiliated with or endorsed by Barberton Tree Service, Inc. All customer names, jobs, and promises inside the tool below are fictional and clearly for illustration only. The business description, history, and complaint pattern referenced here are drawn from the company's own published site and from its public BBB complaint file.
Barberton Tree Service carries a strong aggregate reputation (4.7 stars across 854 reviews on Birdeye, mostly positive Yelp reviews) and has been a BBB Accredited, A-rated business since 2006 over its 55 years in business. The gap this tool targets is narrow and specific, not a sign of a business in trouble: three answered BBB complaints from 2024 to 2025 describe crews entering a yard or starting work without notice, and property-damage reports (a vinyl gate on two separate occasions, an ornamental spruce mistakenly removed) followed by a promised callback that did not come until the customer followed up again. A separate review found independently describes the same shape on a different job. The company is also actively hiring (an arborist role and a groundsperson role with a sign-on bonus currently posted), which raises rather than lowers the odds that admin follow-through, not crew capacity, is the bottleneck.
Log a new promise
Open queue, most overdue first
Check the status of a promise
Try BTS-1001, BTS-1002, BTS-1003 or BTS-1004 from the office view's sample queue.
How this gets built for real
The reference code can be whatever the office already writes down. A real build reads from an existing work-order or claim reference instead of asking a customer to remember a new code.
This does not replace crew scheduling. It sits on top of however jobs already get dispatched, and only tracks the specific promise: a callback, a damage claim, or a next-day arrival window.
The customer view shows only customer-safe wording. Internal notes typed in the office view (like who is handling a claim) never appear on the lookup page.