Independent work sample, built for one real business

Irish Roofers Dublin: a place for every promised return visit, callback, or invoice request to live until it's kept

Irish Roofers Dublin's own Google Business reviews describe a repeated shape underneath an otherwise strong 4.9-star record: a return visit, a callback, or an invoice is promised, and it then depends on one staff member remembering to follow through rather than on any shared record. The company's own site has a quote-request contact form only, no scheduling portal, customer account, or job-tracking login anywhere. This example shows a small tool that gives every open promise a due time, an automatic overdue flag sorted worst-first for the office across three locations, and a no-login reference-code lookup so a customer can check status without starting the call over.

Irish Roofers Dublin Northside, Southside & Dublin City offices, since 1970 Roofing, chimney repair, guttering & skylights, Greater Dublin

Independent work sample, not affiliated with or endorsed by Irish Roofers Dublin. All customer names, jobs, 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 Google Business reviews and an independent third-party review roundup.

Irish Roofers Dublin holds a 4.9-star average across 326 Google reviews, but a small number of the negative ones share a pattern: a chimney leak repair that a customer says was still leaking five months later, after being ignored on repeated calls and never sent an invoice despite asking for one; a second customer who spoke with a staff member about a repair and says he "never heard anything back" and switched to a competitor; and an independent third-party roundup that separately flags wrong fittings used on rush jobs. The company's own testimonials page shows follow-up working well when one particular staffer happens to chase it personally, which is exactly the kind of thing a shared queue makes reliable instead of personality-dependent. Checked directly against the company's own site: no service, portal, or job-tracking page exists anywhere on it today, and everything runs through one shared phone line and a contact form.

Log a new promise

Open queue, most overdue first

Check the status of a promise

The same lookup an office staffer uses on an incoming call to answer "is this actually scheduled," or that a customer could use directly, by whatever job reference number they were already given.

Try IRD-2001, IRD-2002, IRD-2003 or IRD-2004 from the office view's sample queue.

How this gets built for real

This replaces nothing, it fills a real gap. The company's own site has no service, portal, or job-tracking page today, so a real build gives all three offices their first shared view of open promises instead of competing with an existing system.
The reference code is whatever the office already writes down. A real build reads from an existing job or quote reference 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 staff can look up a call without exposing internal handling notes.
Back to the general template: Follow-up promise tracker.