Most teams that try AI in customer contact start with the wrong question. They ask "can the AI answer this?" instead of "should the AI answer this on its own?"
We build managed AI colleagues for small and mid-sized companies. After running these setups in production, here is what actually matters.
Start with one repeating process, not with a chatbot
Pick a process that costs time every single week. Answering the same ten questions, completing incoming requests, preparing quotes, following up on leads. If a process does not repeat weekly, it is not a good starting point.
The first process should be live in two weeks. Not six months, not after a data project. Two weeks is enough to cover one workflow honestly.
The escalation matrix is the real product
The value is not in the answers the AI gives. It is in the rules for what it does not handle.
We define four levels for every process:
| Level | Who handles it | Example |
|---|---|---|
| 1 | AI answers directly | opening hours, lead times, standard pricing |
| 2 | AI drafts, human approves | quotes, planning changes, complaints |
| 3 | AI routes to a person | contract questions, legal, exceptions |
| 4 | AI stays out | anything about money or health |
Levels 3 and 4 are where trust is built. A colleague that knows when to stay silent is worth more than one that answers everything.
Measure before and after, per process
Pick three numbers before you start: time spent per week, response time, and error rate. If you cannot measure it, you cannot defend the project later.
What we would do differently
Do not start with the most complex process because it has the biggest payoff. Start with the process where the rules are already clear and written down. Complexity can come later, once the team trusts the setup.
If you want the full checklist we use for the intake and the first two weeks, it is here: Match-AI.
