Spaces

How many hours a week do technician messages take your team?

This planner estimates the hours a week your instrument or controls business spends answering customer messages. Enter how many arrive a day, how long each takes and how many days you take them.

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

Before you start

Messages to an instrument maker rarely look like a big job, because each one is a small pause in the day. Yet a question about a range may need a look through a data sheet, and a calibration request may need a check of the service calendar. Those pauses add up to a surprising share of an engineer's week.

Enter your own figures, or start with the examples. Count a typical day, not your quietest one. You will see hours a week, hours a month and working days a month, which helps you decide who should take messages and when.

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

Under your figures

Hours a week spent answering15
Hours a month (4.3 weeks)63
Working days a month (8-hour days)7.8

This is an estimate from your own figures, so the more exactly you count, the closer it will be.

Reading your result

Many makers find the number higher than expected, mainly because the time falls on skilled people. An application engineer who answers fifteen routine questions a day is not designing, testing or solving the hard cases. The cost is in what that person is not doing.

Once you have the figure, look at where it comes from. Which questions take longest? Which could be answered from a written note? Which must always go to an expert, such as clinical and safety chats?

  • Track messages for one full week for a better average.
  • Note which questions repeat most often.
  • Separate quick lookups from questions needing real thought.
  • Count time spent searching for manuals and records.

FAQ

How do I count minutes per message fairly?

Time a handful of real replies from first reading to sending, including looking things up. Use the average rather than your fastest. Include the time spent switching back to what you were doing.

Should I include handed-over conversations?

Include the time your staff spends on the first reply, and leave out long technical problem-solving that would always need an expert. This keeps the number focused on routine messages.

What do I do with the result?

Use it to decide how much routine work an agent could take on, and to explain the issue to your team. It is a starting figure for a plan, not a target or a promise.

More free tools for instrument and controls makers

Read the guide: Answer technician and lab messages for instrument and controls makers.