Operating goal
A renewal calendar should distinguish reminders, payment status, requested extension and verified panel result. A pending payment is not evidence that a subscription was extended.
Store the private reference, current expiry, proposed term, payment verification and confirmation date in distinct fields.
Where this fits in the customer workflow
Start with customer intake and a device trial, then confirm term, account route and payment verification. After activation, check the reference source and document the expiry. At renewal, identify the same account and reconcile the credit change. Each stage needs a clear status and private reference.
Package totals and credit use
Compare current credit totals before placing a request: 10 credits cost $139, 25 cost $335, 50 cost $645 and 100 cost $1,190. The duration mapping below determines how many customers the balance can support.
| Customer duration | Credit use | Activations from 10 credits |
|---|---|---|
| 1 month | 0.1 credit | 100 |
| 3 months | 0.3 credit | 33 |
| 6 months | 0.6 credit | 16 |
| 12 months | 1 credit | 10 |
Counts assume the supplied duration mapping and one standard activation per customer.
Panel access and responsibilities
The panel image shows menu areas for M3U, MAGs, active code, resellers, credits and transactions. Visible example menus do not establish the permissions enabled for a new account. Ask support about the exact account route, distributor options and support handoff before promising an operation to a customer.
Record and review
Record the account reference, device, chosen app, term, requested action and verified outcome. Keep customer secrets separate from operational notes, limit record access and review pending operations before allocating another credit package.