To use LoneScale like a pro, we advise you to read:
#1 -> the integration guide for Salesforce (= this article)
1️⃣ Go to your Salesforce settings
2️⃣ Select your companies' LinkedIn url property [not mandatory]
3️⃣ Select the property to avoid enriching email or phone number if already enriched.
4️⃣ Set up the process to check whether the contact and/or lead already exists in Salesforce
💡 Pro tip: Click on pre-fill Default Settings or Advanced Settings to automatically map fields following best practice recommendations.
5️⃣ Map your Salesforce fields with LoneScale fields
👉 Enrich your Salesforce contacts or leads with the data of LoneScale
Then you just have to choose the Salesforce field you want to update, the action to do ("Replace" OR "Completed only if it's empty"), and the LoneScale field with which one to do this action
You can add as many actions as you want to click on the "+" button
Here you can see an example:
💡Pro tips
Use the “Pre-fill Default Settings” button to automatically map the recommended basic common settings for Salesforce.
6️⃣ Salesforce Setup
Objective:
Enable reps to source new contacts directly from the Account object in Salesforce
Enable enrichment of emails and phone numbers within SFDC
You've 3 Options to implement:
Option 1 [easier to implement]: Contacts are sourced automatically based on predefined account criteria
Option 2: Reps manually select the persona/scenario to apply per account
Option 3: A hybrid approach cumulating 1 and 2 (reps can override default rules with manual selection)
Option 1: Manual Persona Trigger by Rep
1. Make visible the button a custom property on the Account object: LS – Get More Prospect
2. When a rep hit this button:
When the property ‘LS – Get More Prospect’ is set to ‘Get’, the Salesforce workflow ‘LoneScale Contact Sourcing’ is triggered. It pushes the account to LoneScale and updates the field to ‘Pushed’.
3. Customize the SFDC workflow to determines which LoneScale settings to use:
Build branching logic in the Salesforce workflow based on the account routing.
Each lonescale_assignment element should align with one specific LoneScale contact sourcing workflow.
💡 You can assign an account to a specific LoneScale workflow based on criteria like company vertical, country, industry tier, employee count, and more.
⚠️ Always use a default scenario
🚨 Do not modify the "lonescale_action"
4. Copy id from lonescale platform
5. Into Salesforce Element "lonescale_assignment" and repeat for each scenario
6. Ensure sourced contacts are displayed:
On the related Account record
In a dedicated list view for rep visibility
Option 2: Manual Persona Trigger by Rep
Proposed Flow
• We add a new property on the Account object: “Get More Prospects Personas”.
• Reps can manually select a persona-based scenario for that account (default value: blank). Value: Persona 1, 2, 3, etc
• Once updated, this property triggers an SFDC workflow that updates the “LS – Get More Prospect” property to “Get”.
• That change triggers the LoneScale orchestration, which links the selected persona to the corresponding LoneScale workflow ID, and sends the company to LoneScale.
Action Items
1. Create & display the property “Get More Prospects Personas” on the Account object for rep selection (picklist or button)
2. Create the SFDC button to select persons and that sets the property “LS – Get More Prospect” = “Get”.
3. Build a branch in the “ls” workflow in SFDC to match each selected persona with the corresponding LoneScale workflow ID.
4. Display results: make sure contacts are visible both on the Account level and in a dedicated list view for reps.
6️⃣ Enjoy and exploit your results directly in Salesforce 🎉
Still have questions?
☀️ If you haven't found the answer you were looking for, please ask our lovely team on the LoneScale chat ❤️