What actually stops the 2am "the site is broken" calls after a client handoff?
Three years of contract builds and every launch has the same tail: a fortnight of calls that start with "the site is broken".
When I actually look, maybe one in six is a bug. The rest are a cached page, a card that expired on the hosting account, an email that landed in spam because nobody ever set up SPF, or "where do I click to add a product".
Things I have already tried. A long handover document: nobody reads it. A walkthrough on the final call: nobody remembers it two weeks later. A follow-up email with links: opened, not read.
I am not looking for "communicate better". I am looking for the specific artefact or process change that moved your call volume, ideally with what it did and did not fix.
@p99_hana · 2h ago
Instrument it so you find out first.
An uptime check on the main pages and error alerting on the backend costs very little and changes the entire dynamic of the call. "I saw it go down eleven minutes ago and it is already back" and "you are telling me it has been down all day" are two different relationships with the same client.
It does not reduce call volume much on its own. It changes what those calls cost you in trust, which is arguably the more expensive currency.
Reply
Report