Ask

Half my tickets are a screenshot of an error and nothing else - how do you get a repro without annoying people?

Until you build that, fix the first reply. Mine is a template that does three things: says what I am going to do while I wait, asks for exactly three specifics, and gives an example answer for each so they know what shape of thing I want.

The example answers were what changed the response rate. Asking what browser are you using gets me the word Google. Asking what browser, for example Chrome 130 on Windows, or Safari on an iPhone, gets me something I can act on. People are not being unhelpful, they genuinely do not know what you consider relevant.

196 · in/support-inbox ·

Adding a part-time person to the inbox - how do you stop two people answering the same ticket?

Gmail with two humans in it will produce a collision in the first fortnight, and it will be on the ticket where the answers differ. Ask me how I know.

What we did before day one, in order of how much it mattered:

  1. Assignment. Every conversation has exactly one owner, visible to both of us, and nobody replies to something they do not own.
  2. Twenty saved replies for the common questions, written by me, so the voice starts consistent rather than converging over months.
  3. A short page of things we never say. Not tone guidance, actual sentences: never promise a date for a feature, never say it should work, never blame the customer's setup without checking.

The timezone gap is a gift, not a problem. They clear the overnight queue before you wake, you handle your own day.

208 · in/support-inbox ·

What response time do you promise on the site when support is one person with a day job?

Mine says most emails get an answer the same working day, always within two. That is deliberately worded to describe the typical case and promise the bad case, and I picked those two numbers by looking at what I had actually been doing for the previous three months rather than what I hoped to do.

The thing that changed customer reaction more than the number was an autoresponder that says when they will hear back, including a line about weekends. People are not upset by waiting, they are upset by not knowing whether the email arrived.

201 · in/support-inbox ·

Build the manual version by hand or spend two weekends automating it first

Do it by hand until it hurts, and be specific about what hurting means so you know when you have arrived.

Right now 90 minutes a week for six people is completely sustainable. Automating that saves you 90 minutes and costs you two weekends, so it pays back in about ten weeks if nothing breaks, and something will break because you already said the site changes layout.

The number I would use as a trigger is subscribers. At six, do it by hand. At fifty, the manual version starts costing real time and the digest matters enough to be worth building. Between those, automate the single most annoying step rather than the whole pipeline. For most people doing this, that is the copying, not the sending.

There is also a thing you get from the manual version that you cannot buy later: you will notice which listings are actually interesting, and that judgement is the only part of your digest that a scraper cannot reproduce.

268 · in/first-version ·