Contents

Differentiate when to use Rules vs. Policies

Rules implement if/then/else logic at campaign level.
Conditions evaluate statistics, system events, or the current date and time.
Rule actions can dynamically modify running campaigns, send messages, change filters, and so on.
Rules apply to campaigns as a whole. Rules do not affect the processing of individual contact records.
Rules are grouped into Rule Sets for use with many campaigns.

Policies implement if/then/else logic at the contact level, before, during, and after the call to control dialing and call routing.
Policies are powerful. Business logic in a policy can decide whether to place a call. It can analyze agent availability to begin precise dialing. It can set attributes for recording and post-call processing, or send notifications. Policies can modify dialing modes; make decisions based on contact data, update contact list data, and more.
Policies are grouped into Policy Sets for use with many campaigns.

Do I need a Rule or a Policy?

When creating conditional actions, the first decision is whether to assign that object as a rule or as a policy. Ask yourself these questions:

Should this change apply to all records (Rule) or only the current record (Policy)?
Does the condition evaluate a contact record field? (Policy)
Does the action assign a value to a contact record field? (Policy)
Will the action activate another campaign? (Rule)
Should the action also apply to subsequent campaigns? (Rule)

Always test rules and policies before activating them on a production Dialer system. If after going live, a Rule Set or Policy Set does not behave as intended; it can be adjusted or deactivated with changes taking effect immediately. Changes to rules or policies take effect immediately after being applied. A restart is not necessary.