Klientintegration - VoIPcube-klient obligatorisk
Introduktion
The user will get a pop-up on the ringing event of an incoming call. There are 2 types of pop-ups that may be shown depending on if a contact could be found for the phone number:
-
A pop-up showing the contact info, which contains a deeplink to the contact in Salesforce and a form where the user can make a note of the phone call. This note will then be logged in Salesforce under the contact.
• A pop-up where a new contact can be made, which will be stored in Salesforce
When the contact is saved it will immediately present a pop-up so that a call note may still be created.
A configuration option also exists that will open the contact page in Salesforce when the call is connected.
Usage
Contact information
The contact information is fetched based on the phone number that calls, for the contact to be found by VoIPcube it must be registered under Phoneor Mobile. Other phone fields such as HomePhoneor OtherPhonewill not be recognized. It does not matter for the integration if the phone number is recorded using the national or international format, as it searches for the contact based on the last 7 digits of the number.
For the complete set of information to be shown in the pop-up make sure the following fields are filled in the contact: FirstName, LastName, Title, Account, and Department.
Call note
When a call note is made, the phone call will be logged on the contact. If the call is opened it will show the posted note.
If no note was posted the call will not be logged in Salesforce
Create contact
If no contact has been found the user will be presented with the option to create a contact from the pop-up. The contact will be saved in Salesforce, the pop-up will fill in the FirstName, LastName, and Phonefields.
Configuration
The Salesforce integration authenticates using OAuth2.0. This means that users will log in with their own Salesforce credentials. VoIPcube will automatically present the login screen when required. To configure Salesforce for authenticating with OAuth2.0 execute the following steps:
· Get administration rights in the Salesforce account, or let the Salesforce administrator execute the steps below)
· Go to the Setup page
· Go to Apps > App Manager
· In the top right click ‘New Connected App’
· Select the option Create a Connected App
· Enter the mandatory fields. E.g.
· At the API section API. Click on ‘Enable OAuth settings’.
o For callback url enter the following https://voipcube.nl/authorize o For scopes choose: ManageuserdataviaAPIs(api)+ Performrequestsatany time(refresh_token,offline_access)
o Check require secret for web server flow
o Check require secret for refresh token flow
· Leave the other options unmarked and press ‘save’
· After saving you can see the consumer key + consumer secret. Make sure to store these.
· Go to Apps > Connected Apps > Manage Connected Apps
· Click on the connected app you just created and click 'edit policies' · Adapt the configuration with the options provided below:
o Permitted Users > All users may self authorize
o Timeout Value > 24 hours
o Refresh Token Policy > expire refresh token if not used for 10 days
· Click Save.
Assignment
Values
To assign the integration the following pieces of data are needed:
· The Salesforce domain, this can be found by navigating to the Salesforce environment and copying the domain from the URL, it is situated between https:// and .lightning.force.comin the example below the domain is destinybv-dev-ed.
Authentication
For the authentication the following pieces of data are needed:
· The domain that was gathered in last step
· The consumer key from the configuration
· The consumer secret from the configuration
For this integration use the V4 (Search on last 7 digits)
version of the integration and assign the values in the following manner:
-
toggle this switch on or off depending on if the contact record should open automatically when the call is connected.
When the user logs into the VoIPcube Client the first time after the integration has been assigned, they will be presented with the OAuth2.0 authentication screen. They can use their own Salesforce credentials to log in here.
Once this is complete the integration will be fully functional.
So far no known issues outside of proper configuration have been found. If you still encounter issues please contact support@dstny.se with the problem.