WayaDesk / Operations and recovery
A customer report often combines three questions: was money received, is the account entitled to service and is the device connected? Investigating them separately prevents the wrong corrective action.
Check payment evidence
Locate the merchant and application references and establish the recorded outcome. An unresolved attempt is different from a verified payment. Do not use a router symptom alone to decide whether money was received.
Check entitlement and policy
Inspect the package, paid-through date, scheduled future periods and any suspension. A valid payment may belong to a different period or account. A deliberate suspension should not be removed by an ordinary connection-recovery attempt.
Check current connection evidence
Review the intended access method and fresh router or accounting observations. A customer can have valid entitlement while their device is offline. Conversely, a session can require investigation if it remains active beyond the expected service boundary.
- Write down the observed state of each layer.
- Apply the corrective action only to the layer that needs it.
- Recheck the complete customer journey after the correction.
Give a precise explanation
Instead of saying “the system failed”, describe the confirmed stage and the unresolved stage. For example, a payment may be verified while the router path is unavailable. That tells the customer why another payment is unnecessary and tells the technician where to focus.
Frequently asked questions
Why not start by creating a new payment?
The problem may be policy or connectivity. A new payment can duplicate a legitimate purchase without repairing the fault.
What should an incident note contain?
The payment outcome, entitlement state, connection observation and the action taken, each with relevant references or times.
Choose your software licence
One installation, a clear router allowance, and perpetual use of the purchased version. Setup assistance, hosting and external services are separate.