---
title: "Which business processes to automate first | attendo"
description: "How to choose which processes to automate first: volume, clear rules and the cost of a mistake, with examples by department and where AI helps or does not."
url: "https://attendo.me/en/blog/which-processes-to-automate-first"
lang: "en"
---

# Which processes to automate first, and which to leave alone

Automating the wrong process costs you twice: the time to build it and the time to undo it. Three simple questions separate what is worth automating now from what is better left alone.

- By the attendo team
- Published September 28, 2026
- 4 min read

**In this article**

1. Three questions for every process
2. A simple matrix to decide
3. Examples by department
4. Where AI belongs, and where it does not
5. How to start without breaking anything
6. Three common mistakes

## Three questions for every process

Before you draw any workflow, ask each candidate process three questions:

1. **How often does it happen?** A process that runs four times a year does not deserve a workflow. One that runs forty times a week almost certainly does.
2. **Can you write the rules down?** If you can write on one page what happens in each case, you can automate it. If the answer is “it depends” and nobody knows on what, not yet.
3. **What does a mistake cost?** A ticket routed to the wrong person gets forwarded. A payment approved by mistake, or an email with another customer’s data, cannot be undone.

To start, look for high volume, clear rules and cheap mistakes. Leave for later anything that rarely happens, depends on someone’s judgment and is expensive when it fails.

## A simple matrix to decide

| Type of process | If a mistake is cheap | If a mistake is expensive |
| --- | --- | --- |
| **High volume and clear rules** | Automate it now | Automate it, with a human approval at the sensitive step |
| **Low volume or fuzzy rules** | A template or a checklist is enough | Do not automate it: write the procedure first |

Score each candidate from 1 to 3 on the three questions and rank them. You do not need more precision: the conversation with the people doing the work today matters more than the number.

## Examples by department

| Area | Good first candidate | Better to wait |
| --- | --- | --- |
| Purchasing | Purchase requests with approval based on the amount | Choosing a new supplier |
| HR | Onboarding a new hire, with tasks for IT, admin and their manager | Evaluating the probation period |
| Customer service | Sorting and assigning what comes in, and confirming receipt | Answering a sensitive complaint |
| Quality | Opening a nonconformance with its checklist and owner | Deciding the root cause |
| Finance admin | Approving expenses with their receipts | An out-of-policy expense that needs judgment |
| Maintenance | Creating the work order when a reading goes out of range | Deciding whether to repair or replace a piece of equipment |

The pattern repeats: you automate the movement, meaning who gets what, when and with which data. Judgment stays with people.

## Where AI belongs, and where it does not

AI fits steps where someone has to read free text and mistakes can be corrected. It does not fit where a written rule does the same job, or where a mistake is expensive.

| Yes | No |
| --- | --- |
| Sorting an incoming email: order, complaint or question. If it gets it wrong, someone reclassifies it. | Approving an expense or a payment. A rule based on the amount is cheaper, more predictable and easier to audit. |
| Summarizing a long thread or transcribing a voice note before the next step. | Choosing the path of a process with formal requirements, such as closing a nonconformance. |
| Detecting the tone of a message to prioritize it. | Writing to a customer without review on a sensitive topic. |

A simple test: if the rule fits on one line (“if the amount is over $3,000, the director approves”), you do not need AI. Save it for what does not fit on one line. There is more in [what works and what fails with AI in customer service](https://attendo.me/en/blog/ai-in-customer-service-what-works).

## How to start without breaking anything

1. Pick a single process from the “automate it now” box.
2. Map it with the people who do it today, not with the people who manage it. Steps will show up that were never in any procedure.
3. For two weeks, measure how long it takes and how often it gets stuck.
4. Build it, test it with real cases and turn it on for one team.
5. After a month, review the run history: where it stalls and which exceptions show up.

Exceptions are the valuable part. If many runs end with someone fixing things by hand, the rules were not as clear as they looked.

Calculator

Run the numbers with your own data

Return

### [attendo ROI](https://attendo.me/en/calculators/roi)

The hours and money your team gets back when it stops hunting for data, retyping service reports and chasing approvals.

## Three common mistakes

- **Automating a broken process.** If nobody knows today who approves, the workflow will just make the mess faster.
- **Starting with the most complex one “because it hurts the most.”** It takes the longest to build and is the most likely to fail.
- **Leaving no trail.** An automated process without a history is a black box: when it fails, nobody will know why.

A simple process that runs on its own every day teaches you more than a big project stuck halfway. Start there, and let the exceptions tell you which one comes next.

Last updated: September 28, 2026

## How attendo handles it

With attendo Flows, a flow starts with an email, a form, a webhook or a status change, and acts without code. Business Process Flow (BPF) sets the stages and what is missing to move forward. AI only comes in at the step where you put it. Every run records which path it took, and the validator will not let you turn on an incomplete flow.

- [attendo Flows](https://attendo.me/en/flows)
- [attendo Flows, Business Process Flow (BPF) and AI-Flows](https://attendo.me/en/modules/flows)
- [Automation](https://attendo.me/en/automation)

## More on processes and compliance

### Approvals without email: an approval process that does not stall

Approving by email works until someone asks who approved what, and when. Then the search through other people’s inboxes begins. A well-built approval process answers that question in seconds.

4 min read

Choosing and rolling out software

### How to go from three systems to one without stopping operations

The idea is appealing and the fear is reasonable: replacing the systems your company runs on sounds like weeks of chaos. It can be done without anyone noticing, but not all at once.

4 min read

Support and customer service

### AI in customer service: what works and what doesn’t

We keep hearing that AI will transform customer service. Some things it has already changed, and others still do not work well. It is worth telling them apart before you spend money.

4 min read

[All blog articles](https://attendo.me/en/blog)

## Shall we look at it with your operation?

Tell us how you work today and we will show you attendo with your own data. If it is not a fit, we will say so.

- With your operation, not a generic demo
- A real person from our team replies
- No cold calls afterwards

Would you rather talk first?

- Phone [+34 910 053 530](tel:+34910053530)
- Email [sales@attendo.me](mailto:sales@attendo.me)
- Monday to Thursday 9:30 AM to 6:30 PM and Friday 9:30 AM to 2:30 PM (Spain time)