In Genesys Cloud CX, you can programmatically add new prompts using the Architect API. The process involves three main steps:

1. Create the Prompt Object: Use the API to create a new prompt entity.

2. Create the Prompt Resource: Add a language-specific resource to the prompt, which can include text-to-speech (TTS) or audio content

3. Upload the Prompt's Media File: If using audio files, upload the media file to the prompt resource.

The Performance > API Usage page in Genesys Cloud CX provides a built-in dashboard that allows you to monitor the number of API requests, helping you track usage trends, detect anomalies, and manage limits effectively.

You can combine Genesys Cloud CX Voice and BYOC Cloud to leverage the benefits of both cloud telephony connection options. This hybrid approach allows organizations to utilize Genesys' fully managed telephony service while maintaining relationships with existing carriers.

Genesys Cloud CX enforces a maximum outgoing message size of 40 MB, including attachments, after base64 encoding. Base64 encoding increases the size of the original files by approximately 33%, so the combined size of the email body and attachments should be around 29 MB before encoding to stay within the limit. To manage larger files, you can upload them to Genesys Cloud Documents and include links to these documents in your email, effectively bypassing the attachment size limitation.

In Genesys Cloud CX, a number plan defines the structure of dialed numbers, including how many digits are expected and which patterns should be matched to properly route calls. This ensures consistent and accurate call handling across the system.

Genesys Cloud CX APIs default to JSON format for responses when no specific content type is mentioned in the request, as JSON is the standard data interchange format used across its RESTful API platform.

Cloud CX supports more than 100 agents per Management Unit. Management Units are used to logically group agents for scheduling and forecasting, and there is no such hard limit of 100 agents per unit.

In Genesys Cloud CX, Line Recording is disabled by default. To enable automatic recording of calls, the telephony administrator must configure the system by enabling recording on the SIP trunk. Without this configuration, calls are not automatically recorded.

Core Services in Genesys Cloud CX handle fundamental platform functions such as account configuration, directory search, user membership management, phone call routing, and agent assignment, serving as the backbone of system operations.

In Mandatory, Time-boxed, No early exit ACW, agents are forced into ACW status after an interaction and must remain in that status until the timeout completes. They cannot exit early, ensuring consistent post-call handling within the defined time window.

To connect to AudioCodes phones, which typically function as external SIP devices, you would configure an External trunk in Genesys Cloud CX. This allows SIP communication between Genesys Cloud and the AudioCodes device.

For a user to receive calls via a DID number or extension in Genesys Cloud CX, the number must be properly provisioned in the system's DID or extension pools. Additionally, the user must have the appropriate license, roles, and permissions to handle voice interactions. Missing either of these configurations will prevent call delivery.

Automatic Call Distribution (ACD) reduces wait time by efficiently routing incoming calls to the next available and most appropriate agent, minimizing idle time and ensuring quicker response for each customer.

Genesys Cloud CX uses attributes like agent language proficiency and defined skills (e.g., product knowledge, technical expertise) to route interactions to the most qualified agent, ensuring better customer service outcomes.

This statement is not true. In Genesys Cloud CX, numbering plans (or dial plans) can be created automatically using default settings or manually configured as needed. They are flexible and can be modified based on organizational requirements, but manual creation is not mandatory.

The StandardACD routing method in Genesys Cloud CX routes interactions to the nextavailableagent based on queue configuration, without modifying routing logic or preferences like skills or agent affinity. It ensures straightforward, availability-based distribution.

The Genesys Cloud CX API Change Management Policy categorizes changes as Breaking,Non-Breaking,New Feature, and Deprecations to define how changes are introduced and communicated. These types help manage expectations around compatibility, feature rollout, and transition periods for customers and partners.

Disabling file attachments in chat is managed under Security and Compliance settings in Genesys Cloud CX, where administrators control data sharing options to meet organizational security policies.

In the Genesys Cloud CX Notifications API, ping/pong messages are used to check the healthof the WebSocket connection. These messages help detect if the socket is still open or if it has been dropped, enabling appropriate client-side handling.