Skip to main content
Starting in version 5.5 of the Invoca Salesforce managed package, Caller ID is used as the default matching key — so it no longer appears as an option in Custom Field Matching.
Applies to: Invoca Salesforce managed package, version 5.5 and later; the “Optional: Custom Field Matching” section, under the “Invoca Fields” column, in your Salesforce environment

​
Symptoms

Version 5.5 of the Invoca Salesforce managed package behaves differently than version 5.3 and earlier: it uses SOQL (Salesforce Object Query Language) to match all phone fields to the Caller ID on every object selected in this setting.

​
Cause

In package versions 5.3 and earlier, you could select “Caller ID” as the key used to match other objects. Version 5.5 removed this option because it now uses Caller ID as the default match automatically.

​
Resolution

No action is needed — version 5.5 and later already match on Caller ID by default, so this configuration isn’t necessary. If you’d like to set custom matching criteria beyond the default, upgrade to the most recent version of the package from the Invoca listing on the Salesforce AppExchange, which restores the option to select “Caller ID” manually.

​
Where to go next

Last modified on September 24, 2026