Spaces

Message workload planner for computer and device makers

This calculator works out how many hours a week a computer or peripheral maker spends answering customer messages, from the number of chats, the minutes each takes and the days worked. It is made for owners and support leads.

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

Before you start

Hardware support looks small until you count it. Thirty chats a day about drivers, orders and returns, at six minutes each, is three hours a day. Add launch weeks and the number climbs. Many makers are surprised how much of a technician's week goes to answering the same questions.

Enter how many messages you get on a typical day, how long each takes from first reading to last reply, and how many days a week you answer. Use real numbers from last week if you can. The result shows hours a week, a month and in working days.

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

Under your figures

Hours a week spent answering18
Hours a month (4.3 weeks)77
Working days a month (8-hour days)9.7

An estimate built from your own figures, so check it against a real week of chats before you rely on it.

Reading your result

If the answer is under five hours a week, messages are a light part of the job. Between ten and twenty hours means a technician is spending a day or two a week on chat. Beyond that, the work is probably competing with repairs, testing and product work.

Remember that interruptions cost more than minutes. A message about a driver in the middle of a firmware test breaks concentration. The true cost is usually higher than the arithmetic.

Where the minutes go

In hardware support, time is lost in a few places.

  • Asking for the model, system and serial number over several messages.
  • Looking up the right driver or manual.
  • Explaining the same return steps again and again.
  • Writing a hand-over note after the chat is half done.

FAQ

What should I count as a conversation?

One customer and one issue, from the first message to the last reply. A chat that runs over two days still counts as one, but add the total minutes spent.

Does this include launch weeks?

Use a typical week for the main figure. Then run it again with launch-week numbers to see the peak. The gap between the two shows how much extra help you need.

How accurate is it?

It is only as accurate as your inputs. Count real chats for a week, time a few of them and use those figures for a result that matches your reality.

More free tools for computer and peripheral makers

Read the guide: Answer support and order messages for computer and peripheral makers.