Spaces

Reply speed scorecard for subscriber, author and user messages

This scorecard asks eight yes or no questions about how your publishing business answers messages today, from missed copies to bug reports. It shows where replies are slow and what to fix first.

Runs in your browser. Nothing you enter is sent anywhere or saved.

Before you start

Most publishers think they answer quickly until they look. A subscriber writes on Saturday about a missed paper and hears back on Tuesday. An author waits two weeks for a one-line reply. A software user posts a bug on Friday and gets an answer the next Thursday. Each delay feels small to you and large to them.

Answer each question honestly with yes or no, based on what happens on a normal week, not your best one. Count your yes answers at the end. The result tells you where you stand and what to improve first. There is no pass or fail, only a starting point.

Do you reply to a subscriber about a missed copy on the same day?
Do you reply to every author or contributor message within three working days?
Do you have a written answer for the five most common reader questions?
Do you know who answers messages at weekends and during holidays?
Do you ask software users for their version and error text in your first reply?
Do you tell people when a person will reply if you cannot answer at once?
Do you check once a week for messages that nobody answered?
Do you pass rights, corrections and legal matters to a named person the same day?

Answer all 8 to see your result. 0 so far.

Why speed matters in publishing

Publishing messages are often tied to a date. A missed copy is only fixable if the circulation team hears early. A deadline question is only useful before the deadline. A release-day bug matters most on release day. When a reply arrives late, the answer may be right and still useless, because the moment has passed.

Speed is not only about how fast you type. It is about knowing who owns each kind of message, having the answers written down and knowing when you are unavailable. Most slow replies come from unclear ownership, not from lazy people.

  • Name one owner for each audience.
  • Write the five common answers down.
  • Say honestly when you will be back.
  • Read the unanswered list every week.

FAQ

What is a good reply time for a publisher?

There is no single number. Aim for same day on delivery and software faults, and a few working days for editorial matters. What matters most is telling people what to expect.

Does a fast reply need to be a full answer?

No. A quick message that says you have it, and when a person will follow up, is much better than a long delay followed by a perfect answer. Speed and care work together.

How can an agent help with reply speed?

It can answer routine questions straight away, collect details for harder ones and tell people what happens next. A person then picks up only the cases that need judgement.

More free tools for publishers and software publishers

Read the guide: Answer reader, author and customer messages in publishing.