Siebel Life Sciences Guide > Siebel Pharma Developer's Reference > Configuring Personalized Content Delivery >

Scenario for Identifying Recommended Messaging Plans

This scenario gives one example of identifying recommended messaging plans. You might use this feature differently, depending on your business model.

A sales representative (Sales Rep A) has an Objectives set up called Q1 Objective and has Dr. Adler as a target for this objective.

The Target Record of Dr. Adler has two custom extension fields to hold SegCode1 and SegCode2 for two products, A1 and B2, that Sales Rep A deals with.

The Sales Operation Manager has also five messaging plans, namely MP1, MP2, MP3, MP4, and MP5, associated with this Objective and each messaging plan has a Target Segment code specified as A1, B1, A2, B2, and A1.

Sales Rep A creates a call on Dr. Adler and selects Q1 Objective as Objective for the call. The OptimizeDetailingPlan finds matching messaging plans associated with Objective Q1 Objective that have Target Segment code as A1 and B2. This scenario results in MP1,MP4 and MP5 selected as recommended messaging plans.

Next, consider the situation where Sales Rep A creates another call on Dr. Adler and does not select Objective for the call. OptimizeDetailingPlan matches custom extension fields defined on the call business component (BC) to hold segment code values against Target Segment Code fields on the messaging plans to identify recommended messaging plans.

For Contact Calls with Marketing Communications, the LS PCD Service method provides a list of messaging plans to be loaded in the PCD Viewer based on messaging plans associated with Contact Call Offers for which the sales representative has access. For example, if Sales Rep A has access to three Contact Call Offers but is in the Access Group of only one of the messaging plans associated with the Contact Call Offer, then only that messaging plan can be loaded in the PCD Viewer.