- Print
- PDF
This article provides step-by step instructions for setting up the LiveVox Dialer integration in ACE.
Prerequisites
1. An established relationship with LiveVox :LiveVox will support all configuration required on the LiveVox side
Before setting up the LiveVox Dialer Integration in ACE, you'll need to have the following details provided by LiveVox or accessible through your LiveVox management interface:
- base URL
- API Token
- Client Name (your name with LiveVox)
- A Service ID to be associated with click to dial functionality (required to be set up even if a customer does not anticipate using click to call from ACE)
- API Security Key (This security key contains the username and password used for API calls and is the username and password associated with a LiveVox admin user login account)
2. A "Dialer - LiveVox" package addon for the InterProse ACE application
- Please reach out to InterProse Support to request the addon
Engagement and Setup with LiveVox
Engage with your LiveVox Representative to setup the following:
- Manual Service in LiveVox for Click to Dial in ACE.
- Agents in LiveVox, each with a username and password associated with the services they can work on accounts.
- Customer Inbound Service in LiveVox.
- Preview (& Other) campaigns Services in LiveVox.
- Open accounts in ACE via a phone number URL in LiveVox for inbound calls.
To load accounts by account number associated with an inbound phone number in LiveVox, please work with your LiveVox support in conjunction with your ACE support or implementation staff.
LiveVox Application Setup
- Agents
- Agents Desktop
- Agent Panel +Extended Panel
- Extended Panel
- Supports Expressions: = true
- Custom Panel
- Add
- Window Title = (any label)
- URL = https://customerid.interprose.com/search.do
- Add -> Name = value, Value = {"field":"phone_dialed"}
- Add -> Name = phone, Value = true
- Add -> Name = source, Value = LIVEVOX
- Config
- Open Full Screen = true
- Open Externally = true
- OK
- Save Agent Desktop
Inbound Account Popping
The Service to be used for inbound account popping needs to be setup (Inbound Service/Customer Inbound)
- Services
- Services
- Service = Customer Inbound
- Settings
- Agent Desktop = the name of the desktop where the Custom Panel Widget was set up = (Basic Desktop in our example)
- Save
Set up LiveVox in ACE
- In ACE, go to Setup - Vendors - Dialer
- Just below and to the right of the "Dialer Vendors" list, select "New"
- Enter the Vendor Information as follows:
- Label = LiveVox API (it is especially important that you use a different label if you already have a Template LiveVox dialer vendor set up in ACE)
- Identifier = LIVEVOX_API
- Export Flag Identifier = LIVEVOX_API
- Dialer Provider = LiveVox
- Active = true (checked)
4. Enter the LiveVox Settings as follows:
- Api Token (as provided by LiveVox)
- Client Name (as provided by LiveVox)
- Service ID (as provided by LiveVox)
- Username (API Security Key user name as provided by LiveVox)**
- Password (API Security Key password as provided by LiveVox)**
- The remainder of the settings should be set up to meet your needs; if you are unsure of how you want these to be setup, please start by setting them up as shown in the screenshot below
- "Auto Update Contacts" needs to be set to true in order to ensure that new account contacts are updated to LiveVox at the time of placement and to ensure that contacts continue to be updated in LiveVox when contact fields are modified in ACE
5. Under "Custom Fields", select "Apply" to save the vendor
Custom Fields
1. Custom Fields are initially configured in LiveVox.
2. In ACE, go to the Custom Fields section and click the "Refresh" button to import the custom fields from LiveVox.
3. For each listed custom contact field that you want to keep updated in LiveVox, click the pencil icon and select the corresponding ACE field.
4. Any custom contact fields displayed as "(empty)" and not mapped to ACE data won't update in LiveVox.
Default Fields Between LiveVox and ACE
Certain contact fields, known as DEFAULT fields, will be automatically updated in LiveVox without the need for custom identification.
Please refer to the table below for the list of DEFAULT contact fields:
LiveVox | ACE |
DETAILS | ACCOUNT |
balance | current balance |
account block | PERMANENT iff doNotCall is set |
original account number | client account number |
address1 | address1 |
address2 | address2 |
city | city |
states | state |
account | customer account number |
primary email consent | elsStatus==OPTED_IN |
PHONE | PHONE |
phone | phoneNumber |
phoneBlock | (see function isPhoneNumberAllowed) |
smsConsent | txtMsgStatus==OPTED_IN |
cellConsent | locationType==Mobile && priorExpressConsent |
PERSON | DEMOGRAPHIC |
first name | first name |
lastname | last name (or company name if first and last are empty) |
dob | dob |
ssn | national id last 4 |
zipcode | zip |
Mapped Custom Fields and DEFAULT contact fields will be updated in LiveVox when changes are saved to an account or demographic if Allow Update Contacts is set to true/checked for the LiveVox API vendor OR when a job with the job task Dialer: LiveVox Update Contacts is ran in ACE.
Changes to custom field configurations made in LiveVox are NOT automatically detected by ACE. Please select Refresh after changes are made in LiveVox to update ACE with modifications.
Dialer Codes
Under "Dialer Codes" data will need to be populated with each dialer code LiveVox returns with phone log results.
- Each dialer code will have a number (Dialer Code) that is used by LiveVox. LiveVox may provide defaults for labeling and understanding each dialer code.
- You will need to update each of the corresponding fields; label, skip, phone location, phone result contact, etc. to correspond with the way you want the phone log results/records recorded in ACE.
Action Path Flagging
Since account contacts are automatically updated in LiveVox through the API, and campaigns can be built using this data directly in LiveVox, there's no requirement to flag accounts or export them to LiveVox via SFTP. However, if such a need arises, setting up flagging action path workflows and SFTP export jobs becomes necessary. For assistance with this setup, please consult with the support team for guidance.
Set up Agent in ACE
Each agent that will be working accounts in the LiveVox Dialer and using Click to Dial from ACE will need an agent login ID, Password and a Dialer Caller ID entered in their User Profile in ACE.
Set up Jobs in ACE
It is recommended that two jobs be set up for LiveVox API dialer integration as follows:
1. LiveVox Update Contacts and LiveVox Update DNC (Do Not Call) job - run nightly to catch any changes that may not have transmitted in real time; API update delay of 5 seconds or less can be expected
In ACE, when a phone number is marked as 'DNC' in the Phone Demographic Record, it will update in LiveVox through the LiveVox DNC job task. However, if an account is marked as 'DNC' in the Debt Information section, this change will not be reflected in LiveVox.
To effectively manage 'DNC' records in ACE for customers using LiveVox API integration, ensure proper handling at both the phone and account levels.
2. LiveVox Import Phone Log and Audio File job - run a minimum of once a day
LiveVox Client Specific Click to dial Service ID
If a customer wants to use client specific service ids in place of the default LiveVox Settings Service ID, that can be accomplished using a client form. The following must be true:
- The Form Config Type = CLIENT
- The Form Identifier = LIVEVOX
- The Form Field = SERVICE_ID
- The form field for the client must be populated
- The service ID used must be set up in LiveVox
LiveVox API Demo
You can watch a video showcasing the ACE & LiveVox connectivity and how contact updates are done via the API by clicking LiveVox API Demo