Update pipeline status in Salesforce from rep notes
Reps write notes and Salesforce lags behind. Paste your notes after a meeting and an Orkeste agent finds the opportunity, proposes the new stage or amount and logs the next step as an activity. Each change waits for the rep to approve it.
The problem
Pipeline accuracy depends on reps remembering to update Salesforce. They batch it the day before the forecast, or not at all, and managers plan on stale numbers.
How the workflow runs
Runs: When you start it with your notes.
Give it the notes: The rep starts the agent with the notes from one or several meetings, or points it to a Notion page.
Match the opportunities: The agent searches Salesforce for the opportunity each note refers to.
Propose changes: It proposes a new stage or amount when the notes justify it, and writes the next step.
Approve: Each change waits in Validations; the rep approves, edits or rejects it.
Update Salesforce: Approved changes update the opportunity, and the next step is logged as an activity.
Stage and amount changes wait for the rep's approval in Validations before they reach Salesforce.
Who does what
Pipeline updater: Turns notes into proposed opportunity changes.
Account executive (human): Approves every change.
What this workflow does not do
Changes stage and amount only; close date, owner and other fields are left to the rep.
Works from the notes you give it; it does not record or transcribe calls.