Call module that connects inbound/outbound calls, IVR, recordings, transfer, conference, callbacks, and WhatsApp voice bridge events to the customer log.
Amezay BOSS
Business Operating System Suite | Şirketinizin Ticari Omurgası
Call center / PBX / IVR
Use your phone traffic as a managed commercial system, not just as a ringing line.
ACCSP is the embedded BOS call backbone for inbound handling, routing, recording, voicemail, callback generation, customer-card linkage, and compliant WhatsApp voice-call bridging through an official provider.
Web and mobile PBX surfaceTransfer, conference, extension, and voicemail supportQueue strategy, SLA target, wait-time, and callback policyPublic-sector, call-center, and high-volume service desk scenariosWhatsApp Business Calling API / SIP provider bridgeCall recording and customer-card linkage
Amezay | PBX
What this module fixes
Phone conversations stop disappearing into personal operator space. You can audit who called, how long the caller waited, what happened, and whether a callback is still required.
Turns the company number from a simple ringing line into a measurable and auditable sales/service channel.
Phone conversations stop disappearing into personal operator space. You can audit who called, how long the caller waited, what happened, and whether a callback is still required.
Amezay | PBX • 1
Web and mobile PBX surface
When the company number and extension tree are defined inside BOS, calls are stored together with customer, operator, and process context.
Amezay | PBX • 2
Transfer, conference, extension, and voicemail support
If a call is not answered, voicemail can be collected, callback work can be generated, and any future match can be attached to the same customer story.
Amezay | PBX • 3
Queue strategy, SLA target, wait-time, and callback policy
With an official WhatsApp Business Calling API path or compliant SIP provider, WhatsApp voice calls can enter the Amezay PBX backbone and become part of customer-card, recording, transfer, and follow-up flow.
Amezay | PBX • 4
Public-sector, call-center, and high-volume service desk scenarios
Transfer, conference, recording, and extension-assignment rules keep the phone system under institutional discipline instead of letting it fragment across personal devices.
Amezay | PBX • 5
WhatsApp Business Calling API / SIP provider bridge
Amezay | PBX does more than ring phones. It makes queue strategy, agent ring timeout, maximum queue wait, SLA answer targets, after-call wrap-up, and missed-call callback policy manageable per tenant.
Amezay | PBX • 6
Call recording and customer-card linkage
For municipalities, universities, public offices, hospitals, and multi-branch companies, call traffic should not overload one operator. IVR, live agents, recording, reporting, identity-verification readiness, and VOKA live-translation vision are planned on the same control layer.
Amezay | PBX • 1
The company number lives inside BOS
When the company number and extension tree are defined inside BOS, calls are stored together with customer, operator, and process context.
- Extension tree and queue control
- Inbound greeting and routing
- Central founder/admin history
Amezay | PBX • 2
Voicemail and callback logic
If a call is not answered, voicemail can be collected, callback work can be generated, and any future match can be attached to the same customer story.
- Controlled 60-second voicemail
- Missed-call and callback visibility
- Context carried into repeat contact
Amezay | PBX • 3
WhatsApp voice bridge
With an official WhatsApp Business Calling API path or compliant SIP provider, WhatsApp voice calls can enter the Amezay PBX backbone and become part of customer-card, recording, transfer, and follow-up flow.
- Log WhatsApp call events to the customer record
- Route provider SIP bridge into the PBX queue
- Handle transfer and conference on the PBX bridge
Amezay | PBX • 4
Team call discipline
Transfer, conference, recording, and extension-assignment rules keep the phone system under institutional discipline instead of letting it fragment across personal devices.
- Transfer and conference flows
- Founder-controlled recording history
- Seat and extension management
Amezay | PBX • 5
Queue, SLA, and call-center control
Amezay | PBX does more than ring phones. It makes queue strategy, agent ring timeout, maximum queue wait, SLA answer targets, after-call wrap-up, and missed-call callback policy manageable per tenant.
- Round-robin, ring-all, least-recent, and similar queue strategies
- SLA answer target, wrap-up duration, and maximum wait control
- Missed calls, voicemail, and callbacks written into customer memory
Amezay | PBX • 6
Public-sector and large service-desk vision
For municipalities, universities, public offices, hospitals, and multi-branch companies, call traffic should not overload one operator. IVR, live agents, recording, reporting, identity-verification readiness, and VOKA live-translation vision are planned on the same control layer.
- High-volume inbound calls, multilingual greeting, and internal routing
- Recording retention, access control, and audit-ready infrastructure
- Direct link to customer, student, citizen, or supplier memory
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 | IDENTITY
Let every staff member work with their own account and their own extension.
Replaces shared mobile credentials with user-scoped, auditable mobile access.
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.