This topic details all the settings for plans. This is the information you will need when you add or edit plans.
Service Design Center uses a change management process to track and approve all changes to any product. All of these changes, including additions, edits, and deletions, must go through the promote-approve-deploy process before they become available.
Any changes you make (change a name, change a price, add or delete a product from a bundle, etc.) to any product do not affect any users that already have the product.
The General tab contains most of the settings you will configure to determine how a plan looks, acts, is priced, and more.
These settings define how information about a product will appear to customers.
| Setting | Description |
|---|---|
| Name | Required. The name serves 2 primary purposes: it's what you see in product lists and it's what customers see as a descriptor when they are making purchase decisions. The name is limited to 115 characters. |
| Short Description | Brief plain-text information about the plan that sometimes appears with the plan name. |
| Marketing Message |
Descriptive rich-text information about the plan that appears on only the pre-purchase detail page above the content you add in the Description field. You can format the content you enter in several different ways using the functions in the toolbar. This field is best for a small amount of marketing information that will help drive purchase decisions, such as offers customers will receive with purchase. Use the Description field for larger amounts of additional product information.
|
| Description |
Detailed and descriptive rich-text information about the plan that appears on plan detail pages. The content you enter here is seen on the product detail page both pre- and post-purchase. You can format the content you enter in several different ways using the functions in the toolbar. This field is best for providing additional details about the product, for adding details to the brief marketing message, for legal boilerplate content, and so on.
|
| Fulfillment Type |
Required. This defines the system process by which customers receive the product or fee. Currently, ItsOn Digital Delivery is the only option that is supported. Selecting any other option may produce unpredictable results.
|
These settings determine who can receive the plan and how a plan's allotment can be allocated.
| Setting | Description |
|---|---|
| This product can be purchased for |
Required. Determines who can receive a plan when it is purchased by a customer. Select
Gifted products cannot have more than one cycle, because when you purchase a plan, you are purchasing only the first cycle, and gifting a plan with more than 1 cycle would require the gift recipient to either pay for subsequent cycles or cancel the plan before it renews. So if you choose
A plan can be gifted only at purchase time. The purchase process of a gift requires a phone number to be input by the purchaser to identify the gift recipient. There are several issues that could occur and that would prevent the completion of a gift purchase, issues that include:
|
| Allocation |
Required. Determines how a plan is allocated to subscribers. Select
The Assignable and Shareable options are viable only when the tenant offers more than one subscriber per account.
|
| Share Method |
When Shareable is selected as the Allocation setting, determines how that sharing occurs. Available only when the Allocation setting is Shareable. Select:
|
| Share Type |
Determines how plan allowance can be shared by subscribers. Available only when the Allocation setting is Shareable.
Limited is considered a "hard allocation," which means that once a subscriber is allocated an amount from the plan, no other subscriber can use that allocated amount of the plan unless there is an explicit reallocation. The total of the subscriber allocations cannot exceed 100%. For Limited, the following is true:
Piñata is like a large glass with each subscriber having a straw. Each subscriber can consume as much of the total plan allocation as they are allocated, each allocation can be any value up to the plan allocation, and the total of all allocations can be more than 100%. The amount each subscriber actually consumes each cycle is defined only by their usage pattern. For example, you have a shared 100MB data plan. An account with 2 subscribers purchases the plan and gives each subscriber 100%. The first day of the first cycle, subscriber A uses 100MB. Subscriber B's allocation for the rest of the cycle becomes 0MB. In the second cycle, subscriber B uses 100MB in the first day. Subscriber A's allocation for the rest of the cycle becomes 0MB. For both Limited and Piñata, the total allocation to subscribers can equal less than 100%, so there could be an unallocated amount in a cycle. See Sharing Examples for information on how sharing and allocation works. The Share Type option is viable only when the tenant offers more than one type of sharing.
|
| Assignment Method |
When Assignable is selected as the Allocation setting, determines how that assignment occurs. Select:
|
There are a number of ways that customers receive plans where sharing, assigning, and gifting settings will not be available to them. In those cases, default plan sharablility and assignability occurs.
Some sharing and assigning is done by the plan purchaser as part of the purchase process. In fact, some settings require sharing, assigning, or gifting selection at purchase time. But when a plan is mandatory to be received, is received via the complimentary or provisioning API, or is received as a benefit, it is not included as a part of such a purchase flow, so sharing and assigning selections that are required within that flow cannot be made.
A specific example of this is if a plan's Allocation setting is Assignable and the Assignment Method setting is Assignable at purchase only. If the plan is received as a benefit, it doesn't go through that customer-facing purchase flow, and so cannot be assigned. Another example is if a plan's This product can be purchased for setting is Gift recipient only. If this plan was being purchased, the only option at purchase time would be to enter a phone number of a subscriber outside the account to receive the plan. But again, if the plan is received as a complimentary plan, the screen to enter a phone number isn't shown, so there's no way to gift the plan.
The general rule is that if a plan is received outside of the customer-facing purchase flow, like when a plan is received automatically, and has a combination of settings that require decisions only in that customer-facing purchase flow, then the plan is assigned to the subscriber designated to receive the plan, and if that subscriber is not known, the plan is assigned to the first subscriber in the account.
These settings define which service policy is used in the product and what limits, if any, on the type of service used.
| Setting | Description |
|---|---|
| Service Policy |
Required. Select the service policy from Service Design Center necessary to provide customers the service you offer in the product. The type of service policy is in parentheses after the service policy names. Make sure you select a
If you are not sure which service policy to choose or you do not see the service policy you want to use, contact your service policy designer.
It's important to select the right type of service policy because service policies allow only one type of service. So if you intend to create a voice plan (with a name and a description that suggest voice service) and you accidentally select a messaging service policy (and it gets through all your testing and review), a customer would buy the plan to make voice calls. But when they try to make a voice call using the plan (and if they have no other voice plans that could be used as a fallback), they will be blocked because the policy upon which the plan they do have is based allows only text messaging. |
|
Data Usage Voice Usage Messaging Usage |
Required. Determines whether there are usage limits on the plan, and if so, what the limits are. Select
Plans can have time limits also, set in Cycle Duration, which means that the plan usage can also be limited by time. For example, a plan might offer 10MB of data for 30 days, and when the 30 days ends, any remaining data is forfeited.
|
| Per Call Limit |
Sets the time limit for voice calls. Available only when a voice service policy is selected in Service Policy. Select from:
This setting is sometimes used to create preferred destination plans. For more information, see Create a Favorites Plan. |
These settings determine how and when a plan is available in the store. See Plan Behavior Settings Examples for some scenarios on how these settings combine to produce desired product behavior.
Several of the behavior settings relate to aspects of the plan cycle, aspects that include:
| Setting | Description | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Recurring |
Required. Defines whether the plan is a multi-cycle subscription, lasts for only one cycle, or lasts for one cycle with the option for customers to renew. If you selected Giftable only in the This product can be purchased for setting, the only option here is No. This is because plans that are gifted can have only one cycle because when you purchase a plan, you are purchasing only the first cycle, and gifting a plan with more than 1 cycle would require the gift recipient to either pay for subsequent cycles or cancel the plan before it renews.
Select:
Any segmentation rules that include this setting, including restrictions and offers, will treat both Yes and Optional as the same. That is, if a rule is defined to match a recurring product, the rule will match if this setting for the product is either Yes or Optional.
|
|||||||||||||||
| Number of Cycles |
Required. This defines the number of cycles a subscriber can receive the plan. The options determine if a plan repeats at the end of its duration. (The duration is defined either as the account cycle, if Aligned to account cycle is Yes, or as the plan's Cycle Duration value.) If so, the customer is grandfathered the plan rate and attributes when it is renewed, even if you have made significant changes to the plan or even deleted it from your catalog. Available only when Recurring is set to Yes or Optional. Select from:
Plans renew when they are set to an unlimited number of cycles or when they are "limited" to more than one cycle, that is, the number in the Limited to option is greater than 1. Renewing means that at the end of a plan cycle's duration:
If you are going to make the plan giftable, then it cannot renew and you must select the Limited to option and enter 1. This is because when you purchase a plan, you are paying only for the first cycle. If gifting a plan with more than 1 cycle was allowed, the recipient would be responsible for either paying for subsequent cycles or canceling the plan before it renews. |
|||||||||||||||
| Aligned to account cycle | Required. This is the alignment, and it defines when renewals occur and are billed. Available only when Number of Cycles is set to Unlimited or set to Limited to and its value is greater than 1. Defines whether the plan is billed when the account cycles or when the plan is purchased. | |||||||||||||||
| Cycle Duration |
Required. This defines how long a plan cycle is. Available only when Aligned to account cycle is set to No. Select from:
|
|||||||||||||||
| Prorated on first cycle |
Required. This is proration, and it defines how much is billed and allotted for the first cycle. Available only when Aligned to account cycle is set to Yes. Best Practice: When you have a plan that has more than one account cycle and aligned to the account cycle, you'll almost always want to set this to Yes. If you set it to No, a customer will be charged full price for the plan even if they buy it on the last day of the account cycle. While that may be OK for plans with a fixed amount of consumption, your business needs may dictate otherwise, especially for unlimited plans For example, if if a plan offers 30MB of data for $30/month and a customer whose account cycle begins on the 1st buys the plan of the 20th, they will get a prorated amount of 10MB for a prorated cost of $10. But if you offer an unlimited amount of data for $30/month and a customer whose account cycle begins on the 1st buys the plan on the 30th, they will get an unlimited amount of data for $1. So for unlimited plans, you may want to consider setting this option to No. Even when a plan is prorated normally, when it is offered in an exchange category in a carousel and a customer receives the plan through the exchange category in the carousel, no proration occurs. The customer receives the full allotment for the remainder of the cycle in which it is received and is charged the full cycle price. |
|||||||||||||||
| Usage Display |
When customers buy plans, they can view how much they have used of that plan (or how much they have left to use) and how long they have used the plan (or how long they have left to use the plan) in the My Plans section of the self-care app. Plans can have a consumable element (it's allocation, in minutes, messages, or megabytes) and a duration element (how much time is available to use the plan). The usage display can show the allocation usage, the time usage, or both. The ItsOn system defines a default display of usage, and what's shown for that default depends on other plan settings. You can also define a custom usage display for the plan, which overrides the default. Select:
Default Usage Display
Summary of Usage Display DefaultsUsage display defaults depend on your usage and duration choices in the Voice/Messaging/Data Usage and Cycle Duration settings:
Bar and Label Direction and PositionThe direction of bar movement and the position of labels in relation to the bar (to the right or left of the bar) depend on tenant settings and/or language (left-to-right or right-to-left) settings. First, whether the bars are count up (for example, Day 7 of 15 or 300 of 500 Mins) or count down (for example, 8 days remaining or 500 MB remaining) depends on a tenant setting. Then, the direction that the bar moves (or fills) depends on a tenant setting. Finally, if there is a label, its location depends on language settings. If the language setting is left-to-right, the label will be to the right of the bar. If the language setting is right-to-left, the label will be to the left of the bar. |
|||||||||||||||
| Duration |
Duration represents the length of the cycle. It is one of the options available for you to configure when you select Custom for the Usage Display setting. The duration display contains two components, a progress bar that shows the relative amount compared to the total amount of duration and a text label that shows the actual amount of the cycle. Select:
|
|||||||||||||||
| Unit |
Units represent the consumable element of a plan allocated to users. It is one of the options available for you to configure when you select Custom for the Usage Display setting. The units display contains two components, a progress bar that shows what part of the whole amount of time has been used and a text label that shows the actual amount of the time used. Select:
|
|||||||||||||||
| Display Detailed Usage Data |
Select Yes to allow users to see detailed per-call, per-message, and per-data-session information on their account page. |
|||||||||||||||
| Terminates when usage allowance runs out |
Available only when Renewal is Does not renew because this setting is used only for one-time plans. Determines if a plan is terminated when its usage allowance runs out. The choices are:
Note: A reason why you might want to choose No here is so that customers can upgrade one-time plans if the usage allowance runs out before its expiration. Once a plan terminates, it can't be upgraded.
This is how a depleted plan would look when you select No:
The choice here can also affect when intercept notifications are triggered. One of the intercept notification rule options is a reason, and the two choices are Plan Capped and Plan Not Present. If a plan terminates, then it would match the Plan Not Present option in the notification. If a plan is not terminated when its allocation runs out (the No option of this setting), the plan would still be considered active until its duration expires. This matches the Plan Capped intercept notification option, and you could design an intercept notification to provide easy upgrade options. |
|||||||||||||||
| Visibility |
Determines whether or not the plan is visible to customers. If this is set to Hide, the plan is not visible for purchase in the store nor is it visible in a customer's account information. It is not shown as part of a bundle when included in a bundle, and usage and intercept notifications are not triggered by hidden plans. For more on how hidden plans work in bundles, see Hidden Products in Bundles. A plan cannot be hidden unless its price is equal to 0 (zero). This is because at checkout, a non-zero priced plan in the cart will result in a total price that is different from the sum of the prices of the visible products, which could cause customer confusion. So this setting is unavailable until a price value greater than 0 (zero) has been entered for the plan.
|
| Setting | Description |
|---|---|
| Retail Price | Defines the default, standard price for the product (plan, fee, or bundle). This is the price customers will see unless overridden by the Sale Price field or other available offer mechanisms. If no value is entered, 0 is used. |
| Sale Price |
Overrides the Retail Price while allowing you to keep a record of the retail price. To return to the Retail Price, delete the contents of this field. A Sale Price can affect whether customers qualify for offers (benefits and discounts), depending on the value of the Apply to sale price setting in the offer.
When a customer is viewing the catalog, both the sale price and the retail price are visible in the product listing. The exact appearance will depend on your branding. The following graphic is an example of what customers might see in a product where the Retail Price is 1.00 and the Sale Price is 0.80:
Some research suggests that consumers believe prices with more syllables are higher than the same prices with fewer syllables, and this is seen in both spoken and printed prices. Both commas and decimal points add to the "syllables," so, for example, $1,199.00 is viewed as more than $1199. ItsOn provides a client-side branding setting that can present catalog prices without the decimal and the digits after the decimal for whole number prices. If this setting were used for the example above, the values seen in the catalog presentation would be $1 and $0.80. This setting does not affect the amounts you enter in the Retail Price Price or the Sale Price fields, nor the amounts shown during checkout, in customer invoices, and in customer service records.
|
| Tax Classification |
This defines what specific taxes should be charged, if at all. Different municipalities and other political units charge varying amounts of and types of taxes and fees on specific types of goods and services. This selection drives the correct type and amount of taxes to be collected based on the customer's location and type of service purchased. Select from:
|