When is it cheaper to automate a customer query than to handle it manually?

Why work with us:

– We improve your accessibility
– We enhance your customer experience
– We increase your efficiency

Want to know how we’ve been using AI to enhance the customer experience for years?

“With Pegamento, we found not just a supplier, but a true partner in change. Thanks to their expertise and our joint DevOps approach, we have made great strides in a short time. The technology supports our people so they can focus on where they make a difference: personal contact with entrepreneurs.”

Automating a customer query is cheaper than manual handling as soon as the fixed costs of the automation solution are lower than the cumulative personnel costs for the same contacts over time. For most service organizations, that break-even point lies with recurring, highly predictable queries with a sufficiently high volume. The sections below explain the calculation logic step by step, so you can make an informed assessment for your own situation.

What costs are associated with manual customer query handling?

The real costs of a manually handled customer contact consist of more than just an employee’s salary. On average, they include direct wage costs including employer contributions, overhead such as housing and tooling, training time, quality control, and the costs of errors or repeat contacts. Those who only look at the hourly rate significantly underestimate the real price per contact.

Suppose an employee handles a simple status information request in four minutes. At a fully loaded hourly rate of roughly fifty euros, that amounts to over three euros per contact. But there is more: the time the employee needs to look up information in multiple systems, the chance of errors leading to a follow-up contact, and the coordination costs if the query is forwarded to another department. In practice, the real costs of a manually handled customer contact for many service organizations are significantly higher than the direct wage costs suggest.

Hidden cost items that organizations often overlook:

  • Repeat contact because the first answer was incomplete or incorrect
  • Waiting time costs for customers leading to extra contact attempts
  • Administrative after-call work
  • Absenteeism and turnover due to repetitive work
  • Scaling costs during peak loads, such as the use of temporary staff

What are the real costs of an automated customer query?

The costs of an automated customer contact consist of two components: the one-time or periodic fixed costs of the solution and the variable costs per handled contact. Those variable costs per contact decrease as the volume increases, which makes automation increasingly attractive at scale.

The fixed cost component includes license or platform costs, implementation and integration with existing systems, maintenance, and ongoing optimization. The variable component per contact is usually low: computing power, API calls, and any transaction costs. Depending on the chosen technology and the volume, the variable costs per automatically handled contact can amount to a fraction of the manual costs.

Important to include in the calculation:

  • Not every automated contact is handled entirely without human intervention. A portion escalates to an employee. Include those costs as well.
  • Integration with existing systems costs time and money. The more legacy systems in the field, the higher the initial investment.
  • A well-set-up solution requires periodic maintenance, especially if processes or products change.

How many contacts are needed to make automation profitable?

The break-even point for automating a customer query is reached when the cumulative savings on manual handling equal the total investment in the automation solution. That point depends on the cost price per manual contact, the fixed costs of the solution, and the monthly contact volume for that specific query type.

A simple calculation example: suppose the implementation costs for automated handling of one query type amount to fifteen thousand euros, including integration and setup. The manual cost price per contact is three euros. In that case, the solution must handle five thousand contacts before the investment is recouped. With a thousand contacts per month, that break-even point is reached after five months. With a hundred contacts per month, it takes over four years, which makes the business case a lot less strong.

Factors influencing the break-even point:

  • The degree of reuse: can the same technology handle multiple query types?
  • The complexity of the integration with existing systems
  • The percentage of contacts successfully handled automatically without escalation
  • The expected growth of contact volume in the coming years

Which types of customer queries are best suited for automation?

Customer queries best suited for automation are those with high frequency, a predictable answer, and a limited need for empathy or complex assessment. Think of status information, frequently asked questions, appointment management, simple changes, and standard payment queries.

The rule of thumb is simple: the more a query resembles another query and the more the answer can be given based on available data without human judgment, the more suitable that query is for automation. Queries where a customer is emotionally involved, where exceptional situations are the norm, or where an error has major consequences, often require human contact.

Query types with strong automation potential:

  • Status information about orders, requests, or repairs
  • Opening hours, locations, and general product information
  • Password recovery and account management
  • Making, changing, or canceling appointments
  • Simple invoice and payment queries
  • Filling out forms or providing documents

When is automation cheaper despite a low contact volume?

Automation can also be more cost-effective than manual handling at a relatively low contact volume when manual handling is disproportionately expensive, when the query arrives outside office hours, or when errors in handling cause high follow-up costs.

A good example is nighttime malfunction reports at a utility company. The volume may be limited, but an employee who must be available in the middle of the night is significantly more expensive than an automated first response that registers, confirms, and forwards the report. The same applies to query types where a manual error leads to a legal or financial consequence.

