Bluerock

With Bluerock's seamless integration, agents can take advantage of Forth while keeping a consistent, productive workflow in their current environment.

Integration Details

• Click 2 Call
• Incoming Call Pop-Up
• Ability to post into campaigns using WebHooks
• Call Dispositions
• Call / Voicemail Recordings
• Pull contacts based on Workflow Status

Integrating Bluerock with Forth

Before you begin the setup process your CRM account will need to have signed up for a phone system integration. If you have not and are interested, please contact sales@setforth.com or call (630) 394-6260.

Once you have signed up for the phone system add-on, you will then have access to the Bluerock Settings Page. This page can be accessed by clicking on the Admin tab, clicking on Settings from the Navigation Bar, and then selecting "Bluerock Phone". 

Bluerock Settings

General Settings

Go to the settings page and click Create One to create the Bluerock Connect Token (if you don't already have a token).

After creating the connect token, provide the token and the Web Connector Endpoint that is displayed to Bluerock. These two (2) items are what Bluerock uses to access your account for some of the functionality the integration offers.

**IMPORTANT - Select the Search Company-wide Only checkbox! This will limit the search to only contacts available to user agents, instead of searching an entire account.

* The Web Connector Endpoint will display with the domain you are logged in with; if you are logging in through a domain you do not usually use or plan on having a custom login domain created, you will need to make sure and adjust the Endpoint with Bluerock. Bluerock needs the Endpoint to be for the same domain your users will be logging into the CRM from. To ensure you have the proper Endpoint, you can log in to the CRM via the domain your users will be using, go to the Bluerock settings page, and copy the Endpoint. If this method is followed, the Endpoint should adjust to the domain you are logged in from.

Bluerock API

Now that you have created the Connect Token and Web Connector Endpoint, copy the information and provide it to support@1bluerock.com and request that they provide the API ID and API Hash. Usually, the API ID is a 2 or 3-digit number and the Hash is a 32-digit text string. Once Bluerock Support responds to you with the information, you can simply cut and paste it into the corresponding input fields on the Bluerock settings page in Forth.


Now enter the Bluerock URL. This should be the same for all accounts, but you should confirm with Bluerock the correct URL to use. The standard URL options have been provided below; simply enter either choice into the input field as displayed.

https://web102.1bluerock.com/communicator

OR https://web103.1bluerock.com/communicator

User Mapping

Now map the Bluerock usernames to the users in your account. Make sure you map the correct Bluerock username with the correct CRM username. Also, be sure to enter the Bluerock username exactly as it appears in Bluerock. Any discrepancies (differences in case, spacing, or spelling) will cause some functionality to not work properly. If you are having an issue with an individual user, the first thing to check is that the Bluerock username has been entered correctly here.

* Only users from the company the admin user is logged in from will be displayed. If you are trying to activate or edit Bluerock settings for affiliate company users you will need to log in as an admin from that affiliate that has access to the settings page. It may be necessary to temporarily change the user role of an affiliate user and log in as them in order to make edits for the Bluerock settings. Also, you will need to configure the "General Settings" section on the Bluerock setting page (Active / Running, Bluerock URL, API ID, and API Hash values) the same as the parent company. 

WebHooks

Additionally, a WebHook can be set up to post leads to a specific campaign. Bluerock has the functionality to pull leads in based on their workflow status and a WebHook may not be necessary. Most likely you would want to set up a WebHook in a situation where you have leads importing through a data source that you wish to have immediately added to the top of a campaign in Bluerock. Bluerock can provide posting instructions to set up the Webhook. Please visit our article on setting up WebHooks here.

IMPORTANT: If the data passed from Bluerock in the campaign field does not match a campaign that exists in the CRM, it will create a campaign with the name passed in the campaign field.

Call Logs Post to Main Applicant Only

This feature for clients using Bluerock phone systems and the Forth CRM, allows for incoming call logs to be uniformly assigned to the primary applicant's Contact record when a phone number is shared between a primary applicant and co-applicant. It modifies existing system logic to ensure that when a shared phone number provided by Bluerock is identified for both a primary applicant and a co-applicant, the call log is systematically posted to the primary applicant's Contact ID. For two primary applicants sharing a phone number and/or for two co-applicants sharing a phone number, pre-existing logic will be applied.

Search for Contacts Lookup

We now have a dedicated API that Bluerock hits that lets you search contacts by status. One of the parameters they post is "status=New Lead". The system then searches for contacts in that status for the account and sends it back to Bluerock. You can now pass in a List ID instead of a status name. You may now use "status=New Lead" or "status=List:102319". This allows the use of contact list logic/filters to retrieve the contact set. This is valuable if you want a more refined set of contacts than just status alone. The configuration is on the Bluerock end in their user interface, so a client could edit the value in Bluerock and change from status=“XXXXXX” to status=List:12345.

Article Version History: