Skip to content
Fonsent

Give AI a job description. Decide what it may change, who may approve, and see everything it did.

Field modes, roles, a required second step at sign-in, a usage limit and an audit log: the controls you would want before letting software write to your CRM.

FonsentSettings · Agent
Agent settings. Each field is set to Auto, Suggest or Off: Next steps and Competitors on Auto, Deal value and Close date on Suggest, Stage on Off.

The problem

“The AI did it” is not an answer. When a value is wrong or a message should not have gone out, someone has to be able to say what happened, and stop it happening again.

What you get. For admins, operations and anyone accountable for the data.

A mode for every field

Auto, Suggest or Off, field by field. Let Fonsent keep next steps current on its own, and make it ask before it touches a deal value.

  • A person’s own edit always wins over an older source.

Four roles

Owner, Admin, Member and Viewer. Members run the agent and approve; a Viewer is read-only.

03

A second step at sign-in

Fonsent supports 2-step verification with an authenticator app, and a workspace can require it for everyone.

FonsentSettings · Security
Security settings: 2-step verification with an authenticator app is on, the workspace requires it for everyone, sign-in is by email and password, and there are controls to sign out other sessions or everywhere.

An audit log of every change

By people, the agent, automations and API clients, with before and after values and undo status.

Limits on spend and on keys

Model usage is metered in credits, and a workspace sets its own limit. API keys are read-only or editor, and each is limited to 120 requests a minute.

Your data leaves when you say

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

Built for trust

Controls that hold without supervision.

The rules below are enforced in the database, for every person, agent and integration.

Another workspace’s data
Not readable. Every table enforces row-level security.
A Viewer
Read-only.
An integration’s request
Treated as an agent’s. It can’t approve a draft.
A field on Off
Never touched by Fonsent.

Questions

Can we stop the agent touching certain fields?

Yes. Set the field to Off and Fonsent never touches it.

Can a Viewer approve or change anything?

No. A Viewer is read-only.

Is there single sign-on?

Not yet. You sign in with an email address and a password, and can add 2-step verification. Single sign-on (SAML) isn’t set up.

Can we see what an integration did?

Yes. The audit log includes changes made by API clients, with before and after values.

Can we get all our data out?

Yes. Every object exports as CSV, and the whole workspace exports 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.