Genesys Tempo is a workforce management application that enables agents to perform the scheduling tasks.

How do I create a time-off request?

At the bottom of the screen, tap Time Off. Then, to schedule a time-off request, to the upper right, tap Add .

How do I view my time-off with Genesys Tempo for iOS?

Tap Time Off. The Summary tab appears. This tab displays your pending requests, any approved requests for this week, and your upcoming approved requests.

To see all of your requests, tap All Requests.

What are the possible statuses of my time-off requests?

The following statuses are possible:

How do I use Genesys Tempo for iOS to create a time-off request with non-sequential dates?

Currently, Genesys Tempo does not support the ability to create time-off requests with non-continuous dates. You can use the web app to create a time-off request with non-continuous dates.

You can use Genesys Tempo to view time-off requests with non-sequential dates.

For time-off requests, what are the possible indicators I can see?

When you log on to Tempo, the following indicators are possible:

• No border around the date indicates that the date is available to request time-off.
• Fire on the date indicates that the date is filling fast; the hours available are less than three times the requested amount. For example, if I request eight hours and the hours under the limit are less than 24, a fire appears on the date.
• A red border around the date indicates that there is a short waitlist; five or fewer people requested time-off on that day. 
• A red filled box on the date indicates that there is a long waitlist; more than five people are on the waitlist after requesting time-off on that day. 
• An exclamation mark (!) on the date indicates that a time-off request is pending, but it violates one or more auto-approval rules in a time-off plan.
• A question mark (?) on the date indicates that a time-off plan doesn’t exist or is set to always require an Admin approval.
• The bar at the bottom indicates the requested time-off hours in yellow and the available balance in green.

What do the different pending messages mean for time-off requests?

Can I create a web chat without a deployment?

No. You can create web chats only by creating a widget. For more information about setting up a widget deployment, see Create a widget for web chat.

Do I have to use authenticated chat?

No. You can use a web chat without requiring authentication. For more information about setting up a widget deployment, see Create a widget for web chat.

Can I allow both authenticated chat and anonymous chat?

Yes. Create one deployment for authenticated chat and another deployment for anonymous chat. For more information about setting up a deployment, see Create a widget for web chat.

How do I know that authenticated chat requests to Genesys Cloud are only coming from my site?

Your site can request a signature for authenticated chat only if it has a valid OAuth token for your organization. Only you know the credentials for making requests to the Genesys Cloud API on behalf of your organization. As long as you secure your credentials, no one else can make requests to the Genesys Cloud API on your behalf.

What information is sent to Genesys Cloud with a signature request?

You can send as much or as little information as you want. The only required item is the OAuth token.

You cannot assign division directly to an existing contact. By default, all existing contacts appear as unassigned to a division. This display allows existing contacts to be visible to users who have the appropriate permissions.

To use divisions for external contacts, you must delete existing contacts and recreate them with the preferred division assignment. For more information about how to delete and recreate existing contacts, see Divisions for External Contacts quick start guide.

Limits define thresholds for specific areas of the Genesys Cloud API. These guardrails help to safeguard Genesys services from abusive and unexpected traffic patterns, encourage efficient use of billable resources, and protect customers from unexpected usage.

Genesys defines limitations in the Developer Center. For more information about limitations and limits that are specific to a feature, see Limits in the Developer Center. For information about Genesys Cloud system requirements, see Genesys Cloud system requirements.

Analytics data is subject to change because Genesys Cloud runs a batch process known as pipeline, which is a nightly job that takes place overnight in all regions. The job reprocesses raw event data and inserts it back into their respective data stores.

The main purpose of the pipeline process is the following:

• Make corrections to any minor real-time processing issues that can occur on the service. Real-time processing load is unpredictable, and if an event is overlooked, Genesys cannot rectify it in real-time. The batch processing that occurs nightly corrects these events.
• Fault tolerance: In the unlikely event where a large-scale issue occurs on Genesys Cloud’s real-time processing stack, the pipeline operates independently to correct data.
• Bug fix corrections: If a bug causes certain details or metric records to store incorrectly, these records can recalculate during the pipeline process.
• Compliance: The process of deleting data that you must remove for compliance reasons, such as GDPR in Europe.
• The rollout of new features, such as new, retroactive metrics.

The pipeline runs overnight and reprocesses data that is a minimum of 48 hours at the time that the job kicks off. However, the job can take longer due to the type of data being processed as well as other factors. If expected changes happen due to an issue in real time, the pipeline may begin processing that change after the conversation is at least three days old.

