Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.

We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.

This video focuses on the integration of Salesforce with Bonterra Impact Management.

Interested in deploying an integration with Salesforce for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.

Watch time: 8 minutes

Video Transcript
[SLIDE]

In this video we are going to explore use cases for integrating Salesforce with Bonterra Impact Management.

[SLIDE]

Sidekick Solutions is a Zapier Certified Expert. We work exclusively with nonprofit and public sector organizations, specializing in integrations and system automation for case management and donor management/CRM software.

Our team of integration experts supports Zapier-enabled integrations and custom developed integrations using the Bonterra Impact Management API, Bonterra Impact Management Connect API, and Bonterra Impact Management Automated Import (SFTP) tools.

[SLIDE]

We’ve released a number of products including the Connect Auto-provision application, Zapier connector, and private API.

This slide includes a list of our automation deployments to date, across a variety of iPaaS platforms, applications, and solutions.

[SLIDE]

We believe integration and automation are essential to user experience and the promise of efficient work through technology.

The goal of case management software is to do less paperwork and serve more people. From our view, automation is the critical ingredient to realizing that full vision.

This is why our team at Sidekick Solutions develops integration products and services for Bonterra Case Management software.

[SLIDE]

The challenge most users face in Bonterra Impact Management is that the product does a great job of building an electronic record, but it is “click heavy”. Because service delivery is a dynamic experience, the only way to reduce time is to reduce clicks and to do so smartly.

This means we focus on:

• automations and workflow rules that run conditionally
• integrations that reflect Bonterra Impact Management’s strengths as a customizable platform
• remove double entry
• expand capability and capacity without requiring more human capital

[SLIDE]

Bonterra Impact Management is a constituent relationship management platform with a primary function of case management.

It is geared toward serving individuals, engaging them, and interacting with them. But, Bonterra Impact Management may not be the only system you use. As a result, we think of it as a hub.

Bonterra Impact Management is a strong end user business application and serves well as the central hub of a tech stack. We find that users enjoy the look and feel and it does a great job of building a case file per participant.

[SLIDE]

Because Bonterra Impact Management is a hub product, we have the opportunity to extend it with spokes.

We think about that process in six steps. You can use this to plan for extension of your technology stack with Bonterra Impact Management.

When exploring new technology to extend Bonterra Impact Management, we encourage you to focus on your mission, strategic plan, and organizational goals, allowing real use-cases to drive the adoption of new tools/apps.

[SLIDE]

When we think about integrations, it’s helpful to think of it as stacking bricks. Once you have one automation in place, you level-up to the next layer, and so on.

This is how you can, over time, build a complete technology stack or ecosystem around your Bonterra Impact Management system.

The journey to full-system automation is never over. As more use cases require automation or other apps are added to your organization’s tech stack, you will need to continue improving and expanding the solutions integrated with Bonterra Impact Management.

[SLIDE]

When exploring an integration between Salesforce and Bonterra Impact Management, the data can flow in either direction. We are going to explore a use case where data syncs from Bonterra Impact Management to Salesforce first.

[SLIDE]

For this use case, the client adopted Bonterra Impact Management to support its staff with its case management activities. All other departments of the organization continue to use Salesforce and Salesforce remains the primary database for funder reporting. Therefore, the client needed to ensure key demographic and service data was available in Salesforce for this reporting.

This solution had three primary flows.

1. Participants. For each new or update to an existing T1 Participant in Apricot, the flow searches for an existing Contact in Salesforce by the T1 Participant record ID. If an existing Contact is not found, a new one is created. If an existing Contact was found, it will be updated.
2. Enrollment (Cases). For each new or update to an existing T2 Enrollment record in Apricot, the flow searches for an existing Case in Salesforce by the T2 Enrollment record ID. If an existing Case is not found, a new one is created. If an existing Case was found, it will be updated.
3. Services. When a new T2 Service is created in Apricot, the integration will create a Service record in Salesforce.

By syncing this key demographic and service delivery data from Bonterra Impact Management to Salesforce, the organization was able to continue generating funder reports across all domains from a centralized source.

[SLIDE]

For this next use case, we are going to explore flows that sync data from Salesforce back to Bonterra Impact Management.

[SLIDE]

The organization for this use case runs Salesforce (NeighborWorks Compass), alongside Bonterra Impact Management, for its housing counseling and education services.

This solution had two primary flows.

1. Contacts. For each new Contact in Salesforce, the flow searches for an existing T1 Participant in Apricot, creating a new one if an existing T1 is not found. Then, the Contact in Salesforce is updated to append the found/created T1 Participant record to support syncing of service related data.
2. Bookings & Notes. Service delivery in Salesforce is tracked on Bookings & Notes records. Each time a new Bookings & Notes record is created, the flow will use the T1 Participant record ID on the Contact to create a T2 Service record in the Participant’s document folder in Apricot.

This solution allows the organization to centralize all service delivery in the Participant’s document folder in Bonterra Impact Management, creating a complete electronic case file.

[SLIDE]

Another common use case is syncing Vendor/Partners from Salesforce to Bonterra Impact Management. While this solution isn’t as robust as the prior two use cases, it ensures the T1 Vendor/Partner directory in Bonterra Impact Management remains in sync and users are selecting from an up to date directory.

[SLIDE]

These use cases are the tip of the iceberg for integrating Salesforce with Bonterra Impact Management. If you are interested in exploring deployment of this solution for your organization, contact us at sales@sidekicksolutionsllc.com to get started.