Routing – Champify | Documentation

This how we’ll ensure the right data gets to the right person, and they know about it! Below we review options for routing, assignment, alerting, and how this approach varies depending on your current tech and process for routing.

LeanData

Champify works seamlessly with LeanData - and you can likely use much of your existing routing logic to pick up Champify leads.

Based on the “flowchart” you put together during scoping, and your current LeanData configuration, we can determine what specific tweaks or additions need to be made to incorporate Champify leads.

Fields you can use to single out Champify records for routing:

On net new lead and/or contact records created

Created by Champify = True

If you add a picklist value for Champify for Lead Source - Champify will set lead source = “Champify” on any net new leads created

On any champify lead and/or contact record, even if it existed before/without Champify

Is a Champify = True. This is set on all former-customer new-job records flagged by Champify, regardless of whether they already existed in your system.

Merging & Duplicate settings

Similar to the fuzzy Salesforce “standard matching”, LeanData’s fuzzy matching may consider person @ company A and person @ company B duplicates. This can interfere with Champify as it can mesh old and new records and result in messy data.

You will either need to either:

Change the LeanData fuzzy matching to email or name + company name match, or

Add a node that bypasses the LeanData duplicate matching for leads created by Champify

If you are using LeanData and the matching criteria is not exact email or similar - please inform your Champify contact so we can collaborate on the best solution.

Do we need to change our lead conversion logic?

You can opt to use or not use Champify’s pre-built lead conversion trigger

If you choose to not use Champify’s lead conversion trigger, you can add the Champify custom fields to the LeanData conversion to ensure the Champify values are passed correctly from lead → contact upon conversion

What about alerting?

You can continue to use LeanData ad hoc Slack alerts in conjunction with the Champify weekly email alert

Please do not enable the LeanData Slack alerts until after Champify has been activated. Due to the historical backlog we work through, reps may receive many alerts initially. Best practice is to enable ad hoc Slack alerts 2-3 days after activating Champify.

Champify Native Routing

If you do not already leverage a lead routing or assignment tool like LeanData, there are several options for how to set this up.

The main considerations, and what they will help us determine:

Do you already have logic built to assign inbound leads today?

If Yes: Do we need to make any adjustments to this logic for the Champify use case, or can we leverage 100% of your existing logic?

If No: Champify team will help you configure logic to accomplish the “flows” you defined earlier in our scoping process.

Do you leverage the lead object in Salesforce, or only contact and account objects?

Will help determine if we configure Champify to work with leads, contacts/accounts, or both record types? (more on configuring which record types Champify should create here)

If you do not have a dedicated routing tool, please consult with your Champify representative, or email team@champify.io, to ensure we are buttoned up with this process.