Skip to content
Fonsent

How to audit what AI changed in your CRM

Pick one field and ask three things: what was its last change, who or what made it, and can it be undone. A trail worth the name answers all three for people, agents, automations and API clients alike, with the value before and after.

Updated · 2 min read · Fonsent

In early access today. The AI model isn’t switched on yet. Field updates come from built-in rules, which pick up only sentences that state a value outright. What works today

When software can write to your records, “who changed this?” needs a better answer than the name of an integration. An audit is possible only if the product kept the right things at the moment of the change. They can’t be reconstructed afterwards.

Five things to check

Pick a field that matters, such as a deal’s amount or its close date.

  1. Ask for the field’s last change, with the value before and after.In Fonsent. The audit log lists every change in the workspace, by people, the agent, automations and API clients, with before and after values and undo status.
  2. Ask what a change made with an API key counts as: a person’s, or an agent’s.In Fonsent. A request made with an API key or through the MCP server is treated as an agent’s request. The same rules apply, and it can’t approve a draft.
  3. Ask to see what the agent would change before it writes anything.In Fonsent. Turn on Preview changes to see what Fonsent would change before anything is written.
  4. Undo a change that someone has edited since.In Fonsent. Undo restores the earlier value only if nothing has edited it since. A change across several records is undone in one step, all or nothing.
  5. Ask which changes the agent makes alone, and which it has to draft.In Fonsent. Fonsent reads freely and makes small, reversible changes on its own, each recorded with an Undo. Deleting, merging, bulk stage changes and new automations are drafted for a person. Email is always a draft.
FonsentChat
A chat with Fonsent. A person asks to move a deal to Won; a card shows the stage change from Proposal to Won, that the agent applied it 30 seconds ago, and an Undo control.

A log you can act on

Most products keep some history. The useful question is what you can do with it. A log that names the actor, shows both values and carries an undo lets you correct a mistake in the place you found it. A log that only says something changed sends you to a backup.

Watch what undo does when the record has moved on. Restoring an old value over a newer edit is quiet data loss. Refusing, and saying why, is the safe answer.

Where it stops

A log shows what changed and who or what changed it. Whether the change was right is still a reading, and for that you need the sentence it was based on.

Open any value to read why it says what it says: the source and its date, the quote in context, who applied it, and Undo.

One thing can’t be undone at all, and the log doesn’t pretend otherwise. A sent email is never shown as undone.

The product page shows the rules and the history together: an agent you can undo.

Questions

Short answers to what people ask next.

Does the log include changes made through the API?

Yes. The audit log lists every change in the workspace, by people, the agent, automations and API clients.

Can an undo overwrite newer work?

No. Undo restores the earlier value only if nothing has edited it since.

Can one undo cover many records?

Yes. A change across several records is undone in one step, all or nothing.

Can I take the data out and audit it elsewhere?

Yes. Export any object as CSV, or the whole workspace as JSON.

Start with your own records.

Create an account, import a CSV or a few emails, and read the first proposals with their quotes. An import is one change you can undo.

Early access. No payment details are asked for.