The information contained in this document is confidential, privileged, and only for the use of internal Birdeye users. This document may not be used, published or redistributed.

This integration is supported for both SMB & Enterprise businesses.

Integrating Birdeye with Rent Manager
User Manual - SUPPORT ARTICLE

Rent Manager is a property management software which caters to the needs of both commercial and residential real estate companies. The deeply integrated software solution offers features including billing and invoicing, expense management, contact management, budget management, financial reporting, etc.

Birdeye can seamlessly integrate with your Rent Manager account and send out review solicitations to your customers automatically. Integrating Rent Manager with Birdeye will automate the process of sending out review requests to your customers on a daily basis.

Table of Contents

​

Birdeye allows you to fetch data from your CRM using some predefined triggers. You can choose any combination from the list of available triggers and inform the support team about your selection. Here are the supported triggers for Rent Manager:

​

​

Enterprise ID

Business IDs of all locations

Login to your Birdeye account, go to Left Navigation Rail and click on ‘Settings’. Once the new page appears, click on ‘Profile’ and select ‘Business Profiles.’

To view Location ID, hover over the ‘Status’ of location.

​

Before you can integrate Rent Manager with Birdeye, you will need to set up the following configurations on the integrations support dashboard:

To set up native integration, we have an integration support dashboard, where we need to set up the integration and then follow these steps to complete the configuration.

https://integrations.Birdeye.com/sign-in/

Select the Trigger Name (Check Box) as per the client’s requirement and click ‘Next.’

Note: To fetch information for all the triggers available using curl commands, use this command. To replace triggers, use this curl command.

Here; you can manage group-level properties, which will be applied to all locations under a CRM.

Customer Fetch Delay: It is used if businesses want to send review requests with a delay (number of days). You can set a delay or leave it blank and click ‘Next.’

Note: This step will create a group for our integration. Alternatively, you can do it via curl commands.

For SMB accounts, you can access the curl command.

For Enterprise accounts, you can access the curl command.

For Single Location/Multi-Location Accounts, select the drop-down and click on ‘Add.’

(In the case of Single Location accounts, it will give you only one option).

A drawer will appear on the right-hand side.

The Status, Frequency and Next RunTime will be set by default. You can make changes if required.

NOTE: For Multi-location, pass the Location Name after the AccountID provided by the client, such as 104323:Espire. The valid format is Account id: Location Name. Remember to provide the colon(:) as a separator. This format is supported when

Override Group Properties: With this, you can override the Customer Fetch Delay property added at the group level, specific to each location.

Click on ‘Next’ and click on ‘Save.’

Note: For SMB and Enterprise, you can use ‘manage the locations’ using this curl command.

​

Before you can integrate Rent Manager with Birdeye, you will need to set up the following configurations:

A business integration group is a configuration that supports the business hierarchy of individual businesses on the Birdeye platform. The properties that are common for all business integrations are entered at the group level. Setting up a business integration group allows you to associate multiple business locations with the Enterprise account. Below is the list of curl commands that you will need to run to set this up.

Copy this Curl Command

curl -X PUT

https://common-services.Birdeye.com/integration/add/businessintegrationgroup -H 'Cache-Control: no-cache' -H 'Content-Type: application/json' -d '{"parentBusinessNumber" :150088776180458,"integrationSourceId" : 15,"integrationGroupTriggers":[{"triggerId":15,"triggerTypeId":1}],"integrationGroupProperties" :[{"propertyKey" : "companyId","propertyValue": "Birdeye"},{"triggerId":15,"propertyKey" : "customer.fetch.delay","propertyValue": 10},{"triggerId":19,"propertyKey" : "customer.fetch.delay","propertyValue": 12},{"triggerId":20,"propertyKey" : "customer.fetch.delay","propertyValue": 5} ]}'

NOTE: We will get the group ID once we run the first curl (Integration Group) and make a note of group ID as that will be required while we will be doing the integration mapping.

Copy this Curl Command

Sample response: A sample response like this (see below) will appear after you run the curl command. The response will have the trigger name, description and the ID. This trigger ID will be utilized while creating the integration group. An integration can have one or more triggers. To use more than one trigger, enter comma separated values while creating the integration group.

Copy this Curl Command

Sample Response

Copy this Curl Command

This configuration is developed to create the actual business integration mapping. Each business integration mapping corresponds to an individual business location.

Copy this Curl Command

Copy this Curl Command

IMPORTANT:

The Location ID can be found for a business using the Inspect Element tool on the browser. Go to the login page, and right-click on the location. From the drop-down menu, click on the ‘Inspect’ button. In this case, the location ID for ‘Palo Alto’ will be 3.

NOTE: The login URL for the Rent Manager business will be - https://xyz.api.rentmanager.com/Help/Login, where xyz is the company ID.

https://Birdeye.api.rentmanager.com/Help/Login

In case, the location ID, is not available with the client, you can hit the curl command to fetch the location ID.

Copy this Curl Command

To execute this curl login to the remote desktop -

IP - 10.51.13.199

User - Administrator

Password - Birdeye@123

​

The company ID for the Rent Manager can be found in the login URL provided to you by Rent Manager.

Example: In the URL on the login screen below 'Birdeye.api.rentmanager.com', the company ID would be 'Birdeye'.

While you are on the integration setup call, you may ask for a specific time delay in sending review requests for any or all of the three different cases - move in, move out and service request completion. You may also specify the desired review request/survey email template (configured in your Birdeye account) that will be used to send review/survey requests once the integration is complete. After the Birdeye support team confirms the integration, you need to perform the steps mentioned below:

Log into your Rent Manager account and in the 'Admin' panel, click on 'Available Integrations'.

In the 'Search' box, type 'Birdeye'. When the 'Birdeye' integration box opens, click 'Activate’. This opens a new pop-up window.

In the pop-up window, select the locations you want to establish the integration for, and click ‘Activate'.

NOTE: By default, ‘Available Integrations’ is visible only for your ‘Default location’.

When the next pop-up appears, click 'Ok'.

Now, Birdeye integration has been activated, and the 'Activate' button will turn grey.

Now you can view the information in the 'My Integrations' section with four new options.

Once the Client has activated our Birdeye Integration from the Rent Manager, an email will be sent which will confirm that the activation is successful. And now, you can add the details to Integration Dashboard and complete the integration.

​

Campaign tags are used to set up campaigns within the Birdeye dashboard.These tags are either provided by the client or can be fetched from Kibana for already checked-in contacts.

RentManager Campaign tags are:

tenant_color_status,billing_name_1,billing_name_2,move_in_date,lease_sign_date,rentmanager_tenent_status,service_request_issue_category.

​

Restriction reason is used to identify the contacts which have been opted-out(restricted) from sending a review request. This reason can be fetched from Kibana for contacts that are checked-in already.

Possible restriction reasons are:

Troubleshooting Steps