How to Calculate the Real Cost of Manual Email Support for Your Team

Ask a support manager what the team's inbox costs and you will usually get a shrug, or the monthly salary of the people who work in it. Neither is a real answer. Email support has no invoice of its own. Its cost is spread across hours, interruptions and corrections, and so it stays invisible until someone sits down and works it out.
This article gives you a simple, honest way to do exactly that. It walks through the cost drivers of manual email handling, shows a formula you can fill in with your own numbers, explains how to measure the inputs without fooling yourself, and then looks at what changes when classification and first drafts are automated. It contains no promised savings and no customer figures, because the only numbers that matter for your decision are your own.
Why the cost stays hidden
Most teams know how many emails arrive. Far fewer know how long each one takes. The reasons are understandable:
- The work is fragmented. A reply is rarely one uninterrupted task. It is reading, looking something up in another system, writing, checking and sending, often interrupted by the next message.
- The time is shared. When five people each spend an hour a day in the inbox, nobody sees a full-time job, but it is one.
- The costs sit in different budgets. Staff time is in the payroll, rework appears as delays elsewhere, and customer frustration appears nowhere at all.
Because of this, email support tends to be underestimated. Making the cost visible is the first step towards deciding, calmly, what is worth improving.
The cost drivers
Four drivers explain most of what manual email support costs.
1. Volume
How many emails does your team handle in a typical month? Count the emails that require a reply, not every notification and not newsletters. If volume varies a lot, take an average over several months. If you use a helpdesk or shared mailbox, a simple export usually provides this number.
2. Time per email
This is the driver that is most often guessed and most often wrong. Time per email is the whole handling time, not only the typing:
- Reading and understanding the request.
- Finding the right information, for example in a customer record, an order system or an earlier thread.
- Writing the reply, including checking tone and facts.
- Sending, filing and any follow-up action.
- The cost of switching between tasks, which is real even if it is hard to measure.
Simple emails may take two minutes and complicated ones twenty. What you need is a realistic average, ideally split by type.
3. The hourly cost of staff
Use the full cost of an hour of work, not the hourly wage. The full cost includes the employer's contributions, paid leave and sick days, equipment and workspace, and the share of management and training that the role requires. Your finance department can usually give you a loaded hourly rate. If you do not have one, a careful estimate is better than the gross wage.
4. Errors, rework and follow-ups
Not every email is answered correctly the first time. Some replies miss a detail and trigger a second message from the customer. Some are sent to the wrong colleague, and some need a correction. Each of these costs another round of reading, writing and sending. A realistic estimate includes the share of emails that need a second round and the time that round takes.
Beyond these four, there are costs that are real but harder to put a number on, such as slow replies that lead to additional "any news?" emails, or customers who go elsewhere. It is better to name these than to pretend they are zero, but keep them out of the formula so that the number you calculate stays defensible.
A simple formula
Here is the calculation in plain language.
Monthly handling cost = emails per month × average minutes per email ÷ 60 × loaded hourly cost
Monthly rework cost = emails per month × share that needs a second round × minutes per second round ÷ 60 × loaded hourly cost
Total = handling cost + rework cost
To see how it works, take an illustrative example. The figures are invented to show the arithmetic and are not benchmarks:
- 1,200 emails per month
- 6 minutes on average per email
- A loaded hourly cost of 38 EUR
- 10 percent of emails need a second round of 5 minutes
Handling: 1,200 × 6 ÷ 60 = 120 hours, and 120 × 38 EUR = 4,560 EUR per month. Rework: 1,200 × 0.10 = 120 emails, 120 × 5 ÷ 60 = 10 hours, and 10 × 38 EUR = 380 EUR per month. Total: 4,940 EUR per month in this example.
Replace each input with your own, and you have a first estimate. The result is not a precise figure, but a reasoned one that you can discuss and refine.
How to measure the inputs honestly
The quality of the result depends on the quality of the inputs. A few practical habits help.
- Sample instead of guessing. For one or two weeks, ask the team to note how long a sample of emails takes, split by type. A simple tally is enough.
- Split by type. An order status question and a complaint do not take the same time. Averages by type are more useful than one global average.
- Use real volume. Pull the numbers from your mailbox or helpdesk rather than relying on memory.
- Ask the people who do the work. They know which emails need a lookup in three systems and which can be answered from memory.
- Be conservative. If you are unsure between two values, take the lower one. A cautious estimate that still looks significant is more convincing than an optimistic one.
The ROI calculator on this site follows the same logic and lets you try different values. Its defaults are assumptions that are stated on the page, so adjust them to your situation instead of taking them as given.
Pitfalls that distort the picture
- Counting the wrong hours. Include the time spent on email by people whose job is not officially support, such as account managers or administrators.
- Using the gross wage. This understates the real cost of an hour.
- Ignoring peaks. If one week is twice as busy as another, the team either works overtime or replies slowly. Both have a cost.
- Double counting. Do not add the same hour once as handling time and again as rework.
- Mixing in the benefit before you have the cost. First establish what the current process costs. Only then ask what could change.
What changes with automation
Once you know the cost, the next question is which parts of it could shrink. Looking at the drivers helps.
Volume stays the same. Customers will keep writing, and you would not want to discourage them. Time per email and rework are the drivers that automation can influence.
- Classification. Sorting incoming mail by topic and priority is work that happens before a reply is even started. When an assistant categorises emails, the right mail reaches the right person without someone first reading everything.
- First drafts. For recurring questions, an assistant can prepare a reply in the language of the customer, based on the way your team has answered similar emails before. The colleague reviews and sends instead of writing from scratch.
- Lookups. Where a connection to your own systems has been configured, the assistant can retrieve the facts needed for a reply, so nobody has to open three different tools. Whether this is possible depends on your systems and is scoped individually.
- Consistent replies. Standard answers prepared from your own material can reduce the follow-up questions caused by incomplete replies.
This does not mean that the work disappears. People still review, decide and handle everything that needs judgement. InboxFirma is built so that sensitive mail goes to a person, and so that you decide per type of email whether a reply may be sent automatically, needs approval or always goes to a colleague. What changes is where the team's time is spent: less on sorting, searching and typing routine answers, more on the conversations that need a human.
It would be easy to attach a percentage to this, and many articles do. We do not, because the effect depends entirely on your mix of emails, your systems and the rules you choose. The honest approach is to calculate your current cost, estimate how many of your email types are routine, and then discuss a realistic scenario for those types only.
See the mechanics for yourself
Numbers on a page are one thing, and seeing the process is another. Our live AI email demo lets you choose a business category, paste the text of a sample email and watch what happens: the email is classified, relevant information is looked up in a simulated company system, a reply is drafted and a routing decision is shown. The data in the demo is fictional and the text you paste is not stored, so it is a safe way to get a feeling for how the steps fit together.
When you look at the result, think about your own inbox. Which of your emails resemble the examples? How many minutes would the review of such a draft take compared to writing it yourself? That small thought experiment often tells you more than a spreadsheet.
Turning the number into a decision
With a monthly cost in hand, you can ask better questions:
- Which email types make up most of the time? Often a handful of recurring types account for a large share of the work.
- Which of them are routine? Status questions, document confirmations, appointment requests and standard information requests are typical candidates.
- What would have to be true to automate them safely? Clear rules, access to the right data, and an approval phase at the start.
- What is the effort to set this up, and what does it cost? Compare the one-off and monthly cost of a custom setup with your own number, and be sceptical of anyone who promises results without knowing your emails.
A calculation like this does not have to be perfect. It only has to be good enough to show whether the topic deserves attention. For many teams it turns out that the inbox is one of the largest hidden costs in their daily work, and also one of the more tractable ones.
A short checklist
- Count the emails that need a reply per month.
- Measure the average handling time by type, over one or two weeks.
- Use the loaded hourly cost, not the wage.
- Estimate the share of emails that need a second round, and its duration.
- Apply the formula and keep the result as a range, not a single number.
- Identify the routine types and discuss them first.
Done thoughtfully, this exercise takes an afternoon. If you would like to go through it with your own figures, you can talk to us about what a custom setup could look like for your email volume.


