Blog
Act, then tell: what the assistant is allowed to change
The AI in ainocrm never changes your pipeline quietly. It acts on what you said, tells you exactly what it did, only fills in what was empty from email, and asks when it is unsure — and here is why we dropped approvals.
The fastest way to lose a sales team's trust in an AI tool is to have it change something and not say so. The second fastest is to have it ask permission for everything — because then it is a form again, with extra steps.
ainocrm reads chat messages and emails and turns them into deal updates. That is its whole job. So from day one we needed a rule for what Aino, the assistant, is allowed to do with what it reads. Our first answer was approvals: the model suggested, the rep confirmed. But an approval queue is one more thing to keep up with, and a CRM that waits for it goes stale the same way a form does. This is the rule we replaced it with.
Act, then tell
When a rep says "call with Acme, they want to renew at 65k, closing this month", Aino does not propose anything. It logs the call, sets the value and the close date, moves the stage if the requirements are met, and adds the follow-up — and then it says exactly what it did, in one message. If any of it is wrong, "undo that" or "move it back" fixes it in a sentence.
The same goes for changes that happen when the rep is not looking. A stage moved by an email, a deal closed, a change made by a leader: the owner gets a notification for each. You are never told about your own actions, and never left to discover someone else's.
Three places it holds back
| Situation | What Aino does |
|---|---|
| An email mentions a value or a close date | Fills it in only if the deal has none. An email never overwrites what is already there. |
| It can't tell which customer or deal is meant | In chat, it asks — a short "did you mean…?" with the candidates. For an email, it files nothing rather than guess. |
| The change is hard to take back, or contradicts the record | Asks first: before deleting an opportunity, before saving an automation, and when a stated value disagrees with the products on the deal. |
Why not ask every time?
Because a question the rep answers "yes" to forty times a day is not a safeguard, it is a habit. When a customer writes "we can do €48k for two years if support is included", the useful thing is to log the email on the deal, fill the value in if there was none, and tell the owner. The rep reads one line and either agrees or corrects it. That is less work than an approval, and it gets read.
Ask, don't guess
Ambiguity is different. "Call with Jane, she is in" — which Jane? Which deal? A system that guesses and is wrong has just filed an interaction against the wrong opportunity, and nobody will notice until the review. So here Aino asks, with the candidates as buttons. It costs the rep one tap and saves the pipeline from a silent error.
The rule
Aino may change what you told it to, fill in what was empty, and must always say what it did. It asks when it is unsure, and before anything it cannot easily undo.
It means the assistant occasionally gets something wrong in plain sight. We think that is the right trade: a mistake you are told about costs one sentence to fix, and a CRM that waits for approval is one nobody keeps up to date. The concepts guide goes into the mechanics.
Get started
See it on your own pipeline
Start a workspace in a minute — no card, no forms. Or watch the demo first.