When you create a session in Contact Optimization, you can select a template table. If you select a template table for your session, the PCT and OCT contain the following fields:
The repetition of the field name can cause confusion when Contact Optimization retrieves information from the
ContactHistory table.
Create a single physical database table that contains all possible customized fields that you might want to use in an Contact Optimization session. This practice is preferable to creating separate physical tables, each with its particular pairing of fields, for each session. For example, instead of creating two optimization template tables, one with fields A, C, and E, and another with fields B and D, it is better to create one database table with fields A, B, C, D, and E.
By default, the PCT template contains the ScorePerOffer field that you can use when assigning scores in an optimization session. However,
Contact Optimization can use any numeric field in the template table for scores in an optimization session. The
ScorePerOffer field has a float data type. If you must use another data type for your scores, you need to either create a column in your template table or edit the existing score column. You might also have several types of scores that you are comparing to determine which is most optimal for a particular
Contact Optimization session. By creating many possible score fields in your template table, you can switch between score types when you configure your optimization sessions without rerunning each of the participating campaigns and flowcharts.