Skip to content
Talk to usSee a demo

The model proposes the change.
Proxara commits it under the firm’s rules.

A Salesforce update, an Outlook follow-up, a Karbon task: typed actions the model proposes with stand-ins, never with a credential or a client name. Proxara resolves the real client inside the firm, runs what policy permits, holds what needs a person, and confirms each change in the system it landed in.

Start with the pilotProxara Connect

The advisor asks the model to wrap up a client review. The model proposes three typed actions against stand-ins: a Salesforce record update, an Outlook follow-up, a Karbon task. Each proposal passes the catalogue gate, is matched to the real client record inside the firm, is checked against the advisor’s own permissions and the current record, and is given its lane: the update and the task run automatically; the send waits. In a private review the advisor sees the real recipient, Ruth Calloway, edits if needed, and confirms once. The model is told only that the send was held, never for whom.

How a proposal becomes a committed change.

One request from an advisor. Three typed actions. Two run on policy, one waits for a person.

How a proposal becomes a committed change.

One request from an advisor. Three typed actions. Two run on policy, one waits for a person.

01

The model proposes known actions

The model never holds a credential or an open API. From a closed catalogue it proposes typed work: update a record, send an email, create a task. Every field is named, every target is a stand-in issued for this job, and anything outside the catalogue is rejected.

Wrap up my 2:00 client review: log the outcome, send the follow-up we agreed, and set up the trust-amendment task.

Proxara · connected
update_record
fieldAnnual review → Complete
record[CLIENT_R4]
send_email
subjectFollowing up on today’s review
to[CLIENT_R4]
create_task
titleCollect signed trust amendment
assignee[STAFF_P2] · due 12 Aug

Action catalogue · a closed set

update_recordSalesforce
send_emailOutlook
create_taskKarbon

No entry exists: money movement · trading · payment details

02

The real client is matched inside the firm

Proxara resolves each stand-in to the current client record and checks the advisor’s own permissions against the record as it stands now. Then every action gets its lane: internal, reversible work runs automatically under policy; anything a client will see waits for the advisor; a change the firm flags needs two people; and some changes have no entry in the catalogue at all.

Checked inside the firm

[CLIENT_R4]the current client record

Real client resolved

The advisor’s own permissions

Records unchanged since read

Consequence classed

Runs automaticallyinternal, reversible workupdate_recordcreate_task
The advisor confirmsanything a client will seesend_email · held
Two people approvewhere firm policy requires it
No entry in the cataloguenothing exists to travel on

03

The advisor sees the real names. The model sees a status.

Before the follow-up goes anywhere, the advisor opens a private review inside the firm: the real recipient, the exact text, an edit if needed, one confirmation. The model is told the send is held. It is never told for whom.

Private review · Daniel Osei
Send toRuth Calloway · ruth.calloway@calloway.co

Thanks for today. As agreed, the September rebalancing is going ahead, and the trust amendment is on its way to you for signature.

Edit draftConfirm send

Already running under policy: Salesforce update · Karbon task

What the model is told

update_record · permitted

create_task · permitted

send_email · held for confirmation

Status, never the name.

04

Every change is confirmed in the system it landed in.

Before Proxara touches a system, the exact intended change is written down. If the record changed since the model read it, or a recipient is no longer valid, the action stops before it runs. After the write, Proxara confirms the result in the system itself: an unconfirmed change becomes a check, never a guess and never a quiet retry.

A check that cannot be settled stays open, with a named owner, until a person or a later read resolves it. It never becomes a claimed success.

The firm sets how far actions reach.

Many firms start read-only. Then internal work: tasks, notes, statuses. Then drafts. Then approved external sends. Each step is a policy setting on the same catalogue, not a new product.

Real changes, under the firm's rules.

Tell us which systems the firm wants AI to write to, and a person will reply.

Talk to us