An EMI lock workflow connects a repayment account with an enrolled device.
An EMI lock workflow connects a repayment account with an enrolled device. The account can be current, overdue or disputed; the phone can be reachable, offline or awaiting an action. Those states do not always change at the same moment. Staff should understand both before promising a customer that a problem is resolved.
1. Establish the customer and device match
Before handover, verify that the device record belongs to the correct customer and sale. Explain the management process and support route. Complete enrollment using the supported setup method for that model; do not assume an already-used phone can be enrolled in the same way as a new one.
2. Track the installment and check exceptions
Review the agreed due date and match received payments to the right installment. A partial payment, late posting or duplicate receipt needs an explicit decision by the account owner. Reminder availability and automation rules should be confirmed for the chosen configuration.
3. Authorize and verify a device action
When a restriction is appropriate under the applicable process, the responsible operator issues the action. Sending a command is not proof that the phone has applied it. Confirm the resulting state and keep unresolved actions visible in your operating log.
4. Restore access and close the loop
After the payment or account error is resolved, arrange authorized unlocking and ask the customer to confirm the result. If the phone is offline, follow the provider’s supported reconnection procedure. Final settlement also needs an account-closure and release process; a temporary unlock alone does not document completion.
Continue with the next practical question.Prepare an Android device trialarrow_forwardUse your own device and repayment requirements for a product walkthrough.Explore the relevant RecTym solutionarrow_forward