Template, not built for a specific business

Every "someone will call you back" promise, visible until it's kept

A crew tells a customer someone will come out, or the office says a damage report is being looked into, and then it lives only in one person's memory or a sticky note. When that person is busy the promise quietly slips, the customer calls back annoyed, and it looks like the business does not follow through even when the actual work is good. This page shows one small, working tool that fixes that: an internal queue that surfaces every open promise sorted by how overdue it is, and a customer-facing status page so a customer can check where things stand without calling the office first.

Everything below is fictional. When this gets built for a real business, the office view is what staff actually use to log and close out promises, and the reference code on the customer view is whatever the office already hands out (a work order number, a claim number), not a new system to adopt.

Log a new promise

Open queue, most overdue first

Check the status of a promise

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

How this gets built for real

The reference code is whatever the office already uses. A real build reads from an existing work-order or claim number instead of inventing a new one for the customer to remember.
Overdue math here is a simple timer. A real build can page or text the person responsible once something crosses overdue, instead of relying on someone opening this page.
The customer view shows only customer-safe wording. Internal notes stay in the office view; nothing typed there is exposed on the lookup page.
See it built for real businesses: Barberton Tree Service, Arrow Auto Glass, Fabian Oil, 4US Moving, Budget Heating, Cooling & Plumbing, The London Removal Company, Dallas Automatic Gate, Floorguard, Inc., The Window Depot, LLC, Britannia Double Glazing Ltd, Hot Tubs, Inc. and Irish Roofers Dublin.