Before you start
- Use the business email originally registered with K7abeer where possible.
- Check spam and junk folders for recovery messages.
- Never send an existing password, OTP, payment credential, API secret, or private key.
Procedure
Follow these steps in order
Use Forgot password
From the login page, request a password-reset message for the business email. Use only the newest unexpired link.
Complete identity verification
Enter the requested verification code or link and set a new unique password. K7abeer support cannot view the old password.
Report an inaccessible email
If the mailbox itself is unavailable, open the account-recovery path and provide the non-secret ownership evidence requested by the audited workflow.
Open a technical ticket
Include account email, branch, vendor, model, device or batch ID, app version, time of failure, full error text, and what changed immediately before the problem.
Authorize support deliberately
Support can inspect and repair only within assigned permissions and the audit trail. Device-wide or account actions still require the appropriate confirmation.
Verify success
- The new password signs in and the old password no longer works.
- Recovery and support actions appear in the audit trail.
- No secret was posted in the ticket.
Troubleshooting
No reset message arrives
Confirm the exact email spelling, check junk folders, wait for the latest request, and then use account recovery or contact support without creating duplicate business accounts.
Support asks for diagnosis details
Send identifiers, timestamps, app build, and error text. Do not send passwords, OTPs, active vouchers, or vendor secrets.
Was this guide helpful?
Your response helps the system owner prioritize documentation updates.