What should you do if you notice your data change?

• Check the release notes for new features released that may cause new calculations or new data points to add to the platform.
• Check the status page for any recent issues around real-time processing of analytics data.

Outside of any recent issues or releases, it is not expected behavior to see differences caused by pipeline rebuilding data nightly.

If you do notice changes, consider the following:

1. What data changes took place?
2. Is the change indicative of an improvement or a decline in the data under review?
3. If further investigation is required, make sure to provide the following to Genesys Product Support:
   • ID information (queue ID, user IDs, conversation ID).
   • What data changes took place?
   • What was the expected outcome?
   • The data where the change took place; for example, the conversation details or user details data.

If you are unfamiliar with how to gather the analytics data, contact Genesys Product Support.

Yes, co-browse relies on the Messenger snippet to continue the session when you navigate across pages.

You can find the interaction Fax Analytics in the Interactions view.

Note: Under the Available columns section, you can view the list of available column names and their descriptions. If you cannot find a column in the table, in the search bar, enter the name of the column to view its name and description.

For example, under the Available columns section, in the Interactions section’s search bar, search Fax to view the Fax column and its description. 

For various reasons, some organizations must remove voicemail functionality from certain users. To deactivate voicemail for a specific user, remove the Voicemail > Voicemail > Receive permission from the user’s role. For more information, see Edit a role.

Administrators can enable multiple actions on a single email that allows agent to perform different actions on a single email such as replies and forwards before they disconnect and wrap-up the interaction. For more information, see Use the organization’s email domain name.

For more information on how the option appears on the agent desktop, see Reply to or forward an email message interaction.

To disable the /giphy chat command for users, remove the C hat > Giphy > Access permission from user roles. By default, the permission is included in the Employee role. When a user types /giphy in a chat room without the permission, Genesys Cloud does not display search results from the Giphy website and the user cannot select a Giphy image to insert into the chat room. Users can still manually insert an image into a chat room. For more information about how to remove permissions from roles, see Edit a role.

Retraining fails due to insufficient data for certain media types, because of a reduced number of interactions on the queue since activation. For more information, see Predictive routing during KPI processing phase.

An error occurs either because of insufficient data to create a data model or because of an unlikely system error. For more information, see Predictive routing during KPI processing phase.

Genesys Cloud includes three independent concepts that people often call locations:

• A location is a specific, physical place with an address. An admin configures locations. Locations appear in the Location section of your profile.

• A geolocation is a geographic area that Genesys Cloud determines by IP address. An admin can enable or disable geolocation for an organization. Your geolocation appears near your name and photo on your profile page, on your contact card, at the top of a chat window, and in Genesys Cloud search results for your organization.

• A site is a container for phone and BYOC Premises Edge configuration information and must have a designated location. While a site can have the same name as a location, the two are independent concepts. A telephony admin configures sites.

To modify the reporting structure as it appears in the Hierarchy Tree view, update the user’s profile.

The information in the Relationships section determines the reporting structure.

To configure agentless SMS notifications from an Architect flow:

1. Create a data action that calls the SMS notification API. For more information, see About the Genesys Cloud data actions integration.
2. Use that data action within the flow. For more information, see Use data actions in Architect for integrations.

You can access agentless SMS notifications by a public API. For more information, see the Conversations page and the Agentless SMS notifications page in the Developer Center.

For more information on the expected data storage for an org based on the number of calls, average duration, retention time, and optional screen recording, see Data storage charge examples.

Yes.  If the site is configured with the default numbering plans, the Edge will accept the number and then normalize it to the E.164 number format (with the ‘+’).

For Genesys Cloud feature subscription package information, see the Genesys Cloud feature matrix and Overview of Genesys Cloud CX. For more information about licensing, see About licenses.

The Edge Mini and the Edge Micro are physically identical in that they both use the same chassis. So the only way to distinguish between them is by the size of the hard disk. The Edge Micro has a 256 GB hard disk while the Edge Mini has a 512 GB hard disk. You can slide out the externally removable solid-state drive to examine them.

Genesys recommends labeling the Mini and Micro Edges when you receive them.

For more information, see About BYOC Premises – Genesys Hardware Solution.

There are five Edge versions that you can be using in a BYOC Premises – Genesys Hardware Solution organization:

• Edge Standard v1
• Edge Standard v2
• Edge Standard v3
• Edge Mini
• Edge Micro

