Reporting > Text Processing > Suggested Actions

Use the Suggested Actions screen to enable Action Intelligence powered by Medallia AI suggested actions processing, and to configure which fields and units are available for processing.

After processing, Action Intelligence populates the Actionability flag (a_actionability_flag) with a value of either Yes or No to indicate whether feedback in a response is actionable. For responses that are actionable, Action Intelligence also populates the Actionability score (a_actionability) with a value from 0-100, with greater values indicating higher-impact actions. For more information, see Suggested actions.

Enabled

Select to enable suggested actions processing.

Comment fields

Select the comment fields to be processed by Action Intelligence.

Units

Select the units and unit groups to be processed by Action Intelligence.

Bootstrap start date

Important: Aggregated Actions is deprecated, and should not be configured. Accordingly, the Bootstrap start date property is not needed.

The earliest date to consider for aggregated actions processing, in the format YYYY-MM-DD. Enter a date and then click Save to begin processing. Select a date two years prior to the current date. After processing has been completed once, incoming records are processed automatically.

Suggested Action threshold

Phrases with actionability score higher than the threshold are tagged as suggestions. After changing this value, bootstrap processing must be restarted. For more information, see Actionability score.

Condition

Enter a conditional expression to limit the records processed for suggested actions. For example, you might want to limit processing to specific feedback programs. For more information, see Conditional expressions.

Status

Important: Aggregated Actions is deprecated, and should not be configured. Accordingly, the Status property is not needed.

If aggregated actions processing has been completed at least once, this property shows the current status.

Status history

Important: Aggregated Actions is deprecated, and should not be configured. Accordingly, the Status history property is not needed.

A history of recent changes in aggregated actions processing.