Spaces

How many hours a week do software customer messages take?

This planner turns the number of customer messages you receive, and the minutes each takes, into hours a week and working days a month. It is made for software publishers and app makers.

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

Before you start

Support rarely feels like a job of its own in a software company. It leaks into the hours of developers, founders and account managers, a few minutes at a time. Added up, those minutes can quietly take a full day or more every week.

Enter your typical figures. Count every message that needs a reply: install trouble, licence questions, how-to requests and pre-sales chats. Use an honest average for the minutes, including the time to look up an account or check the docs.

Every starting figure is an example. Change each one to your own.

Under your figures

Hours a week spent answering24
Hours a month (4.3 weeks)103
Working days a month (8-hour days)13

This is an estimate based on your own figures, so use a typical week and adjust if release weeks run much busier.

Reading your result

The number of hours a week shows what support really costs you in time. If it comes to more than a working day, you are probably paying an engineer or founder to do work that does not need their skills.

Look at the working days a month as well. Half a working day a week is two or three days a month, which could have gone into a feature or a fix customers are asking for.

Where the minutes hide

Most time goes on a small set of repeat questions.

  • Resending download links and licence emails.
  • Explaining system requirements to the same type of buyer.
  • Asking for version and error details in the first reply.
  • Looking up an account to confirm an edition or seat count.

FAQ

Should I count release weeks in the average?

Use a normal week for the main figure, then run it again with your busiest release week. The second number shows how much extra support a launch really creates.

What if different messages take very different time?

Use a weighted average. Many short link requests and a few long bug threads might average out to five or six minutes, which is a fair figure to enter.

Does this include sales chats?

It can. If pre-sales questions come in through the same chat, count them too, since they take time and often decide whether a purchase happens.

More free tools for software publishers and app makers

Read the guide: Answer software customer messages before they become tickets.