Rate plan change: Atlas
Use these steps to change rate plans in Atlas. If you encounter any system errors that can't be resolved, use Samson to complete the requested changes.
Before changing plans
General
- Common reasons Atlas may not change a plan:
- Restricted account type
- Suspended account or line
- A pending (future dated) migration from Legacy/Classic to a Value Plan.
- Pooled Plans: You can change the pooled plan and change features at both the BAN and Product level and for each subscriber.
- Individual plans: You can change one or many individual lines on an account and change features on any of those lines in a single transaction.
- Retired plans are not available in Atlas.
- The change feature flow for Atlas has special indicators to help you identify Future dated changes and Retired plans.
- If you exit or cancel the plan change flow or cart without saving, the change will cancel and must be started again when you return.
- If performing a rate plan change and add-a-line one transaction, perform the rate plan change first.
Dropping features / information during plan change
- When moving customers between plan groups (such Magenta to Magenta MAX, TE to TI, ONE plan to Magenta), some features (such as Netflix or Stateside International) may drop as plan/SOC eligibility varies between plans.
- These dropped SOCs will need to be re-added during the plan change process to prevent customers from being charged for features that are discounted or On Us.
- For Netflix, if feature is not re-added during the plan change, those customers will need to take extra action and re-redeem Netflix.
- Some plan changes might cause customers to lose information, such as voicemail. Ensure customers back up personal information or save voicemails before completing a plan change.
Samson callouts
- Use Samson to complete a rate plan change for accounts with 20+ lines on a non-pooled plan and 12+ lines for a pooled plan. Atlas won't allow navigation to the Add/Remove Features flow.
- While future-dated plan changes can only be removed in Samson, you can overwrite any future-dated plan changes with this flow.
Postpaid rate plan change
1. Access rate plan change flow in Atlas | Steps
|
|---|---|
2. Select a rate plan | Steps On the Change rate plan screen:
|
3. Select talk primary line (TPL) | Steps On the Select talk primary lines (TPL) screen, review the selected TPLs or choose new ones based on the customer's preference. Notes:
|
4. Handle Conflict Resolution (if it appears) | Steps Read each conflict and modify the conflicting item(s) appropriately by using the back button to go to a previous step of the Rate plan change flow. Note: This appears only:
|
5. Change features | Steps Select Continue to advance to the Change features flow where you can Add, remove or change features. |
6. Review rate plan cart | Steps On the Rate plan cart screen, review the changes for accuracy and select Checkout to save your changes. Notes:
|
7. Checkout & Confirmation | Steps After clicking Checkout on the "Cart review" screen, the "Transaction Confirmation" screen displays. Notes:
|
Error codes
Error: SOC XXXXXX can be removed only on future bill cycle(s) start date but can be upgraded on any date in the current cycle or future bill cycle start dates.
Description: Atlas won’t allow users to delete a data feature mid-cycle or backdate w/out replacing it in the same transaction.
Solution: Replace the data feature in the same transaction.
- While changing a rate plan and you’re presented with a Conflict Summary screen, it’s likely legacy data features were removed and need to be replaced.
- Click Continue to navigate to the Change Features screen.
- On the Change Features screen, ensure that each MSISDN has a data feature selected.
- The effective date will automatically update to match the effective date of your new rate plan.
- Click Go to Cart and complete checkout.
Error: SOC Code: XXXXXXX Error: XXXXXXX is a Product Level SOC. You can't select it.
Description: You're trying to add a BAN level feature (such as Family Allowances) at the line/MSISDN level.
Solution: When adding BAN level features in the Rate Plan or Features flow, make sure you've expanded the **Account** blade before selecting the feature.