Read and act from the subscriber profile
Open a subscriber from the list or global search. The profile combines current account data with related sessions, usage, payments, invoices, tickets, SMS history, and package actions.Verify identity first
Before changing access or money:- Match the subscriber name with at least one stable identifier—account number, username, phone, email, MAC, or address.
- Confirm the service type and package.
- Check the status and expiry.
- Confirm the router/session context when the issue is network-related.
Profile areas
Depending on data and permission, the profile exposes:- identity and contact details;
- account/service status and expiry;
- package and access identifiers;
- current and historical session/usage information;
- payment and invoice history;
- tickets and operator notes;
- sent SMS/messages;
- deferred usage and payment aggregates.
Common actions
Send credentials
Use the dedicated action so the current access details are delivered through the configured channel. Confirm the recipient number/address and never read a password aloud to an unverified caller.Send payment information
This action sends the ISP’s configured payment instructions. Verify the gateway and instructions in settings first, especially after switching providers.Send a message
Write the intended SMS and confirm provider credit/readiness. The profile history should reflect the send result, but provider acceptance is not always final handset delivery.Send a voucher
Choose a compatible voucher/package and verify the subscriber phone. Voucher issuance can consume inventory and create an access entitlement; do not repeat the action until checking whether the first voucher was created.Generate an invoice
Generate only after verifying the amount/service context and avoiding an existing invoice for the same obligation. The new invoice appears in the subscriber and invoice workspaces.Pause, resume, block, or unblock
Read the current state and reason before changing it. A network disconnect may still be needed to terminate an already active RADIUS session after an account-state change.Change expiry or compensate
Use expiry change for an explicit target date. Use compensation to add controlled time for an outage/service issue and retain the operational reason. Bulk outage compensation can also be automated by operator-alert settings when enabled.Notes
Add concise factual notes: what happened, what was checked, the action taken, and any follow-up. Do not store passwords, OTPs, API keys, full payment credentials, or unnecessary sensitive personal data in notes.Investigate “paid but offline”
- Verify the payment reached a successful/final state and belongs to this subscriber.
- Check package, expiry, account status, pause/block state, and device limit.
- Review active/recent sessions and router health.
- Confirm the access credential or binding data.
- Disconnect stale sessions only when needed.
- Avoid creating a second payment or subscriber while the first record is unresolved.