Related links
Homepage
User documentation
Uživatelská dokumentaceFront-End Scripting
CMS - Content Management & Web API services
Task, Project, Quality
Task & Task pattern
System Management (part of framework)
HR - Human Resources
Mobile & Web Application
- clientprogramming_fevaldataobject
- userinterface-objectstructure
- cliplink
- npmlibraries
- fclip
- drag-drop
- AyMINE Application
- objectdefinition_inlineedit
- npmlibraries_stringlibrary
- clientprogramming
- mobileapplication
- languagesupport
- objectdefinition_multiupdate
- clientprogramming_fevalglobal
- clientprogramming_fevallanguage
- clientprogramming_fevaluser
- objectdefinition_viewdefinition
- offlineobjects
- System console
- Runtime debugging
- objectdefinition_detailview
Framework Core functionality
- prices
- managementfaq
- prices_private-installation
- clientdefinedattributes
- phplibraries
- servermethods
- io_export
- AyMINE Framework Server
- The AyMINE licence model
- System Rights
- servermethods_frmfrm
- io_import
- multiclient-architecture
- servermethods_stringsandtranslations
- frmevent
- System messaging
- usersessions
- User defined fields
Libraries & Lincences
Module - support for management
FI - Finance Management
Sales & Asset management
Sales related services
Description of a part of the AM module - sales part
Omni-channel Communication Support
Multichannel communication is the essential part of every CRM system
The CRM module supports major important communication channels:
Integration with system module
Communication gateways
Each channel has its own support. CRM module does not manage the communication gateways to the phone exchange or email server but uses the functionality of the system module.
Description of the communication gateways is here..
The business process
The communication business process is almost the same for all remote communication channels. The following scheme describes the call process:
Application process
Complete management of the voice call initiated by the CRM is rather complicated. the process goes over several modules as well as between front-end and back-end.
It is always initiated by used, but the complete call is managed by back-end. Even when user calls from mobile application, the call is initiated by the exchange.
The following process described technical implementation in the AyMINE:
