Draft follow-up emails for Salesforce opportunities
Writing a personal follow-up for every open deal takes time nobody has. An Orkeste agent reads the opportunity and its recent activity in Salesforce and drafts a follow-up that builds on the last exchange. The rep approves each email; in Gmail it becomes a draft, in Outlook it is sent.
The problem
Reps fall back on the same template, or skip the follow-up when the week is busy. Prospects receive messages that ignore what they said last time, and deals go quiet.
How the workflow runs
Runs: Every week on the day you set, or when you start it for one deal.
Pick the opportunities: The agent queries Salesforce for open opportunities that match its briefing, such as no activity for ten days, up to five per query.
Read the history: It reads each opportunity and its logged activities.
Draft: It writes one follow-up per deal that refers to the last exchange and proposes a clear next step.
Approve: Each email waits in Validations; the rep edits, approves or rejects it.
Send or save: Approved emails are sent from Outlook or saved as Gmail drafts, and the follow-up can be logged as an activity.
No follow-up leaves without the rep's approval when approval is on, and in Gmail the rep still presses send.
Who does what
Follow-up writer: Drafts a personal email from the opportunity's history.
Account executive (human): Edits and approves each email.
What this workflow does not do
Writes one email per deal per run; it does not push sequences to an engagement tool.
Does not schedule emails for later; schedule the agent instead.
A Salesforce query returns up to five opportunities.