AI
AI with the context to actually help.
Most support AI generates plausible replies from the text of a message. This one reads the customer record, the approved knowledge and the finance ledger first — which is the difference between "refunds take three to five days" and "your €320 refund is scheduled for Thursday".
Three levels, kept distinct
Understand what is being asked. Suggest a resolution with its evidence. Act, but only within approved rules. Collapsing those three is how AI support goes wrong in public.
It never sees more than the person asking
Queries run with the agent's identity through the same permission checks as every screen. There is no separate AI permission model to drift out of step.
Fact, inference and recommendation are labelled
"Four cases this month" is a fact. "This customer may be losing patience" is an inference. "The account owner should call" is a recommendation. Presenting the second as the first is the failure that costs trust.
In this area
8 pages under AI.
Each one is its own surface in the product, and each one is here because it does something the others do not.
Understand
What is this customer actually asking, and about what?
ReadSuggest
A drafted reply, with the evidence it rests on.
ReadAct
Approved actions, inside rules you define.
ReadConfidence
Knowing when not to answer.
ReadAutonomy rules
Exactly what it may handle without a person, decided by you.
ReadWhere answers come from
Every claim cites the record behind it.
ReadPermissions
The assistant inherits the asker's access exactly.
ReadWhat it will not do
The line between helping a team and replacing a judgement.
ReadThe rest of Resolivo
This is one part of one loop.
Take better care of every customer.
Give your team the context, knowledge and AI they need to resolve problems properly — and know who needs attention before they ask.
Keep the mailbox you already use · The AI is never metered · [email protected]