This article covers the technical details of how integration works between Koncert and Salesloft.
OAuth Connection scopes
Koncert integrates with Salesloft using OAuth 2.0, allowing secure interaction between the platforms. Each connection uses an Access Token that allows Koncert to communicate with the Salesloft API.
Each user must individually authorize and connect their Salesloft account to Koncert.
Scopes
Koncert requires the following scopes to function effectively.
| Object/Scope | Description |
| Accounts: Manage | Read and write ALL account, account stages, account tier data; upsert accounts; delete account data |
| Activities: Write | Read activity history and create activities |
| Admin: Read | Read a team, group and individual user data, including team level tags, team templates and attachments |
| Cadences: Read | Read ALL cadences, cadence memberships, steps, actions and ongoing actions |
| Calls: Manage | Read and write ALL call data, including call instructions, call data records, call dispositions, call sentiments, caller ids, phone number assignments and recording settings |
| Notes: Write | Read and write notes |
| People: Write | Read, write, and upsert ALL people data, including stages and successes |
| Tasks: Write | Read and write tasks |
Koncert manages access token validity by utilizing refresh tokens. When an access token expires, Koncert uses the refresh token to validate and generate a new access token, ensuring uninterrupted access to the Salesloft API.
For more details and documentation on the Salesloft API: https://developers.salesloft.com/docs/api/
How does the Integration Work?
Koncert utilizes a real-time access model to ensure data from Salesloft is always up-to-date. This model is employed to load the call tasks and log calls, allowing the system to retrieve and interact with Salesloft data in real-time, ensuring seamless synchronization.
The diagram below illustrates how Koncert leverages this real-time model to load tasks and log calls.
The frontend client makes a request to Salesloft using its API to load the list of tasks. As the client performs calls on each prospect, the client submits a request to log these calls in Salesloft based on the workflow defined in Koncert.
Calls logged back to Salesloft from Koncert use the same sentiments and dispositions as calls logged within Salesloft. If needed, these sentiments can be edited within the Third Party Integrations tab of the Koncert, or within Salesloft itself.
Data Permissions, Objects & Retention
Permissions Model
Koncert uses the standard Salesloft data models and inherits access roles from Salesloft. Custom fields will be retrieved based on permissions defined in Salesloft. Koncert users will only be able to see fields that they are able to see on Salesloft itself.
List of Salesloft Objects
Koncert interacts with the following objects in Salesloft.
-
Accounts
-
Activities
- Actions
-
Admin
-
Cadences
-
Calls
-
Notes
-
People
-
Tasks
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 Salesloft . 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 Salesloft. If the API limit is exceeded, the Koncert system alerts the user with a 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/25237125806615-Getting-Started-with-Salesloft
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.