[ channelSUITE Support Wiki ]

From the Lead list, individual Lead Detail page, or Lead Preview screen from a bulk import, you may select whether you wish to route a lead manually or automatically. A brief breakdown of each method is explained below.

You may route leads either internally, to another administrative user, or externally to partner locations.

An internal user may receive leads if they have the View Leads permission associated to their System Account.

At a partner location, when a lead is assigned, all contacts who have the Lead Notification role associated to their Systems Account will receive a notification email.

There are 4 auto-routing methods that are pre-built for channelLEADS:

When setting up a Campaign, an Admin can specify a partner location to be associated. Should the Campaign field of a lead match a known Campaign, then the lead will be auto-routed to that specified partner location.

Should there not be a location associated and this type of routing is chosen, then the lead would be routed to the default internal user, who has been designated by the admin.

When setting up a Partner, an Admin can designate what Territory that partner belongs in. These territories can be assigned combinations of Country, State/Province, US County, US Postal Code, or US Area Code. A lead will be sent when the partner territory matches the data of a lead. Partner territories can overlap; when a lead is covered by multiple partners, a tie breaker rule is used to determine which location should get the lead.

This type of routing is based on closest partner location to the lead's address. Distance is calculated relative to the postal codes of the lead and the partner location.

Notes

• Proximity routing will fail if the lead profile is missing a valid postal code.
• Proximity routing is only available in the United States and Canada.
• When proximity routing fails, the lead is assigned to default admin assignee.

This type of routing is based upon closest partner location (Proximity routing) combined with a location tag match (Interest) to the interest field of a lead. For example, if there are two partner locations that are the same distance away from a Copier lead, then the application will route the lead to the one that has Copier in their location tags.

Notes

• For best results, coordinate definition of partner locations with interest field contents on your lead submission form(s).
• Proximity routing will fail if the lead profile is missing a valid postal code.
• Proximity routing is only available in the United States and Canada.
• When proximity routing fails, the lead is assigned to default admin assignee.

• How are tie breakers handled? On occasions where two partner locations are due to receive the same lead given the auto-routing mechanism used (for example, 2 locations are of equal distance from a lead when using proximity routing or two locations with overlapping territories when using territory routing), the location who has gone longest without a lead will get it.

• With a Proximity auto-route, do the zip codes have to match exactly? No, the algorithm uses a radius search with a 250 mile radius being the default. The default radius is install editable.

• Is there any default routing? Say, in the case that I manually enter a lead? Yes, in this specific case it is assigned to the inputting internal user unless you take action to route it elsewhere.