Master User approved mobile login, user-scoped extension binding, and a security layer ready for WhatsApp/device verification.
Amezay BOSS
Business Operating System Suite | Şirketinizin Ticari Omurgası
Mobile login and approval
Let every staff member work with their own account and their own extension.
Amezay Auth secures mobile access with a Master User controlled six-digit approval code. The Android app opens with the user’s own company, permissions, and extension instead of a shared founder token.
Six-digit Amezay Auth code sent to the Master UserMobile session bound to the user’s company and extensionCentral access shutdown when staff leaves
Amezay | IDENTITY
What this module fixes
A shared mobile account breaks security and audit trails. Amezay Auth verifies each staff member separately so calls, emails, and actions attach to the correct person.
Replaces shared mobile credentials with user-scoped, auditable mobile access.
A shared mobile account breaks security and audit trails. Amezay Auth verifies each staff member separately so calls, emails, and actions attach to the correct person.
Amezay | IDENTITY • 1
Six-digit Amezay Auth code sent to the Master User
When staff sign in on mobile, the Master User receives a six-digit approval code. The app does not open company modules until the code is verified.
Amezay | IDENTITY • 2
Mobile session bound to the user’s company and extension
After verification, the app opens with the user’s own company, permissions, and ACCSP extension so logs attach to the right staff member.
Amezay | IDENTITY • 3
Central access shutdown when staff leaves
The same foundation can expand into WhatsApp approval, device trust, Google Authenticator, and company-level session policies.
Amezay | IDENTITY • 1
Master User approved first login
When staff sign in on mobile, the Master User receives a six-digit approval code. The app does not open company modules until the code is verified.
- Controlled first mobile login
- Short-lived 10-minute OTP
- Safer device onboarding
Amezay | IDENTITY • 2
Personal extension context
After verification, the app opens with the user’s own company, permissions, and ACCSP extension so logs attach to the right staff member.
- User-scoped extension
- Personal call history
- Central Master User shutdown
Amezay | IDENTITY • 3
Expandable security backbone
The same foundation can expand into WhatsApp approval, device trust, Google Authenticator, and company-level session policies.
- Ready for WhatsApp verification
- Device and session policy foundation
- Tenant-scoped security settings
Amezay BOSS transition line
Move your company into one customer-memory and call-center control layer.
Leave a short request; we will map how your sales, service, calls, email, and customer history can move into BOSS.
Other modules
Other powerful layers running on the same BOSS system
Amezay | COMPANY
Keep holding, company, branch, and team structure on one governed business identity.
Turns scattered company data, roles, and onboarding gaps into one governed operating surface.
Amezay | CUSTOMER-CRM
Run customer ownership, opportunity flow, and follow-up rhythm from one operating spine.
Replaces scattered notes, personal spreadsheets, and missed callbacks with a governed CRM rhythm.
Amezay | PBX
Use your phone traffic as a managed commercial system, not just as a ringing line.
Turns the company number from a simple ringing line into a measurable and auditable sales/service channel.
Amezay | WHATSAPP
Keep customer conversations in company memory, not in personal devices.
Prevents the loss of customer communication, attachments, and decision history when staff changes.