Skip to end of banner
Go to start of banner

How to automatically route calls to assigned Infusionsoft agents

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

Wildix integrates phone calls to Infusionsoft. You can import your Infusionsoft contacts to Wildix PBX and set up automatic routing of calls to contact owners. Consult the Document for details.

Integration with Infusionsoft: https://www.wildix.com/infusionsoft/

Chrome Extension "Wildix integration to Infusionsoft": https://goo.gl/Z5YnMZ

Created: January 2019

Permalink: https://confluence.wildix.com/x/ZQHwAQ

Step 1. Import of Infusionsoft contacts

  • Go to WMS -> Users -> Phonebooks
  • Select a phonebook you want to import contacts to and click Import (available only for admin user)
  • Select Infusionsoft from the list of backend options -> Log in to your account 
  • Click Save and Import


Note: For detailed information about import, please consult Import of Contacts and Users Guide.

After the import is completed, Infusionsoft contacts appear in the phonebook you have selected. If imported contacts have "Owner" (specified in Infusionsoft) and owner's email address is present both in Infusionsoft and local LDAP, then the owner is automatically assigned to the imported contacts in Collaboration. Owners can be changed when editing contacts (Collaboration -> Phonebook -> Edit -> "Contact owner" field)

Important: During the import, a contact owner is looked up via the email address. Make sure the email address is present both in Infusionsoft and local LDAP. 

Step 2. Dialplan configuration

To configure automatic routing of calls, you need to perform a lookup (Lookupphonebook) using the function MYVAR=${LOOKUPPHONEBOOK(valuetolookup, fieldswelookup, fieldwewant)}). The function searches for a specified parameter of a contact and, according to results, routes a call to its owner.

Where:

  • MYVAR - the variable to which the result of performing LOOKUPPHONEBOOK function is saved
  • valuetolookup - the value to be looked up. Can be a channel variable
  • fieldswelookup - the list of fields to search by. Multiple values, separated by commas, are allowed (in this case use single quotes)
  • fieldwewant - the field whose value to return

Lookupphonebook is performed in such a way: SELECT fieldwewant FROM all_shared_phonebooks WHERE (fieldwelookup_1=valuetolookup OR fieldwelookup_2=valuetolookup OR ...)

For example: OWNER -> ${LOOKUPPHONEBOOK(CALLER_NUMBER, 'office, mobile', 'owner_id')} 

Important: the search is performed in shared phonebooks!


Limitation: The function can only be executed via "Set" Dialplan application and cannot be a part of larger expression.

Here you can find the example of Dialplan configuration:

  1. Set -> OWNER -> ${LOOKUPPHONEBOOK(${CALLERID(num)} , 'office,home,mobile', 'owner_id')} - looks up for owner ID
  2. Set -> INFUSIONSOFT -> ${LOOKUPPHONEBOOK(${OWNER}, 'source_id', 'extension')} - looks up for a contact owner according to the found ID (PBX user) in shared phonebooks
  3. Jump to if -> "${INFUSIONSOFT}"!="" -> Procedure with a modified number ${INFUSIONSOFT} - if the previous execution is successful, routes a call to a contact owner
  4. Call group - the application is executed in case no contact owner is found

Note: Refer to Dialplan applications Admin Guide for the detailed information about Dialplan applications.


  • No labels