The v1 is a custom server built by Genesys. The v2 and v3 are built on Hewlett Packard system and customized to Genesys Cloud specifications. The Mini and Micro are built on an Advantech system and customized to Genesys Cloud specifications. For more information, see About BYOC Premises – Genesys Hardware Solution.

You can identify the version of an Edge by the serial number.

To find the serial number:

1. Click Menu > Digital and Telephony > Telephony > Edges.
2. Select the check box for the row that contains the Edge you want identify.
3. Click Edit Edge on the toolbar.
4. On the General tab, locate the information panel, and find the Serial Number.

Edge standard

If the serial number begins with the letters CCP, then it is a Edge Standard v1. If the serial number begins with any other letters or numbers, then it is either an Edge Standard v2 or an Edge Standard v3.

To determine whether it is a Standard v2 or a Standard v3:

1. Take note of the serial number.
2. Access the Hewlett Packard Enterprise Support Services Central site.
3. Enter the serial number when prompted.

If the result is HPE DL60 Gen9, then you have a Edge Standard v2.

If the result is HPE DL360 Gen10, then you have a Edge Standard v3.

Edge Mini or an Edge Micro

If the serial number begins with the letters KSA or ACG, then it is either an Edge Mini or an Edge Micro. Unfortunately, you can’t actually differentiate the Edge Mini and the Edge Micro from the serial number. To tell them apart, you have to have physical access to the device.

The Edge Mini and the Edge Micro are physically identical in that they both use the same chassis, so telling them apart depends on when they were manufactured.

In some cases, you can tell them apart by the model number found on the sticker on the bottom of the chassis.

• If the model number is ARK-1550-S9A1E, then you have an Edge Mini.
• If the model number is ARK-1550-S6A1E, then you have an Edge Micro.

If the model numbers do not correspond to this scheme, the only way to distinguish between them is by the size of the hard disk. The Edge Micro has a 256 GB hard disk while the Edge Mini has a 512 GB hard disk. You can slide out the externally removable solid-state drive to examine them.

Genesys recommends labeling the Mini and Micro Edges when you receive them.

You must be a member of owners-only or members-only Genesys Cloud groups to administer chat notifications (webhooks) to those groups. If you are not a member of those groups, you won’t find them when you attempt to specify the Chat Target in the Genesys Cloud configuration. Ask the owners of those groups to add you as a member and then remove you when the configuration is completed.Note: You can administer notifications to public groups without being a member.

If you are using a Genesys Cloud Communicate license, then you have 2TB of storage available per organization.

If you are paying for a Genesys Cloud CX 1, Genesys Cloud CX 2, or Genesys Cloud CX 3 license, then you have unlimited storage available for all users.

See also How many documents can I upload?

No. Genesys Cloud does not support the use a private STUN/TURN server nor does it support private proxy servers. Genesys Cloud provides STUN and TURN services; in addition, it leverages Google’s global network of STUN (not TURN) servers for faster and better NAT traversal. If you disable them, then you will experience broken or slow NAT traversal during the connection of features like video chat or WebRTC phones. 

Add the Conversation > Fax > Send and Conversation > One Number Fax > Receive  permissions to the user. No default roles include these permissions, so add them to a new or existing role and then add that role to the user. For more information about roles and permissions, see Products, roles, and permissions list. 

If you have a physical phone set as your default phone, then you can make and receive calls on that phone even if you are logged off of Genesys Cloud. Ask your administrator if you are unsure which phone is your default phone. If you are an administrator and want more information about how to assign a default phone to a user, see Assign a default phone. 

If you do not have a physical phone set as your default phone and are logged off of Genesys Cloud, then you can still receive calls to your phone number in Genesys Cloud. Before you log off, enable call forwarding. Genesys Cloud forwards any calls made to your Genesys Cloud number to the number of your choice. 

When a user sends a fax, Genesys Cloud converts the file to TIF file format and sends it to the appropriate device depending on your telephony connection. If you are using BYOC Premises, that location is an onsite edge device. If you are using either BYOC Cloud or Genesys Cloud Voice, that location is a cloud media device.

The device then sends the file to the user-entered number using your SIP trunks. If the file did not originate in Documents, Genesys Cloud also stores the original file in its original format in the user’s workspace in Documents. For information about how to send a fax from Genesys Cloud, see Send a fax.

