For Salesforce Integrations, there will be a point in time during the integration process where the API User will need to log in and establish the API connection and confirm access to the Conversica platform. This is the final step you will go through with your TAM in order to complete the Integration step. In the process, we have seen clients run into several common errors - all which can be avoided. Below, I will list some of these errors and show you how to bypass them in order to successfully complete the connection.

When trying to access Conversica through the Salesforce Dashboard you get…

1. A Conversica username and password login screen (Expected behavior - Once you click on the Conversica Link you should have access right away)

Solution: Try enabling third party cookies under your browser settings

2. An “Insufficient Permissions” error

Solution: Make sure you are accessing Conversica under the “All Items” section and NOT the “All Apps” section. This is a very common mistake that we see and it is important to make sure you are clicking on Conversica in the correct section. 

3. “This user is not authorized. You must be added as a Manager or Sales Rep in the Conversica Dashboard to view this page”

Solution: Make sure you are logged in as the API user. It is common to see clients entering their personal user creds here however, it is important to make sure that the correct creds are being entered.


     4. A Salesforce error saying there is an issue with the Canvas App (Conversica) 

Solution: Make sure the permissions/profile steps are set up correctly in the Salesforce Implementation Documentation which were sent to you by your TAM. Also, check to make sure the Connected App settings are set up correctly as seen in the image below. Here are 2 links that may be helpful: Configuring User Permissions Through Profiles or Permission Sets , Downloading the Conversica Package from the Salesforce AppExchange

     5. A prompt to enter your Salesforce credentials

Solution: Connected App setting #1 is not set correctly and must be set as shown in the image above.

     6. "Insufficient permissions: secure query included inaccessible field" under the visual force section 

Solution: The user does not have access to the fields on the CampaignMember object that our visual force section tries to load. The API user will need read access to see CampaignMember object.