Spaces

How many hours a week do customer messages take your machine company?

This planner estimates the hours a week your machinery company spends answering plant messages. Enter how many arrive a day, how long each takes and how many days you answer.

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

Before you start

Machinery messages are rarely quick. A single parts request may mean finding a serial number, checking a build record, searching an exploded diagram and replying with a part number and a lead time. A fault message may mean reading a manual and asking three follow-up questions. Those minutes add up across a week without anyone noticing.

Enter your own figures, or begin with the examples. Think of a normal week, not the quietest one. The result shows your hours a week, hours a month and working days a month, so you can see how much of your team's time goes into replies before any engineering or parts work begins.

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

Under your figures

Hours a week spent answering25
Hours a month (4.3 weeks)108
Working days a month (8-hour days)13

This is an estimate based on the figures you enter, so use your real numbers for the best picture.

Reading your result

If the number surprises you, that is common. Time spent on messages is spread across service engineers, parts staff and sales engineers, each giving twenty minutes here and there. Nobody records it, so it never appears on a plan or a budget.

Once you have the figure, look at where it comes from. Which questions take the longest? Which could be answered from a document you already own? Which should always go to a person, like safety and price?

  • Count one full week to get a more reliable average.
  • Include evening and weekend messages from other time zones.
  • Note how many questions are repeated.

What to do with the number

A high figure is a reason to tidy your documents and decide who answers what. An AI agent can take routine requests such as manuals and part lookups, while engineers keep faults, safety and quotes.

FAQ

What counts as one message?

Count each new conversation or request, not every line in a chat. A single fault case with ten replies is one message, though it may take a long time, so use a realistic average for minutes.

Why are my minutes per message so high?

Machine messages often need a serial number lookup, a manual search and a check of the build. That makes twelve minutes or more normal. Faster tools and better documents are the usual way to bring it down.

Should I include time on follow-up calls?

You can, if a message leads to a call about the same case. The point is to see the real time cost of answering customers, so include whatever your team honestly spends.

More free tools for industrial machinery makers

Read the guide: Answer commissioning and spare parts messages for machinery makers.