Sales

The CRM update from the call you just had

Pick the call that just ended. Aestus shows every HubSpot field it would change, with the words from the call, and writes nothing until you tick.

Join the waitlist See what it produces

After the call

Update CRM after calls

Who it is for: The account executive with four customer calls a day and a CRM that is always a day behind.
What starts it: You ask Drop after a call, from home or a ticket, or pick one of the calls Drop offers from your own calendar.; On demand

Coming soonUpdate CRM after calls is built, but not ready yet, so it cannot be turned on today. In Aestus you can ask to be told when it is ready.

After a customer call, the CRM is usually the last thing anybody updates, and it is updated from memory. The close date is a guess, the stage is whatever sounded right, and the next step never makes it in.

This use case starts from the call itself. Pick the call that just ended, or say which one, and Aestus reads what was said on it: the calendar event, the transcript or notes attached to it, and anything you wrote down. Every point it takes from the call is quoted word for word, with the file it came from.

Then a separate step finds the HubSpot records the call is about and reads what they say now. You get one table: each field, its value now, the value after, and the words from the call that justify the change. You tick the rows to write. A value Aestus is unsure of starts unticked, and nothing reaches HubSpot until you approve.

Aestus does not record calls. It reads only what your workspace can connect, and when there is nothing to read it says so instead of guessing. It never creates, archives or merges a record, and it writes no note onto the deal, because the HubSpot connection here has no tool for that.

What you get

The artifact this use case produces, in the product view you would read it in.

Example — fictional team and data. Not a live run or customer result.

Worked example

document

CRM update after Northwind renewal

Produced by: Run EXAMPLE-CRMC-01 · one approval · document artifact · nothing sent · demo values

Proposed changes: 3 rows, each with the value the field held when it was read, the value it would become, and the words from the call — "we're ready to move to contract" against the stage, "legal can sign by October 15th" against the close date.
Note recorded in Aestus: Northwind renewal call, 23 Sep 2026. Ready to move to contract; legal can sign by 15 Oct; order form to Priya by Friday; talking about 60 seats. Kept in Aestus: this product's HubSpot connection has no note tool, so nothing was written onto the deal as a note.
Not changed: They said 60 seats but named no price, and amount is not in this workspace's allowed field list, so it is reported rather than written.
Applied: 2 fields written in one update call, and 1 left unticked by the person approving — recorded as skipped, never written.

How it runs

Each step is one node in the workflow graph the interpreter runs. Nothing here is a prompt chain hidden in a route handler.

Workflow steps

01You pick the call
Drop offers the outside calls on your own calendar that ended in the last day and a half — "Northwind renewal · 42 min" — or you say it in words. The call is the whole input.
02It reads what was said
From the calendar event, the transcript or notes Google Meet attached to it in Google Drive, and any notes you paste. Aestus does not record calls, so it reads only what you can connect. Every point it finds is a word-for-word quote with the file it came from. This step holds no CRM.
03It finds the records and reads them now
A second step, holding HubSpot read-only, finds the deal from the guests on the call and reads the current value of every field the call touches, with the second it read each one. Two matching deals is not a guess: it says so and proposes nothing.
04You tick the rows to write
One table: the field, the value now, the value after, and the words from the call. You untick anything you do not want, and a value Aestus is unsure of starts unticked. Nothing reaches HubSpot before you approve.
05It writes, re-reading each field first
A value somebody changed by hand while you were deciding is skipped and recorded, never written over. Every row shows what happened: written, skipped by you, or what HubSpot said.

By hand, and on Aestus

The same job, on either side.

By hand
Update the CRM from memory at the end of the day.
On Aestus
Right after the call, from what was actually said.
By hand
A close date moves and nobody knows who moved it or why.
On Aestus
Every row carries the words from the call and the value it replaced.
By hand
An assistant writes straight into the CRM.
On Aestus
Nothing is written until you tick the rows, and an unsure value starts unticked.
By hand
Somebody edits the deal while the update is being typed.
On Aestus
Each field is read again at the moment of writing, and a value that moved is skipped.
By hand
A call that mentions a new logo creates a duplicate company.
On Aestus
No record is ever created, archived, deleted or merged.

What Aestus records

Every run is auditable after the fact, which is what makes handing the job over survivable.

The changeset
One document per call, with the proposal, your choices and the result of every write in the same place.
The run
Cost, tokens, duration and a failure code if it failed, on the same ledger as every other run in the workspace.
Nothing sent
It writes to HubSpot after you approve and posts nothing to Slack or email.

What it connects to

Only the tools this workflow actually uses. Each one has a setup guide.

Questions teams ask

Where does it hear the call?

Aestus does not record calls and has no Gong, Zoom or Fireflies connection. It reads the Google Calendar event, the transcript or notes Google Meet attaches to it in Google Drive, and notes you paste into the card. With none of those, it proposes nothing and says what it could not read.

Does anything change before I approve?

No. The step that can change a record is reachable only through your approval, and that approval carries the customer-record permission the runtime checks for.

Does it log a note on the HubSpot call?

No. The HubSpot connection here has no note or engagement tool, so the call note is kept in the Aestus document instead, and the document says so.

Can something said on the call tell it to do something else?

No. A transcript is treated as words somebody said, never as an instruction. The step that reads it holds no CRM, the step that holds the CRM cannot write, and the fields it may write are a setting no run can widen.

All use cases How access is governed

Sources

lib/domain/use-cases/update-crm-after-calls/seed.ts — which step holds which connection, and the one approval
lib/domain/use-cases/update-crm-after-calls/reader.ts — the call reading and the check that every quote came from it
lib/domain/use-cases/update-your-crm-from-slack/reader.ts — the changeset contract both CRM use cases share

Hand over Update CRM after calls.

Tell us how your team does this today and we will set it up with you.

Talk to us

Update CRM after calls

Who it is for

The account executive with four customer calls a day and a CRM that is always a day behind.

What starts it

You ask Drop after a call, from home or a ticket, or pick one of the calls Drop offers from your own calendar.

On demand

Coming soonUpdate CRM after calls is built, but not ready yet, so it cannot be turned on today. In Aestus you can ask to be told when it is ready.

Questions teams ask

Where does it hear the call?

Does anything change before I approve?

No. The step that can change a record is reachable only through your approval, and that approval carries the customer-record permission the runtime checks for.

Does it log a note on the HubSpot call?

No. The HubSpot connection here has no note or engagement tool, so the call note is kept in the Aestus document instead, and the document says so.

Can something said on the call tell it to do something else?

Sources

lib/domain/use-cases/update-crm-after-calls/seed.ts — which step holds which connection, and the one approval

lib/domain/use-cases/update-crm-after-calls/reader.ts — the call reading and the check that every quote came from it

lib/domain/use-cases/update-your-crm-from-slack/reader.ts — the changeset contract both CRM use cases share

The CRM update from the call you just had

Update CRM after calls

What you get

CRM update after Northwind renewal

How it runs

By hand, and on Aestus

What Aestus records

The changeset

The run

Nothing sent

What it connects to

Questions teams ask

Other use cases

Hand over Update CRM after calls.

The CRM update from the call you just had

Update CRM after calls

What you get

CRM update after Northwind renewal

How it runs

By hand, and on Aestus

What Aestus records

The changeset

The run

Nothing sent

What it connects to

Questions teams ask

Other use cases

Hand over Update CRM after calls.