Since a user has the same number for both incoming calls and faxes, the device must detect whether an incoming call is a voice call or fax. If fax detection is enabled and the device detects incoming fax tones, it negotiates the T.30 transmission, receives the image data, and sends the file to Genesys Cloud in TIF format. Genesys Cloud then converts the TIF file to a PDF file and sends it to both the user’s inbox and workspace in Documents. For information about how to view received faxes in Genesys Cloud, see View faxes in the inbox.

Genesys Cloud uses public IP addresses provided by Amazon. These public IP addresses change frequently. For more information, see About ports and services for your firewall.

Some permissions are not associated with any default roles in Genesys Cloud. For a complete list of permissions not assigned to a role by default, see the unassigned tab in the Products, roles, and permissions list.

If you want your users to have these permissions, add the permission to a default or user-added role and assign the role to the users you want to have the permission.

Contact center agents and supervisors need extra roles assigned to them so they can see the features they need to complete their work.

• Agents need the User role in addition to the Genesys Cloud User role.
• Contact center supervisors need the Supervisor role in addition to the Genesys Cloud Supervisor role. 

If a user has a DID number or extension assigned to them and they cannot receive calls through that DID number or extension, check the following:

• If the user has both a DID number and extension, the DID number and extension are entered as different phones in the user’s Contact Information section in their profile. The DID number and extensions are considered different numbers and cannot be entered as the same phone. See Set your contact options.
• The DID number and extension are listed and defined in the DID or extension pools. 
• The user has the proper license type, roles, and permissions. See Check a user’s permissions. 

To receive voicemail, a user must have the Voicemail > Voicemail > Receive permission enabled. This permission is assigned to the Communicate – User role by default. If a user is assigned the Communicate – User role, the voicemail option should appear. If the voicemail option does not appear, see Products, roles, and permissions list for instructions on how to add the voicemail permission. You can also add the  Voicemail > Voicemail > Receive permission to other roles. For more information, see Roles and permissions overview.

To view your voicemails, see Access your voicemail. 

Automatic speech recognition (ASR) is enabled by default for the starting menu of new call flows. If no ASR terms are defined on the starting menu, the system can disconnect the caller. To prevent unintentionally disconnecting callers, define valid ASR terms for the menu options or override ASR for the call flow. See Basic flow design steps and Set up the starting menu.

To view your organization ID, follow these steps:

1. Click Menu > Account > Organization Settings.
2. Click Advanced.

Genesys Cloud displays your organization ID.

Click the link below for Genesys Cloud’s operational, system availability, incident, and outage information. Use the Subscribe to Updates button to receive status updates through email, SMS notifications, or RSS or Atom feeds.

Genesys Cloud System Status

Call recording requires that Line Recording is enabled on the SIP trunk by a telephony admin. Complete the Enable recording on the trunk procedure. 

There is a rate limit of 10 webhook notifications per second. If you are seeing some notifications but not others, try narrowing the focus of the webhook mappings by adding more filters.

Open the flow for which you want to enable company directory support and in the flow’s Settings area, select Recording and Speech Recognition. In the Recording and Speech Recognition design area, under General Speech Settings, complete the following steps:

1. Select the Enable speech recognition for the entire flow check box. 
2. From the Company Directory list, select the Enable for entire flow check box.

Genesys Cloud can connect to any PBX that supports SIP. However, Genesys Cloud cannot currently share data, such as status or prior input, with these PBXs. 

When you log in to the browser app, desktop app, or mobile app, you are prompted to select the region where your organization was created, for example, Americas (US East), Americas (US East 2), Americas (US West), Americas (Canada), Americas (São Paulo), Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Sydney), Asia Pacific (Tokyo), EMEA (Dublin), EMEA (Frankfurt), or EMEA (London). If you are already logged in, log out and log back in with the region selected.

Whether you are in the office, at home, or traveling, your access to Genesys Cloud is routed to the URL corresponding to the location of the Amazon data center for your region. 

If you are unsure of your region, contact your Genesys Cloud administrator. Alternatively, try these work-arounds.

• First time log in: Access the Genesys Cloud login URL for each region. Log in will be successful only with the URL corresponding to your organization’s region.
• Currently logged in: (Web app only) The web app URL corresponds to your organization’s region.

Yes. Toggle the Open Admission switch to OFF in the Organization Settings. See Configure invite links.

Genesys Cloud for Salesforce is based on the Salesforce Open CTI APIs, which is what Salesforce currently supports. The CTI Toolkit has reached end of support with Salesforce and is not used with the integration.

For more information about the integration, see About Genesys Cloud for Salesforce.