It gets better at your business, not at business in general
Every company means something different by revenue, by overdue, by an active project. The assistant picks yours up as it works (the correction you made, the way you actually compute a figure, the table the answer really lives in) and uses them next time. You do not build this layer. It builds itself, from day one, without anyone being given a homework assignment.
Nobody writes the first entry
It is on by default and it runs on its own. When something gets settled in a conversation (a definition agreed, a correction made, a figure explained), the assistant writes it down, and a second, smaller agent checks it before it counts. Neither step asks anyone for anything.
It notices
The assistant writes an entry the moment something is settled: you corrected a figure, you named what a term means, it worked out which table actually holds the answer. It happens mid-conversation and costs you nothing.
after a correction, an agreed definition, an explained figure
What it picks up
Two kinds of thing, and they behave differently on purpose.
The semantic layer
A business term plus how to compute it. Always company scope, because a definition that is only true for one person is not a definition. An entry can carry the exact query that established a figure, so the next answer does not re-derive it. It replays it.
Over credit limit
A customer whose open Cust. Ledger Entry balance exceeds the Credit Limit (LCY) on the Customer card. Blocked customers are excluded.
- Triggers on
- credit limit
- kreditmaksimum
- over limit
- Stored recipe
- bc__read_data · Cust. Ledger Entry (21) · Open = true
- Used
- applied 34 times · retrieved 112 times
Memory
Lessons, preferences and corrections. Company scope for something true of the business, user scope for something true of one person's way of working. A user-scope memory learned inside a customer company is only ever retrieved back inside that company.
Report currency
This company reports in DKK even though several projects are invoiced in EUR. Convert before totalling across projects.
- Triggers on
- currency
- valuta
- EUR
- Scope
- company · memory
- Used
- retrieved 41 times
Why the next answer is better than the last
An entry does not sit in a settings page waiting to be read. It arrives in the conversation that needs it, by one of four routes.
- By name
A term appears, so its definition comes with it
A semantic entry is included in full when its title or one of its trigger keywords appears in the message. Below that threshold the assistant sees a list of at most thirty titles and can search for the rest.
- By tool
An entry can attach itself to a result
An entry bound to a tool (Job Ledger Entry reads, any Outlook call) is attached to that tool's result the moment it is used, and stays on the session afterwards.
- By meaning
Found by meaning, not by keyword
Memories are retrieved by meaning after every tool call: a close match arrives as its full body, a weaker one as a title the assistant can choose to open.
- By connection
Scoped to where it is true
A binding can hold an entry to one company, one Business Central environment, or every connection of a kind, so a rule about one environment does not follow you into another.
What you control, and what it will not do
The layer is yours to steer, and it is built so that steering it is optional rather than required.
- Moderation
A list, not a black box
Every entry is a row with a status, a scope and an owner. Read them, sort by how often each was actually used, edit one, delete one, restore one you retired, or write one yourself. A report query can be saved as a business term straight from the editor.
- Who approves
The second agent, or a person
By default the reviewing agent publishes and tells your administrators. Switch the policy to human review and a company-wide entry waits as a recommendation until an administrator confirms it.
- Switching it off
Two separate toggles
Learning and recall are independent, both per company, and personal memory follows the company's setting. Turning either off asks first and names exactly which answers get worse.
- When it breaks
No knowledge beats a failed answer
If the knowledge layer cannot be reached, the question is answered without it. A broken knowledge layer is never allowed to break an answer.
- How long it lasts
Until it stops being true
Entries are not conversations and do not expire with them. A definition that is still correct should outlive the chat that produced it. You can set an expiry anyway, and you are warned first that still-true terms will go with it.
Ask it the same question twice, a month apart
That is the honest demo of this one. We can also show you the layer a real company built without anyone touching it.
Or write to us at hello@uni4c.ai