Overview
BytePro is a loan origination system (LOS) designed for banks, credit unions, and brokers. It provides a variety of features to help lenders improve loan quality and efficiency.
Experience.com’s integration with BytePro lets enterprise customers send automated surveys to loan customers during and after key moments in the lending/homebuying process. The Experience.com BytePro integration allows you to:
Ingest loan transaction data from BytePro into Experience.com.
Map ingested data to campaigns within the account
Automate campaigns and surveys to loan customers based on role, transaction type, journey moment, or location.
Transactions ingested from BytePro into the XMP are labeled as verified transactions.
...
| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Pre-requisites for Integrating with BytePro
Several prerequisites must be met before Experience.com can access and ingest transaction data from BytePro for a specific organization. While a Primary Point of Contact (POC) is essential for managing the relationship between Experience.com and their organization, it may be beneficial to request the participation of the organization’s BytePro Administrator, who has the permissions and knowledge required to complete the integration configuration with Experience.com ’s XMP.
Before getting started, an Experience.com team member must obtain the following information from the lender (Technical POC):
Site name & server name
BytePro username & password
API Key
Once this information is received, create the integration in the XMP.
Add Integration
To create a new configuration, navigate to the Account Settings page and open the Ingestion Settings. Click BytePro, and then click the blue “New Connection” button.
Using the information gathered earlier in the process, enter the following information. Once the information has been entered, click anywhere within the BytePro Configuration drawer to begin testing the connection automatically.
A connection name
Server name
Username
Password
API Key
Date Filter Field
All fields used in the XMP must begin with “Fields.” For example, if the BytePro field is 1997, enter “Fields.1997”
a point of contact (email address)
Once the information has been verified, a notice message will confirm that the information is verified and the configuration has been created. A few more details are required to finalize the connection before it can be saved.
Use the arrows or type a number into the Number of Look-Back Days field to set the data ingestion period.
| Info |
|---|
Lookback Days (to initiate transactions): this represents the number of days of historical transaction data collected on each data transfer from Calendly to the XMP. By default, this value is set to 3 days, which means the XMP will collect data for the previous three days and the current day for which it is ingesting the data. |
...
| Tip |
|---|
The Go Live Date is the date on which data is made available for a survey for use in real-time. By default, it will display the date of the day the configuration was created. |
Before activating the ingestion configuration, you must configure the Trigger and Dynamic Fields. Defaults are present for each with the recommended selections, however, they can be added or removed as necessary.
Trigger Fields: fields that can be used to create conditions. Fields entered here can be used to trigger a survey for a specific transaction when conditions are met.
Dynamic Fields: fields that can quickly be pulled in to personalize survey questions, campaign emails, and workflows. If, for example, survey questions are asking about an individual’s experience with their specific agent, and you want to include that agent by name, the [AgentName] dynamic field can make it possible to send a personalized message to numerous recipients simultaneously.
...
Finally, confirm that the survey sender//survey recipient link present is the intended workflow. For a participant to receive a survey, they must be linked here as a survey recipient.
Lookback Report
Once the connection is activated, a lookback report can be used to provide a complete detailed picture of data that has been ingested from the connection over a set number of days. A lookback report can be downloaded for a maximum of 90 days and can ensure that data was received from BytePro to the XMP.
...
Activate the Connection
To enable the connection to ingest data for campaigns, be sure the checkbox is checked, then click the blue Save button. The integration can be discontinued at any time by unchecking the box and clicking save.
...
Add the BytePro ingestion source to an active Campaign to automate transactions using the newly configured BytePro connection.