The Lifecycle of a Lead with Advanced Analysis
The following describes the states of a Lead that is sent to an external system for advanced analysis prior to activation..
(Refer to the C1–AdvancedAnalysisLead business object to view the lifecycle diagram.)
Pending state: Leads can be created in either the Pending or Ready for Extract state. By generating them in the Pending state, you can verify the targeted customers before actively marketing the initiative.
Ready for Extract state: At this state, leads are ready to be sent to the external system for analysis. A monitor batch process is defined on this state, to ensure that leads in this state are transitioned only when the batch process runs.
Waiting for Analysis state: When a lead is transitioned to this state, an outbound message containing lead information is sent to the external system.
Error state: The lead is transitioned to this state if the system is unable to send the outbound message. Retry logic on this state will attempt to resend the lead to the external system. Leads in this state can also be Discarded if needed.
Active state: When a lead completes external analysis, the External Validation and External Activation Priority flags on the lead are updated. An inbound web service sends back the lead and transitions the lead into the Active state. An enter algorithm evaluates the External Activation Priority flag. If the lead is marked as being a priority for activation (based on settings in master configuration), the lead stays in the Active state. Otherwise, the lead is Discarded.
When a lead is in the Active state, lead events are created to encourage the customers to participate in the initiative. For example, one event could be that a letter or an email is sent to a customer. The lead events and the sequence in which they occur are defined on the initiative’s lead event type profile. The lead remains in the active state while it is being actively marketed to the customer.
Successful state: The system infers that a lead has succeeded by the creation of other data in the system, at which time the lead transitions to the Successful state. For example:
• If an active lead for a customer is related to a rebate claim conservation program, the lead is determined to be successful when that rebate claim is filed for the customer.
• If an active lead for a customer is related to a contract option, the lead is determined to be successful when the customer’s service agreement is linked to that contract option.
• If an active lead for a customer is related to a campaign, the lead is determined to be successful if a completed order exists for the customer for the campaign.
• If an active lead is assigned to a third party representative (to perform one or more tasks), the lead is determined to be successful if the Notify Third Party lead event is completed.
An enter algorithm on this state sends an outbound message, to notify the external system about lead success.
Discarded state: Leads that are evaluated as non-priority for activation are transitioned to this state. Unsuccessful leads also transition to this state after a certain amount of time has passed, as defined on the initiative. If the initiative does not specify a time period, unsuccessful leads remain in the Active state until a user manually discards it.
Refer to
Maintaining Leads for more information.
Parent topic