Skip to content

Requirements & Security

To ensure a seamless and secure experience with Mobile4ME, please verify that your environment, devices, and Genesys Cloud organization meet the following prerequisites.

  • Operating System: iOS 15.0 or later.
  • Hardware: iPhone 8 or newer recommended.
  • Storage: Minimum 1 GB of free space.
  • RAM: Minimum 4 GB recommended for optimal performance.

Mobile4ME requests the following permissions to provide full contact center functionality on your device:

Permission Scope Purpose Required For
Microphone Enables voice call capabilities and audio recording. Voice Interactions
Notifications Delivers real-time push notifications for incoming calls, chats, and callbacks. Core App Functionality
Camera Allows agents to capture and send photos in Web Chat or WhatsApp interactions. Rich Media Messaging
Storage / Photos Secures access to local files to upload documents or save received media. Rich Media Messaging
Contacts Allows synchronization with the corporate directory or local device contacts for outbound dialing. Outbound Interactions

To integrate Mobile4ME, your Genesys Cloud organization must meet these requirements:

Licensing

  • Genesys Cloud CX 1, 2, or 3 license.
  • Appropriate user licenses for all agents who will use the app.

Configuration

  • An active OAuth Client configured for Mobile4ME.
  • Agents must be assigned to the correct Roles and Divisions (see our Setup Guide).

For Mobile4ME to function correctly, your network or VPN must allow traffic to specific domains and ports:

  • Mobile4ME Infrastructure: HTTPS (port 443) access must be allowed to *.mobile4me.app.
  • Genesys Cloud Infrastructure: The application relies on standard Genesys network requirements for WebRTC voice calls, API access, and WebSocket real-time events. For a complete list of required domains, ports, and IP addresses, please refer to the official Genesys Cloud Network Requirements.

Mobile4ME is built with enterprise security in mind:

  • Authentication: Fully relies on Genesys Cloud OAuth 2.0. No user credentials are saved locally. For OAuth configuration, please refer to:
  • Data Encryption: All data in transit is encrypted using TLS 1.2+. Local caching is encrypted using native mobile secure enclaves (Keychain on iOS, Keystore on Android).
  • Session Management: Automatically synchronizes session timeouts with your Genesys Cloud organization policies.
Request Priority Response Time Scope
Critical Immediately or within 1 (one) hour after contact by phone, within the contracted service modality. Total unavailability of the platform.
High Within 2 (two) hours after contact by e-mail or ticket creation, within the contracted service modality. Partial unavailability of the platform or performance not meeting the original specifications, affecting more than 50% of the operation.
Normal Within 4 (four) hours after contact by e-mail or ticket creation, within the contracted service modality. Partial unavailability of the platform or performance not meeting the original specifications, affecting less than 50% of the operation.
Low Within 24 (twenty-four) hours after contact by phone or ticket creation, within the contracted service modality. A system component is inoperative or performing below the original specifications, causing a low or insignificant impact on the operation.
Inquiry Within 72 (seventy-two) hours after contact by phone or ticket creation, within the contracted service modality. Requests for information or clarification regarding the system and its components.

Last updated: