Freeze rule

configuration/freeze-rule

(TP39081 / 2023.0708)

Subscription products can have freeze rules on a system or company level that limits how often and for how long a subscription can be frozen, and if the customer can freeze the subscription by themselves in the app or the web.

Configuring a freeze rule

The properties of a freeze rule

 

Name of the rule (not visible to the customer)

Description (visible to the customer)

Used to describe the rules to the customer. Visible in the app and on the webb.

Company (if the rule is not on a system level but specific for a company)

Max number of freezes per year (for example 1 for once per calendar year)

If the freeze starts and ends in different year, the freeze counts towards the quota of the year in which the freeze starts.

Minimum length of a freeze (for example minimum 1 month)

Maximum length of a freeze (for example minimum 3 months)

Freeze reasons (that can be selected when freezing subscriptions with this freeze rule)

Can be applied by

Controls if subscriptions with this rule can be frozen by customers and staff, or only by staff

Applying to a subscription product

A freeze rule is applied to a subscription product.

If a subscription product has no freeze rule, the behavior is as before this feature was developed. Staff can freeze all subscriptions.

Behavior in mobility (web and app)

Freeze and Unfreeze Subscription

Behavior in BRP Cloud (staff)

The freeze rules are used in the wizards for freezing and unfreezing subscriptions.

Freeze subscription (next generation wizard)

Unfreeze subscription (next generation wizard)

Limitation:

If the customer changes from one subscription product to another, the freezes for the previous subscription product are disregarded.