Working example, built around Midgleys' own published facts
A paid fireplace install shouldn't sit unscheduled until a customer files a complaint
Right now, a customer who orders and pays for a fireplace, stove or insert install has one option to check status: call the shop and ask. There is a "Service Request" form on midgleys.com, but it gives no confirmation ID and no status check, and a public BBB complaint on file (filed 01/30/2026) shows exactly this gap in practice: a customer paid in full on October 16, faced repeated scheduling delays, installation was finally attempted December 3, and completion was still pending 02/06/26 with the delay only surfaced after the customer complained. Below is a working tool sized to close that specific gap: every paid job gets a ticket that moves through Received, Scheduled, Installation in progress and Completed, a simulated status email fires on each change, and any paid job stalled past a set number of days is flagged before it becomes a complaint.
Everything below is fictional. Customer names, job details and dates on this page are sample data, illustrative only, not Midgleys' real customer or job records. One sample job below is deliberately shaped to mirror the timeline pattern described in the public BBB complaint (paid, then stalled for months before installation) to make the "needs attention" flag concrete, not because it reflects a real Midgleys customer.
Roger Oberg · GMDeanneFarrenDai Hogan · Scheduler
days with no stage change
Log a new job
Roger, Deanne, Farren and Dai all see this same queue at once, no separate login or handoff needed.
Shared job queue, flagged jobs first
Check the status of a paid order
Try MID-1001, MID-1002, MID-1003 or MID-1004 from the team view's sample queue. Replaces calling the shop to ask "where is my install."
How this gets built for real
The order number is whatever Midgleys already hands out. A real build reads from the existing paid-order or invoice number instead of inventing a new one for the customer to remember.
The status email here is a log entry, not a real send. A real build wires this to Midgleys' existing email so the ping actually reaches the customer the moment a stage changes.
This does not replace Dai's scheduling judgment. It only makes the paid-but-not-yet-scheduled and paid-but-stalled cases visible to the whole team automatically, instead of surfacing only when a customer calls or a complaint is filed.