OAuth Connection
Koncert integrates with Salesforce through OAuth, enabling secure communication between the two platforms. Each connection generates an access token that allows Koncert to interact with the Salesforce API.
Scopes:
Koncert requests the following scopes.
| Object/Scope | Description |
|
Access the identity URL service (id, profile, email, address, phone) |
Allows access to the identity URL service. You can request a profile, email, address, or phone individually to get the same result as using id because they’re synonymous. |
|
Manage user data via Web browsers (web) |
Allows use of the access_token on the web. This scope also includes visualforce, allowing access to customer-created Visualforce pages. |
|
Manage user data via APIs (api) |
Allows access to the current, logged-in user’s account using APIs, such as REST API and Bulk API 2.0. This scope also includes chatter_api, which allows access to Connect REST API resources. |
|
Perform requests at any time (refresh_token, offline_access) |
Allows a refresh token to be returned when the requesting client is eligible to receive one. With a refresh token, the app can interact with the user’s data while the user is offline. This token is synonymous with requesting offline_access. |
Tokens adhere to the access roles and permissions of the user, limiting access to what the user can see within Salesforce. Occasionally, these tokens may expire, prompting a re-connection request from Koncert.
For more details and documentation on Salesforce OAuth connections and the SFDC API:
How the Integration Works
Koncert uses a “real-time” access approach to ensure data from Salesforce is always current.
The below diagram shows how Koncert uses this access model to load contacts from a report and log calls after they've been made.
The frontend client makes a request to Salesforce using its API to load the report as a list of Call Tasks. As the client performs calls on each prospect, the client submits a request to log these calls in Salesforce based on the workflow defined in Koncert.
Data Permissions, Objects & Retention
Permissions Model
Koncert uses the standard SFDC data models and inherits access roles from Salesforce. Custom fields will be retrieved based on permissions defined in Salesforce; Koncert users will only be able to see fields that they are able to see on Salesforce itself.
List of SFDC Objects
Koncert interacts with the following standard objects in Salesforce.
- Contact/Account
- Lead
- Activity
Koncert also supports custom objects that are linked with Contact/Lead at this time.
Data Retention
Koncert stores minimal data needed for dialing purposes such as Account Name, Contact Name, Title, and Phone Number. There can be additional fields mapped and stored from Salesforce. After we dial, we store the call details of those records for a period of 180 days, and will be purged. Also the user has the ability to delete a specific prospect information from the Koncert platform.
Rate Limiting & Throttling
Koncert uses the API limit available for that user in Salesforce. If the API limit is exceeded, the Koncert system alerts the user with an message and stops syncing.
Please refer to this link for more information about getting started with Koncert.
https://kb.koncert.com/hc/en-us/articles/18013746975127-Getting-Started-with-Salesforce
Please contact Koncert Support for any questions at support@koncert.com or 603-952-2505.
NOTE: The information provided here is for informational purposes only and should not be considered as a legal advice. Please consult your legal counsel regarding compliance with relevant laws.