Restore suspended subscribers: Samson
Use these steps to restore suspended subscribers in Samson.
Restore a single suspended subscriber
- Access the Agreement tab.
- Click Page Options on the upper toolbar.
- Select Restore Suspended Subscriber, and enter the following details:
- Enter the date to restore suspension.
- Select a Samson reason code.
- Enter memos and click OK.
- Click OK on the pop-up box.
- Regular SOCs may be present on the account. Many times an error will occur due to the presence of these SOCs.
- If you encounter an error, perform these additional steps:
- Delete the error-causing SOC.
- Attempt to restore the account.
- If the account does not restore, escalate to your Coach to have a Service Desk ticket filed.
- Refresh the account to verify that the account has been restored. If not restored, escalate to your Coach to have a Service Desk ticket filed.
Business Accounts: Select the Restore suspended sub icon on the Activities toolbar to open the Restore Suspended Subscriber widget.
Restore multiple suspended subscribers
- Select Actions on the upper toolbar.
- Click Multi-Subscriber Activities.
- Choose Restore Multi-Suspended Subscriber.
- Select the subscribers you want to restore, and then click OK. To select more than one subscriber, hold down the SHIFT key and click each subscriber.
- Enter a date to end the suspension.
- Select a Samson reason code.
- If 100 or more subscribers are being restored, the request will be moved to the Samson FT Worklist.
- Schedule a Samson Follow-Up in an hour to ensure the subscribers were restored.
- Enter Memos and click OK.
- Refresh the account to verify that the account has been restored. If not restored, escalate to your Coach to have a Service Desk ticket filed.
Restore an involuntary suspended BAN
- Click Actions on the upper toolbar.
- Select BAN Activities > Restore Suspended BAN.
- Select a reason code.
- For customers suspended for non-pay, select the appropriate reason code that generates restore fees related to the reason code:
- FPQ
- IFQ
- LDXM
- NSQ
- Click OK.
- Review the AutoPay option with the customer, if they do not want to be enrolled in AutoPay continue to the next step.
- Select the option for AutoPay that the customer chooses.
- In the pop-up, review the Payment Summary section, and provide the details to customers.
- Choose Pay Now.
- Select the radio button for the amount to be paid.
- Enter payment information. (ERT, Senior Reps and Coaches have the ability to select Pay the minimum and push taxes and fees to the bill.)
- If customer would like to set up AutoPay, click the check box.
- An email is automatically sent to the Primary Account Holder. Enter an additional email address and choose the language, only if customers would like a receipt email to them.
- Review the AutoPay option with the customer, if they do not want to be enrolled in AutoPay continue to the next step.
- If AutoPay was chosen, review the Payment Agreement and click the check box.
- Click Submit.
- Only available if all information is entered correctly.
- If information is entered incorrectly, an error will appear, and the option to push the charges to the bill will be available.
- While the payment is processing, do not close the screen, as this will delete the payment.
- When the confirmation screen appears, only give customers the payment hashtag number.
- Click OK.
- The BAN will automatically refresh.
- The account will be restored.
- Refresh the account to verify that the account has been restored. If not restored, escalate to your Coach to have a Service Desk ticket filed.
Restore Without Payment option
- Don't use the Restore Without Payment option to waive fees for customers, unless their scenario can be found on Ladex/suspend/cancel for non-payment.
- If using Restore Without Payment, you must use the Customer Request – CR restore reason code.
- If you do not use this code, customers will be charged restore fees on their next bill.
- If using this option, customers must still resolve their past due balance. If no payment is collected due to a dispute, use a collection hold with the appropriate reason code.