Skip to content
Assistant & search

Proposals you approve

The assistant writes, you decide. Nothing is recorded until you say so.

Last updated 1 min read

Nothing is written without permission

When you ask the assistant to do something — leave a note, create a task, correct a field — the result is a proposal, not a completed act. Until you approve it, no row is written to any table.

The proposal card shows exactly what will be recorded, plus where it will land: which client, which engagement, which contact.

If the destination cannot be named — a record deleted between the proposal and the render, say — the badge simply goes unnamed rather than the card breaking.

Three things you can do

  1. Approve it

    Exactly what was written is what gets recorded.

  2. Correct it first

    Change the wording and then approve. The edit goes through the same door and the same validation; an emptied note will not post. You can even turn a plain note into a decision.

  3. Discard it

    Nothing is recorded. Decided is also final: once approved or rejected, that card is no longer editable.

You are the author; the machine is marked

Anything recorded this way is written under your name — the person who approved it — but also carries a machine mark.

That mark is not decoration: activity created by the assistant does not count as human activity in measurement, or an engagement only the assistant had touched would read as freshly worked.

Two limits

Changing identity fields requires an admin approver. If you are not an admin, the proposal stays pending until an admin sees it.

If executing a proposal fails, no half-finished state is left behind: it either happened completely or not at all.

Still stuck?

If the answer wasn't here, write to us. It is a real inbox and it gets answered.

Talk to us