Other situations where automation pays off even at low volume:

  • The query requires access to multiple systems simultaneously, which takes a lot of time manually
  • The query has a strong seasonal character with extreme peaks
  • The organization has insufficient staff available for the task in question
  • The same technology can be used more broadly for multiple processes

In those cases, the business case shifts: it is not the volume that is decisive, but the cost price per manual contact in relation to the fixed costs of the solution.

How do you calculate the business case for automating a specific process?

You build a solid business case for automation by comparing four figures: the current costs per manual contact, the annual contact volume for that query type, the total investment in the solution, and the expected automation percentage. With these, you calculate the payback period and the return over a period of three to five years.

Step by step, the calculation looks like this:

  1. Determine the real cost price per manual contact for the specific query type, including overhead and after-call work.
  2. Total the annual volume of that query type based on historical data.
  3. Estimate the automation percentage realistically. Not every contact is handled fully automatically.
  4. Calculate the annual savings: volume x automation percentage x cost price per contact.
  5. Offset the total investment against the annual savings to determine the payback period.
  6. Add qualitative benefits: higher availability, fewer errors, better customer satisfaction, and lower workload for employees.

An honest business case also takes risks into account: what if the automation percentage turns out lower than expected? What are the costs of a phased rollout? And what are the costs of doing nothing if the contact volume grows in the coming years?

How we help with automating customer queries

We help organizations make an informed choice about which customer queries are suitable for automation and which approach yields the most return. No costly custom work, but a smart combination of proven modules that connect to your processes and systems.

What we offer:

  • Business analysis and process diagnosis: we map out the real contact volume, the cost price per query type, and the automation potential.
  • Concrete business case: including payback period, risks, and a phased approach that fits your organization.
  • Implementation and integration: from conversational AI and self-service to process automation via Agentic AI, the evolution from executing bots to self-thinking assistants that don’t just follow instructions but take independent initiative and act.
  • One point of contact: from analysis to management and ongoing optimization, everything under one roof without complex supplier structures.

Want to know the break-even point for a specific query type in your organization? Contact us and we will be happy to think along with you.

Frequently Asked Questions

How accurate must my contact volume estimate be to create a reliable business case?

An exact count is ideal, but a reliable estimate based on historical data from your CRM, telephone exchange, or ticketing system is sufficient for an initial calculation. Preferably work with a range: calculate the business case for both a conservative and an optimistic scenario. This gives you insight into the margin within which the investment is profitable, without being dependent on a single figure.

What is a realistic automation percentage to use in calculations?

For well-defined, repetitive query types such as status information or appointment management, a realistic automation percentage lies between 70% and 90%. For more complex or varied query types, 50% to 70% is a safer starting point. Always use the conservative figure in your business case and consider everything above that as upside, so you don’t create expectations that the solution cannot meet.

What are the most common mistakes when setting up a customer query automation project?

The most common mistake is underestimating the integration complexity with existing systems, causing the initial investment to be higher than budgeted. A second common mistake is automating a query type that has too many exceptions, keeping the escalation rate high and the savings disappointing. Finally, organizations often forget to appoint an owner for ongoing maintenance, while the quality of the solution declines as soon as products or processes change without the automation being updated.

How do I handle customer queries that can be partially automated but sometimes still require human intervention?

Design the solution from the start as a hybrid model: the automation handles the standard part and seamlessly transfers the conversation to an employee as soon as an exception is recognized. Ensure that the employee has immediate access to the context already collected upon escalation, so the customer doesn’t have to repeat their story. This hybrid model usually already yields significant cost savings, even if the automation percentage is lower than hoped.

Should I start with the query type with the highest volume, or are there better criteria to start with?

Volume is an important criterion, but not the only one. A good starting candidate combines high volume with high predictability of the answer and relatively simple integration with existing systems. Preferably start with a query type that yields quickly demonstrable results, so you build internal support for further automation. A quick first win is strategically more valuable than an ambitious first project that takes a long time and involves many uncertainties.

How do I measure whether the automation solution actually delivers the expected savings after going live?

Establish a baseline measurement beforehand: the actual number of manual contacts for that query type and the average handling time per contact. After going live, monitor the automation percentage, the escalation rate, and the customer satisfaction score for automated contacts. Compare these figures monthly with the baseline and adjust where necessary, for example by training the solution on common exceptions that currently still escalate.

Is it wise to automate multiple query types at once, or is a phased approach better?

A phased approach is almost always preferable, especially for a first automation project. Start with one well-chosen query type, learn from the implementation, and optimize the solution before expanding. The technology and platform you set up for the first query type can then be expanded to other query types with significantly lower incremental costs, further strengthening the business case for later phases.

More blogs

Do you have a question?

We’d be happy to help.
Schedule a 15-minute introductory meeting at
or call +31 (0)88 00 67 180

Download the white paper here

Deepen your knowledge with Pegamento’s white papers.