A deal can look healthy in the pipeline long after the buyer has gone quiet. Every Monday, an Orkeste agent queries Salesforce for the open opportunities with the oldest activity, reads what happened last and posts a short list to your sales channel with a suggested next step for each.
The problem
Stalled deals are noticed at the forecast meeting, when weeks of momentum are already lost. Nobody has time to scan every opportunity for its last touch.
How the workflow runs
Runs: Every week on the day and hour you set.
Query Salesforce: The agent queries open opportunities ordered by last activity date and gets the five oldest.
Read the context: For each one, it reads the record and its latest logged activities.
Suggest a next step: It writes one line on why the deal may be stuck and what the rep could do.
Post to Slack: The list goes to the sales channel, or to one channel per team.
The manager decides: The sales manager and the rep decide what to do. The agent changes nothing in Salesforce here.
This workflow only reads Salesforce and posts to Slack. Any change to a deal is made by a person.
Who does what
Pipeline monitor: Finds the deals that went quiet and suggests a next step.
Sales manager (human): Decides which deals need action.
What this workflow does not do
Each query returns up to five opportunities; to cover more, run one agent per team or segment.
Judges stalls from Salesforce activity only; emails that were not logged are not seen.
Does not change stage, amount or owner in this workflow.