Salesforce + Revenue Force
Sign in with Salesforce to import contacts, including your custom __c fields, and write outcomes back as activity.
Keeps every qualified opportunity tied to your CRM
Salesforce connects to your Revenue Force workspace, so opportunities are developed from the people already in your system of record. Contacts and their custom fields come in to personalize the outreach, and approved outcomes are written back, so you see the opportunity and the conversation in both places without a single export.
Salesforce in, execution under the standard you set, outcomes back to you.
Contacts + custom fields
Written back as activity in Salesforce, off until you enable it.
What flows in
From Salesforce into your Revenue Force workspace: the contacts, companies, and custom fields the outreach personalizes from.
- Leads and contacts with standard and custom __c fields
- Reports and filtered views into your contact book or a campaign
- Custom fields become personalization merge variables
What flows back
From Revenue Force into Salesforce: the outcomes you approve, so the system of record reflects what actually happened. Off by default, on when you say so.
- Reply state, qualification, and opportunity outcomes written back as activity
- Unsubscribes kept in sync with Salesforce
- Write-back off until you enable it: you choose which events leave
Connected in a couple of minutes.
Custom __c fields survive the import and become merge variables, backed by the same background, resumable pipeline with verification, do-not-contact, and dedupe on every record. Qualified opportunities are recorded back in Salesforce once write-back is on.
Click Connect and sign in with Salesforce (OAuth)
Authorize the workspace-scoped connection
Choose what to import and, optionally, turn on write-back
Your account. Your workspace. Your call.
Connecting Salesforce imports on your terms and writes back only what you approve. The connection is yours, scoped to your workspace only, and off-by-default write-back means nothing changes in Salesforce until you turn it on.
Write-back is off by default
Contacts import when you choose. Reply state, qualification, and qualified opportunity outcomes flow back into Salesforce only after you enable them, event by event, never automatically.
Scoped to your workspace only
Your account, your token, your data. A connection lives in one workspace and is never shared across tenants.
Disconnect in one click
Change your mind anytime. Disconnect and the stored credential is cleared immediately. No email, no waiting.
Human approval is the default starting point. Revenue Force proposes, you review, and autonomy increases only when you choose, connection by connection. You set the pace.
Everything a careful buyer should ask.
Is the Salesforce integration available now?
It is fully built and rolling out: it activates the moment our Salesforce OAuth credentials are live. The connect flow is a standard Sign in with Salesforce.
Do custom __c fields import?
Yes. Standard and custom __c fields carry through and become personalization merge variables.
What flows back to Salesforce?
Reply state, qualification, opportunity outcomes, and unsubscribes, but only after you turn write-back on.
How is the connection scoped?
Per workspace, via OAuth, revocable in one click. Your connection is never shared with other workspaces.
Ready to run Revenue Force on Salesforce?
Book a Revenue Force call to see how the people already in Salesforce become qualified opportunities: the target market you define, the standard an opportunity has to meet, and which outcomes flow back to your system of record.