Why CRM-native
An integration gives you a copy of the data. Native gives you the data model.
Orca's advocate objects, reports and dashboards install in Salesforce, related to the Accounts and Opportunities you already report on.
One line for your admin
Orca installs in Salesforce as a managed package: our advocate and reference records would live in our org, related to the Accounts and Opportunities we already report on.
01 · At a glance
What your admin is signing off on.
The install, the records and what runs where, in one place.
Admin review · Spec sheet · For your admin · 01Install · Salesforce managed package
02Records in your org
Advocate and reference records
03Related to · Accounts and Opportunities · 04Ships with
Permission sets, page layouts, reports and dashboards
Flows, validation rules, approvals and alerts run on Orca records
06Runs outside Salesforce
Call processing by Echo, Orca's Customer Intelligence Agent. Subprocessors at trust.orcaforce.co
02 · The data model
Objects your admin can open in Object Manager.
Advocate and reference records sit beside Accounts and Opportunities, so your admin governs them like every other object in the org.
Setup · Object Manager
AccountStandard object
Advocates · Related list · From Advocate
AdvocateCustom object · Orca
To Account · Owner · To User · References · From Reference
Reference · Fields & Relationships · Field label · Data type · Details · Opportunity · Relationship · To Opportunity · Advocate · Relationship · To Advocate · Type · Picklist · Call · Quote · Status · Picklist · Approved · Booked
An install, not a project
- Install the managed package Your admin installs Orca into your Salesforce org.
- Permission sets Included in the package.
- Page layouts Included, related to Accounts and Opportunities.
- Reports and dashboards Included in the package.
03 · For your admin
To an admin, the data model is the outcome.
An install instead of a project, and three things that follow from it.
AUTOMATION
Your admin's tools just work
Flows, validation rules, approvals and alerts run on Orca records like any other record.
REPORTING
Reportable against revenue
A standard Salesforce report shows which deals used a reference.
DOWNSTREAM
Everything that reads Salesforce reads Orca
BI, the data warehouse, forecasting, and AI agents grounded on CRM data, with no new connector.
04 · Why native
Where does the record live?
An integration is a spreadsheet someone emails you every night. It is a day-old copy, and you cannot add your own formulas. Native is the shared sheet you already work in.
The record lives in another system
Salesforce works from a synced copy
The record lives in Salesforce
Orca's advocate and reference records, in your org
Where the record lives
In the other system, with a copy synced to Salesforce
In your Salesforce org
Reporting
Reports run on the fields that sync
Standard reports, related to Accounts and Opportunities
Automation
Flows see the synced copy
Flows, validation rules and approvals run on the record
Access
Permissions set in two places
Your sharing model and permission sets
Upkeep
A renamed field or an expired token can stop the sync
Fields, layouts and permissions your admin already manages
Orca integrates too, with Gong and Slack among others. The difference is where Orca's own advocate and reference records live.
Where each record lives
Your Salesforce org
Your sharing model and permission sets apply
Account · Standard object · Advocate · Orca object · Reference · Orca object · Opportunity · Standard object
Your admin's tools run on these records
Flows · Validation rules · Approvals · Reports · Dashboards · Sharing and permissions
Echo reads account and opportunity context
Echo writes signals and activity back to the records
Echo's call processing. Subprocessors are listed at trust.orcaforce.co
Gong · Calls and transcripts · Echo · Call processing · Slack
Signals to your team
05 · Admin FAQ
Questions admins ask before they say yes.
Straight answers about the install, the records and what runs where.
What does Orca install in Salesforce?
A managed package. It adds the advocate objects and fields, their relationships to Account and Opportunity, page layouts, permission sets, reports and dashboards.
Which records live in our org?
Your advocate and reference records, related to the Accounts and Opportunities you already report on.
Does anything run outside Salesforce?
Yes. Echo's call processing runs outside Salesforce. Your advocate and reference records live in your org, and the current subprocessor list is at trust.orcaforce.co.
Can our admin build Flows and validation rules on Orca records?
Yes. Flows, validation rules, approvals and alerts run on Orca records like any other record.
Can we report on which deals used a reference?
Yes. A standard Salesforce report shows which deals used a reference.
Where can our security team review Orca?
Reports, policies and subprocessors are current and public at trust.orcaforce.co.
06 · Proof
Live in the org they already ran.
BMC · replaced a three-tool stack
“It's perfect the way it is.”
BMC, at renewal
Salesforce dashboards live within weeks of rollout.
Renewed with zero change requests.
Replaced a three-tool stack with records in the org they already ran.
Bring your admin. Every record will look familiar.
A thirty-minute walkthrough of the objects, the install and the reports.