Qualify inbound leads with Salesforce: the recipe

This is the Salesforce version of automated lead qualification. An Orkeste agent reads inbound emails, searches Salesforce for the contact, the account and any open opportunity, applies your criteria and posts the qualified leads to your sales channel. It logs the exchange on the record so the rep starts with the context.

The problem

Inbound requests land in a shared inbox and wait for someone to check whether the company is already a customer, whether a deal is open and whether the request fits. The good ones cool down in the meantime.

How the workflow runs

Runs: Every hour, or when you start it.

  1. Read inbound emails: The agent reads recent emails in the sales inbox, in Gmail or Outlook.
  2. Check Salesforce: For each sender, it searches Salesforce for the contact, the account and open opportunities.
  3. Apply your criteria: It checks the request against its briefing: company size, need, budget or deadline mentioned.
  4. Approve: If you keep Salesforce changes behind approval, the activity waits in Validations for a rep.
  5. Log the activity: When the contact exists, it logs an activity on the record with a summary of the request.
  6. Post to Slack: Qualified leads are posted to the sales channel with the reason, and new companies are flagged for a rep to create.

Changes in Salesforce can wait for a rep's approval in Validations. The reply to the prospect stays with the rep, or with a reply drafter that also waits for approval.

Who does what

What this workflow does not do

Works with your stack

Part of a guide

Questions about this workflow

What if the lead is not in Salesforce yet?

Agents cannot create leads or accounts in Salesforce today. The Slack post flags the new company so a rep creates the record. In HubSpot, the agent can create the contact and the deal itself.

Can it enrich the company from the web?

No. Agents have no web access. They work from the email, your Salesforce data and the knowledge you give them.

Can it reply to the prospect?

Add a reply step: the agent drafts the answer, which waits in Validations. In Gmail an approved reply becomes a draft; in Outlook it is sent.

Related workflows

Keep reading