Item 1: Confirm Salesforce permissions for install
Installing the app requires: Download/Install AppExchange Packages, Modify All Data, Customize Application, Manage Users, Edit HTML Templates, and Manage Letterheads. Most customers have their System Administrator install the app — it’s fine to have a different user install versus authenticate.
Item 2: Decide whether to install in Sandbox or Production first
Production holds live customer data; Sandbox is for testing configurations. We recommend integrating with your sandbox first. On the Invoca side, the connection can be configured at the Network level or in each Profile — it’s helpful to connect your sandbox to a Profile with sufficient call volume to validate your configuration. You’ll always log in with your production credentials first, then choose whether to install in sandbox or production.
The Invoca package requires one user — the “Authenticating user” — to act as the integration’s owner. All Invoca Call Log records and Leads created by Invoca will show as “created by” that user, so we strongly recommend a dedicated user rather than tying the integration to an individual employee. This also avoids disruption from employee turnover.
Item 4: Set permissions for the authenticating user and app users
The User License must be “Salesforce” or “Salesforce Integration” (Force.com licenses aren’t supported).
Use Permission Sets to manage the required permissions (Setup > Users > Permission Sets).
Under Assigned Apps, check Default and Visible for the Invoca Enterprise app — there’s a separate app for Classic and Lightning; assign both if your users switch between them.
Under Object Settings, required permissions vary by object:
Object
Read
Create
Edit
Delete
View All
Modify All
Accounts
x
x
Contacts
x
x
x
Leads
x
x
x
Cases
x
x
Opportunities
x
x
x
Push Topics
x
x
x
x
Invoca Call Log
x
x
x
x
x
x
Invoca Conversion Mapping
x
x
x
x
x
x
Invoca Conversion Reporting
x
x
x
x
x
x
Invoca Error Logs
x
x
x
x
x
x
Under Field Permissions, ensure Read and Edit are set for all fields on Invoca Call Log, Invoca Conversion Mapping, Invoca Reportings, and Invoca Error Logs, plus any mapped fields on Accounts, Contacts, Leads, Opportunities, and Cases.
Invoca Admin and Invoca Console should be Default On.
Under Apex Class Access, enable the roughly 60 Apex classes with the namespace prefix INVOCA_FOR_SF — required for any user converting Leads or Opportunities if conversion reporting is enabled. Two classes (CallLogWrapper and CallStreamingController) use the AuraEnabled annotation, which Salesforce requires explicit permission for (as of August 2020).
Under Visualforce Page Access, enable the 4 pages with the INVOCA_FOR_SF prefix.
Under System Permissions, check Apex REST Services and Edit Tasks. If creating a dedicated integration user, consider enabling Password Never Expires.
If your org enforces IP address restrictions, allow-list these Invoca IP addresses:
