Skip to content
Fonsent

An agent you can undo. It shows what it changed, what that was based on, and the way back.

Ask Fonsent to update your records in plain language. Small changes happen and are recorded. Anything bigger, and every email, waits for you.

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.

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

Delegation needs a way back. What usually goes missing.

  1. No record of what changedThe assistant edited twelve records. Which twelve, and from what to what?
  2. All or nothingEither the AI may do everything, or it may do nothing useful.
  3. No look before the leapYou find out what a request meant after it has been carried out.

How it works. Ask, look, apply, and walk it back if you need to.

Ask in plain language

Ask Fonsent reads your records and can update them. Each change leaves a card: what changed, from what to what, why, and Undo.

Look first

Turn on Preview changes to see what Fonsent would change before anything is written.

Rules for what it may do alone

Fonsent reads freely and makes small, reversible changes on its own, each recorded with an Undo.

  • Setting a field, moving a stage, creating a task: done, recorded, undoable.
  • Deleting, merging, bulk stage changes, new automations: drafted for a person.
  • Email: always a draft.

Undo that can’t trample newer work

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.

05

A complete history

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.

FonsentOpportunities
An opportunity record in Fonsent. The deal value, $96,000, is open to show its source: an email dated 12 November 2026 with the sentence that states the budget marked, who applied the change, and an Undo control.

Enforced

Held by the database, not by a prompt.

What the agent may do is decided in code and checked in Postgres. It doesn’t depend on the model following instructions.

Deleting, merging, bulk changes
Drafted for a person.
Email
Always a draft. An agent can’t approve one.
Undo after a newer edit
Refused, so newer work is never overwritten.
An API key or MCP request
Treated as an agent. The same rules apply.

Questions

What can the agent do without asking?

Read your records, and make small, reversible changes such as setting a field, moving a stage or creating a task. Each one is recorded with an Undo.

Can it send email on its own?

No. Email is always a draft that waits in For review until a person approves that exact text.

What if someone edited the field after the agent did?

Undo is refused, so the newer edit stays. Undo restores an earlier value only if nothing has changed it since.

Can I cap how much the model is used?

Yes. Model usage is metered in credits, and a workspace sets its own limit.

Do the rules apply to our own integrations?

Yes. A request made with an API key or through the MCP server is treated as an agent’s request, and it can’t approve a draft.

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.