The platform / Prepared work and approvals

Useful work arrives. You decide what happens next.

When Zarco spots a gap, it can bring the evidence and prepared work to your Inbox. Review the recipient, message and quote, then decide whether the action should go ahead.

See the product view

What has Zarco prepared for me to review?

Zarco has surfaced the gap in your Inbox with the evidence, a draft email and a quote for review.

Illustrative product film. No live connections or actions.

The film is illustrative. It demonstrates the review sequence without connecting to an inbox, changing a record or sending a message.

Approval is a decision, not a blind hand-off.

The project surfaces the work

A renewal gap, an account concern or a missing next step becomes an Inbox item with an explanation and supporting evidence. The team can distinguish a task, a question, a draft and an action awaiting approval.

Review what will actually happen

Inspect the recipient, subject, wording, quote values and attachment. Edit the prepared work or return it with context. For a send action, the review should make the customer-facing message and its destination clear.

Approve the action, then check the result

Approval can execute the defined action through the connected system. It is not proof of delivery: a failed action stays visible for retry. Later actions continue to follow the same permissions and applicable policies.

Three separate controls, not one permission switch.

Knowing something, preparing something and sending something are different capabilities. Configure each deliberately.

Connected access

Which systems and records are available in the workspace and to the agent.

Connecting a source supplies context within the granted scope. It does not by itself mean every possible action is allowed.

Action permissions

What an agent may create, update, send or delete without asking.

Keep customer-facing actions held for review where required. Permit unattended work only where you intend it.

Approval policies

The conditions that allow, hold or deny a supported action.

Apply the relevant project or workspace policy. The reviewer sees the proposed action, not a blanket grant of future access.

The execution record

What was approved, what was attempted and whether it succeeded.

Track the actual result. A failed send needs attention; approval alone must not be counted as customer contact.

The evidence and the exact work, together.

Draft reviewAwaiting your decision
Prepared work

Email with quote

Draft #1
Edit draftReturn for changesApprove defined action

Static example only. Nothing is connected, edited, approved or sent.

Before you start.

Does approval let an agent do anything afterwards?

No. Approval applies to the prepared action being reviewed. Future actions still follow the workspace permissions and approval rules.

Can someone change a draft before approving it?

Yes. The review pattern is designed for people to inspect and edit prepared work before deciding what happens next.

Will this example send the email?

No. Everything on this page is illustrative. Nothing is connected, saved, approved or sent.

Does every action always need approval?

Not necessarily. Your configuration determines what can run without asking and which actions are held or denied. The film shows the reviewed path. Grant autonomy deliberately, within the available connections and policy controls.

What if an approved send fails?

The action should remain visibly failed or awaiting retry, rather than being labelled sent merely because someone approved it. Check the execution result before treating the customer as contacted.

Bring your working context into the room.

We’ll show you how Zarco could fit your sources, rules and approval boundaries.

Arrange a demo

Opens an email to luke@zarco.uk. No calendar slot is reserved.