channelleads_routing
Differences
This shows you the differences between two versions of the page.
|
channelleads_routing [2009/05/29 19:28] jason |
— (current) | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | =====channelLEADS Routing===== | ||
| - | 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. | ||
| - | ====Manual Routing==== | ||
| - | 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**. FIXME //need confirmation// | ||
| - | |||
| - | At a partner location, the lead will be routed to contacts who have the **Lead Notification** role associated to their **Systems Account**. FIXME //need confirmation// | ||
| - | |||
| - | ====Auto Routing==== | ||
| - | There are 4 auto-routing methods that are pre-built for channelLEADS: | ||
| - | - By Campaign | ||
| - | - By Territory | ||
| - | - By Proximity | ||
| - | - By Interest/Proximity | ||
| - | |||
| - | ===Campaign=== | ||
| - | 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. | ||
| - | |||
| - | ===Territory=== | ||
| - | When setting up a **Partner**, an Admin can designate what Territory that partner belongs in. These territories can be assigned by 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. FIXME //get more granular with tie breakers?// | ||
| - | |||
| - | ===Proximity=== | ||
| - | This type of routing is based on closest partner to the lead's address. FIXME //is partner's closeness based on a Territory postal code Geoblock setup or location address lookup?// | ||
| - | |||
| - | ===Interest/Proximity=== | ||
| - | 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. | ||
| - | |||
| - | ====Mini-FAQ==== | ||
| - | * **How are tie breakers handled?** In occasions where two partner locations are in all ways equal (ie, 2 locations are equidistant from the lead when using proximity routing or two locations with overlapping territories when using territory routing), the location who least recently received a lead will get the lead. | ||
| - | |||
| - | * **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. | ||
channelleads_routing.1243625307.txt.gz ยท Last modified: 2009/05/29 19:28 by jason