Ask
38
@soloseat_sana ·

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.

10 answers Share
Report

Answering anonymously — a moderator will review it first.

  • @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.

    18
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report
  • @rough_draft_rob · 6h ago · 3 replies

    A five-minute screen recording, sent as a link, beats any document I have ever written.

    Clients will watch a video. They will not read a PDF. After I started sending one, the questions that survived were overwhelmingly actual bugs rather than "where do I click", which is the split you are describing.

    Two details that matter. Record it in their own data, not a demo account, so they recognise the screens. And keep it under six minutes — the moment it becomes a training course, it goes in the same drawer as the document.

    24
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report
    • @quiet_promotion · 11h ago

      Pair it rather than replacing. Video for "how do I do the thing", one page for credentials, renewal dates and who to call in what order.

      Video is useless at 2am. Nobody scrubs through a recording looking for the hosting login while panicking. The one-pager in their inbox is what gets found under stress, and the video is what stops the calm-daytime questions.

      11
      Share
      Reply

      Answering anonymously — a moderator will review it first.

      Report
    • @rough_draft_rob · yesterday

      Agreed. One thing I would add: chapter the video. A forty-second answer buried at minute four might as well not exist, and most recorders will let you drop chapter markers in for free.

      6
      Share
      Reply

      Answering anonymously — a moderator will review it first.

      Report
  • @till_and_tally · 16h ago · 2 replies

    Look at your one-in-six number again. Most of the other five are billing and ownership, not code, and that is fixable with an afternoon of admin.

    One page listing every account in the stack — registrar, DNS, hosting, email, payment processor, any paid plugin or API — and for each one: who owns it, which card it bills to, when it renews, and what breaks if it lapses.

    Then the part people skip: during the handover call, while you are both on the line, put the renewal dates into THEIR calendar. Not yours, not a shared document. Their calendar, with a reminder two weeks ahead. An expired card is a Tuesday-afternoon problem if it is on a calendar and a 2am emergency if it is not.

    21
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report
    • @soloseat_sana · 2h ago

      The expired card one has bitten me twice and both times I ate the emergency hours because it felt petty to invoice for someone else's payment method. Putting the dates in their calendar during the call is such an obvious fix that I am mildly annoyed.

      7
      Share
      Reply

      Answering anonymously — a moderator will review it first.

      Report
  • @harlan_voss · 5h ago

    Half of this is a contract problem wearing a documentation hat.

    Define the support window, the response times, and what counts as an emergency, in writing, at signature. Not after launch, when you are negotiating from a position of guilt and they have already formed the habit of ringing you.

    The reason 2am calls happen is that 2am calls are free. Documentation reduces how often somebody needs you. Only the agreement changes when they feel entitled to reach you.

    13
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report
  • @idempotent_ian · 2h ago

    Give them one URL that answers "is it me or is it them".

    A good chunk of the 2am calls are the client's own broadband, their own laptop, or a captive portal in a hotel. A trivially simple status page — even one static page hosted somewhere entirely separate from the app — lets them check before they dial. Put the URL on the one-pager and say it out loud on the handover call: "before you ring me, load this."

    It filters a surprising number of incidents that were never incidents.

    15
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report
  • @csv_apologist · 2h ago · 2 replies

    Put everything in a shared workspace — wiki pages, credentials, runbooks. That is what those tools are for, and then it is all in one searchable place.

    4
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report
    • @harlan_voss · 2h ago

      Clients do not log into a second tool for you. Ever. They log in once during the handover call, agree that it is very nice, and never return.

      Anything you need read has to arrive where they already live: an email with a PDF attached, or something printed that ends up in a drawer near the desk. The wiki is for you and for whoever maintains the thing after you. Building it is fine. Relying on the client to open it is how you end up back on this thread in a year.

      16
      Share
      Reply

      Answering anonymously — a moderator will review it first.

      Report