If you have been using our Flex-Salesforce Integration, you might remember deploying Functions to your Account. The Functions-based click-to-dial implementation can now be moved to a Native Outbound Dialing implementation. This provides the following benefits:
If you are configuring the SFDC plugin for the first time, then you will get the native implementation by default. You will not see the option to perform a migration, and you just need to ensure that the following prerequisites are satisfied.
Enable and configure the Flex Dialpad via the Twilio console.
Navigate to the Salesforce Integration in the Flex Admin:
After completing the migration, we recommend taking the following steps to clean up your environment:
You are using the beta integration if you downloaded and deployed plugin-flex-salesforce-integration
to your Flex Application yourself.
Upgrading from the beta release requires the following steps:
sfdcConfig.js
file - you will need these values when configuring the GA version of your Flex-Salesforce Integration
Navigate to the Flex-Salesforce integration template in the Twilio console and click Create.
Close the window once the functions are created and visible in Runtime>Functions.
To ensure that we only route calls to workers that click on phone numbers in Click-to-Dial scenarios, we need to create a routing rule.
Navigate to your TaskRouter Workspace and select the Workflow you will use for outbound calls. Then, add a filter as shown in the following screenshot:
If you deployed an older version of the Flex-Salesforce integration, you will need the following assets to repeat the setup process:
Asset Type | Asset Source(s) |
---|---|
Flex-Salesforce Integration | plugin-flex-salesforce-integration-0.3.0.js plugin-flex-salesforce-integration-0.3.0.js.map |
Call Center Definition File (Twilio-Hosted Flex) | callCentreDefinition_HostedFlex.xml |
Call Center Definition File (Self-Hosted Flex) | callCentreDefinition_selfHost.xml |
Outbound Caller ID | Phone Number |
Flex-Salesforce Integration Configuration | sfdcConfig.js |
Please note that instead of downloading the above assets, you can also directly point your implementation to the Asset Source paths mentioned.
By default, pointing your implementation to the source paths will sign you up for automatic updates - if you do not wish to subscribe to automatic updates, it's best to download the assets instead.
If any of the following applies to you, you will need to modify the Flex-Salesforce Integration Configuration file (sfdcConfig.js
):
Your sfdcConfig.js
file should look something like this:
1/*in Beta/GA, this will move to CRM configuration screens */2var sfdcConfig = {};34sfdcConfig.globalParams = {5outboundWorkflowSid: "", //leave it empty,if using default Workflow6outboundTaskChannel: "", //leave it empty,if using default Voice Channel7SFDCBaseUrl: "https://someDomain-dev-ed--c.eu16.visual.force.com" // Your SFDC Org8};910sfdcConfig.agentParams = [];1112// default Global Caller Id for outbound calls, when not specific caller Id has been13//defined for an agent in the worker attribute viz. callerId or below agentParams14window.sfdcConfig.defaultAgentParam = {15outboundCallerId: "+447777777777"16}1718// these are caller ids for various agents19//- you can use this setting here if not defining in worker attribute20sfdcConfig.agentParams["user1"] = {21outboundCallerId: "+44777777777"22};2324sfdcConfig.agentParams["user2"] = {25outboundCallerId: "+44777777771"26};27
Populate the relevant information in this file depending on your needs.