Exchange categories give your customers an upgrade and downgrade path for plan and bundle products. The groupings within an exchange category cause the creation of a carousel container in which customers can view and exchange the products within each grouping. When there are differences between a customer's current product and the catalog version of the product, the classification of the differences can affect the experience the customer will have when viewing the catalog and when exchanging products.
Differences in product settings fall into two classifications. These classifications are in order of importance. The two classifications are:
The following plan or bundle settings different from other products in the exchange category are deemed "significant."
The following plan or bundle settings different from other products in the exchange category are deemed "insignificant" unless there are also differences in the settings from the significant group.
In the examples below, the category displays as a carousel, and the plan in bold is the customer's current plan, which they will see as pre-selected.
The first several examples assume that you start with a single exchange category containing 3 messaging plans:
Text 100 | Text 200 | Text 300 |
For this example, John's current plan is the Text 100 plan. The only differences between the plans that John can see in the carousel are the plan names,
Text 100 | Text 200 | Text 300 |
John wants to exchange for the Text 200 plan.
For this example, John's current plan is the Text 200 plan.
Text 100 | Text 200 | Text 300 |
You have decided that "Text" doesn't really reflect the capability of these plans and you want to change the names.
Name is in the compatible and insignificant classification. John now sees a carousel that looks like this:
Messaging 100 | Messaging 200 | Messaging 300 |
Because the differences between John's current plan and the catalog's current plan are all compatible and insignificant:
When the difference between a customer's current plan and the catalog version of the plan is compatible and significant, the carousel experience differs.
For this example, we use our original configuration as the baseline, and John's current plan is the Text 200 plan.
Text 100 | Text 200 | Text 300 |
You're taking the changes to your catalog from example 2 further. Not only are you changing the name of your plans, you're changing the description to better explain what your customers get with the plan. Description is in the compatible and significant classification. John's carousel view is now:
Messaging 100 | Text 200 | Messaging 200 | Messaging 300 |
The difference between John's current version of the plan and the catalog's version of the plan is compatible and significant. It's like you deleted the Text 200 plan and replaced it with the Messaging 200 plan. Because John's plan is "grandfathered," that is, he gets to keep his version of it until it is canceled, he sees both his version and the current catalog version in the carousel. When John views the carousel, he sees a "Grandfathered Plan" message.
John can still exchange for any other plan. However, if he does, his current plan becomes no longer available to him because it is no longer offered in the catalog:
Messaging 100 | Messaging 200 | Messaging 300 |
In the following examples, there are 3 exchange categories. The baseline one as illustrated above, and then one for voice that contains
and one for data that contains
Mary has the Voice 100, Text 200, and Data 30 plans. Mary's carousel view:
Voice 100 | Voice 200 | Voice 300 |
Text 100 | Text 200 | Text 300 |
Data 10 | Data 20 | Data 30 |
Like in example 3 above, you make changes to the messaging plans. You also want to emphasize the high-speed capability of your network, so you change the names of the data plans.
Mary decides that she needs more voice minutes and fewer messages, so she goes into the carousel to exchange plans. She now gets a message that one of her plans has changed, and she sees this:
Voice 100 | Voice 200 | Voice 300 | |
Messaging 100 | Text 200 | Messaging 200 | Messaging 300 |
High Speed Data 10 | High Speed Data 20 | High Speed Data 30 |
Similar to example 3, because her current Text 200 plan is grandfathered as long as she wants to keep it, it also appears in the carousel. She selects a new voice plan. The carousel will now look like this:
Voice 100 | Voice 200 | Voice 300 | |
Messaging 100 | Text 200 | Messaging 200 | Messaging 300 |
High Speed Data 10 | High Speed Data 20 | High Speed Data 30 |
Mary then selects the smaller messaging plan. When she completes the exchange process, the carousel will look like this:
Voice 100 | Voice 200 | Voice 300 |
Messaging 100 | Messaging 200 | Messaging 300 |
High Speed Data 10 | High Speed Data 20 | High Speed Data 30 |
Note two things:
This illustrates a fundamental principle: Once you change a product, the product in its original version is no longer available to be received by a customer. It is as if you created a new, nearly identical product and deleted the old one. And the only way a customer can still see that old product is if they still have it as a current product. (And if it is a recurring product, they get to "grandfather" the "old" version until they specifically cancel the renewal.)