Innovation reference

Did you know? Genesys Cloud CX facts, checked

Every one of the 102 “Did you know?” facts from our Innovation articles in one place, each checked against current Genesys documentation, with the article it comes from and its sources.

As-built evidence in one click: users, phones, queues and groups in a single row

  • Did you know that a Genesys Cloud bulk people import adds roles and queues to existing users but does not replace or remove them? Assignments made over time can quietly accumulate unless someone reviews them.
  • Did you know that CX as Code includes a special genesyscloud_tf_export resource that exports existing Genesys Cloud resources into a local Terraform JSON configuration file? It is configuration as code, designed for managing and promoting configuration.
  • Did you know that Genesys distinguishes counted limits, known as platform quotas, from rate limits, and that API rate limits are generally scoped at a token or user level? A full-org traversal has to be paced to stay inside them.
Sources for these facts
  1. Work with the People page – Genesys Cloud Resource Center
  2. Bulk upload of people data – Genesys Cloud Resource Center
  3. CX as Code – Genesys Cloud Developer Center
  4. Limits – Genesys Cloud Developer Center

Authenticating your customers in Genesys Cloud web messaging with OpenID Connect

  • Did you know authenticated web messaging needs only the openid scope, identifies the customer by the sub claim, and builds their name from given_name and family_name, so a provider that returns only a name claim leaves the name unpopulated unless the userinfo endpoint supplies them?
  • Did you know authenticated web messaging does not support RSA keys shorter than 2048 bits from the authorisation server, so an older identity provider configuration can fail before a single message is sent?
  • Did you know Genesys ended support for ACD Web Chat version 2, and every Chat Widget version that used it, on 11 June 2025, leaving web messaging and Messenger as the route for website conversations?
  • Did you know Genesys Cloud retains web messaging conversation history for up to 18 months for Identified and Curated contacts, but for 15 days for all other contact records?
Sources for these facts
  1. Authenticated web messaging overview
  2. Enable authenticated web messaging
  3. Get started with authenticated web messaging
  4. Authenticated web messaging attributes
  5. Authenticated web messaging quick start guide
  6. Authenticated web messaging (Developer Center)
  7. Identity stitching and journey support coming to authenticated web messaging
  8. Release notes: November 3, 2025
  9. Guest session duration for web messaging
  10. Deprecation: Removal of ACD Web Chat (version 2)

Auto answer in Genesys Cloud: voice, messaging and email, designed with care

  • Did you know there is no hierarchy between queue-level and agent-level auto answer in Genesys Cloud, so an interaction is auto answered when the setting is enabled in either place?
  • Did you know that when you change a queue's auto answer setting, Genesys Cloud treats it as a fresh update and removes every existing channel-level override, which you must then set again?
  • Did you know a queue's voice channel can play whisper audio only to agents configured for auto answer, and plays an audio tone instead when no whisper prompt is configured?
  • Did you know the total interaction time of an auto-answered interaction includes the time between the auto answer and the moment the agent actually picks it up?
Sources for these facts
  1. Auto answer incoming interactions
  2. Turn on auto answer for agents
  3. Work with auto answer enabled interactions
  4. Set behavior and thresholds for voice and chat channels
  5. Agent utilization
  6. Improved auto-answer configuration and toast message control
  7. Digital reporting revision for auto answer
  8. Deprecation: Removal of ACD Web Chat (version 2)

Borrowing agents safely: conditional group routing vs Conditional Group Activation

  • Did you know that if the first conditional group routing rule is not met, Genesys Cloud treats the queue as healthy, deactivates the groups of every later rule and evaluates no further rules, rather than moving on to rule 2?
  • Did you know that Conditional Group Activation counts agents who are working on workitems as idle in its idle agents KPI, while agents deactivated by CGA or CGR are not counted?
  • Did you know that conditional group routing cannot route workitems, and that CGA and CGR can never both be configured on the same queue?
  • Did you know that CGA evaluates queue health on a schedule, for example every 30 seconds, so a group it opens is available to every waiting conversation, not only to the one that has just arrived?
Sources for these facts
  1. Conditional group routing overview
  2. Conditional Group Activation overview
  3. Create and configure queues
  4. Enhanced conditional routing with conditional group activation (CGA)
  5. Why am I not able to change the queue name in the first CGR rule?
  6. CX as Code: genesyscloud_routing_queue_conditional_group_activation

Building a native iPhone app on Genesys Cloud: verified messaging, live video and location

  • Did you know that Genesys publishes an open-source Messenger Transport SDK for iOS and Android? It is a thin network layer over the Web Messaging Guest APIs, so a native app can use Genesys Cloud messaging with its own interface instead of the Messenger web window.
  • Did you know that an inbound message flow in Architect can read Message.IsAuthenticated? It tells the flow whether the customer signed in through authenticated messaging, so routing, greetings and screen pops can treat verified and anonymous customers differently.
  • Did you know that the Genesys Cloud Agentless SMS API, by default, will not send to a customer who already has a connected SMS conversation, whether in a flow, in a queue or with an agent? An optional setting changes that behaviour.
  • Did you know that the Messenger Transport SDK accepts files of up to 10 MB from the customer and up to 25 MB from the agent, with the permitted file types set by a supported content profile in Genesys Cloud?
Sources for these facts
  1. Messenger Transport Mobile SDK overview – Genesys Cloud Developer Center
  2. Authenticated session (Messenger Transport Mobile SDK) – Genesys Cloud Developer Center
  3. Generic file attachment (Messenger Transport Mobile SDK) – Genesys Cloud Developer Center
  4. Mobile Messenger feature comparison matrix – Genesys Cloud Resource Center
  5. Mobile apps for iOS and Android – Genesys Cloud Resource Center
  6. Deploy Messenger – Genesys Cloud Resource Center
  7. Authenticated web messaging attributes – Genesys Cloud Resource Center
  8. Agentless SMS notifications – Genesys Cloud Resource Center
  9. Manage script properties – Genesys Cloud Resource Center
  10. Configure mobile push notifications – Genesys Cloud Resource Center

CX Pulse: a push-driven Genesys Cloud presence wallboard, team by team

  • Did you know that a Genesys Cloud routing status – Off Queue, Idle, Interacting, Communicating or Not Responding – is set by the system, not the agent? Agents are placed in Not Responding automatically when they do not pick up an interaction within the queue’s timeout.
  • Did you know that each Genesys Cloud notification WebSocket is limited to 1,000 topics, and that subscribing to more returns a 400 error? Watching an agent’s presence and routing status costs two topics, so one channel can stream at most 500 agents.
  • Did you know that a PUT to a Genesys Cloud notification channel’s subscriptions replaces the whole topic list, whereas a POST adds to it? Channels stay active for 24 hours, and an application can hold up to 20 of them.
Sources for these facts
  1. Routing status – Genesys Cloud Resource Center
  2. Presence, status, and activity indicators overview
  3. Agents Status Detail view
  4. Performance dashboards overview
  5. About views and dashboards
  6. Notifications – Genesys Cloud Developer Center

Every conversation, flattened: bulk Genesys Cloud detail export with analytics jobs

  • Did you know that the synchronous conversation detail query endpoint accepts interval start dates up to 558 days in the past, and that Genesys recommends the asynchronous conversation detail jobs endpoint for historical queries?
  • Did you know that a conversation detail query can cover at most seven days when it has no filter, and up to 32 days with a filter? Detail jobs lift those interval restrictions, which become a function of the data volume instead.
  • Did you know that the data behind conversation detail jobs is not continuously updated in real time? Depending on when you query, it may be hours to a full day behind, and each result carries a dataAvailabilityDate.
  • Did you know that the Interactions view export limits conversations less than 24 hours old to 10,000 per 12-hour period, while older interactions can be exported up to 1,000,000 conversations in a single export?
Sources for these facts
  1. Analytics Conversation Detail Endpoint API query interval change – Genesys Cloud Resource Center
  2. Conversation detail record jobs – Genesys Cloud Developer Center
  3. Conversation detail queries – Genesys Cloud Developer Center
  4. Conversation Data Model – Genesys Cloud Developer Center
  5. Export view data – Genesys Cloud Resource Center
  6. Interactions view – Genesys Cloud Resource Center
  7. Historical execution data overview – Genesys Cloud Resource Center
  8. Limits – Genesys Cloud Developer Center

Finding what redaction missed: scanning Genesys Cloud transcripts for PII and card data

  • Did you know that Genesys Cloud shows unredacted transcripts only to users with the Recording > Recording > View Sensitive Data permission, that no role includes it by default, and that an administrator must grant it manually?
  • Did you know Genesys states that Automated Sensitive Data Masking is not PCI DSS compliant? It is a safety net for when agents forget Secure Pause; only Secure Pause and Secure Call Flows are validated by a Qualified Security Assessor as Level 1 compliant.
  • Did you know that, according to Genesys, the headers and descriptions of AI-generated transcript outlines are not redacted, so users with access to outlines may see information that is redacted in the transcript itself?
Sources for these facts
  1. Enable automatic redaction of sensitive information
  2. Work with a voice transcript
  3. PCI DSS compliance – Genesys Cloud Resource Center
  4. Is Automated Sensitive Data Masking PCI DSS compliant?
  5. Secure flows overview
  6. Speech and Text Analytics APIs – Genesys Cloud Developer Center

Flow Journey: the story of one call through every Architect flow it touched

  • Did you know Genesys Cloud offers four levels of historical execution data, Base, Notes, Verbose Notes and All, set as an organisation default and overridable for an individual flow?
  • Did you know flow execution data cannot be queried by start or end date and time, so Genesys recommends narrowing queries by conversationId, with at most 200 instances returned per query?
  • Did you know secure flows only ever report execution data at the Base level, and common module flows have no execution data of their own: they appear inside the data of the flow that invoked them?
Sources for these facts
  1. Historical execution data overview
  2. Manage historical execution data
  3. Use replay mode to troubleshoot an Architect flow
  4. Flow execution history
  5. Build a flow execution history query

Flow Mapper: see every Architect flow whole, audit it, and document it as built

  • Did you know Architect's Dependency Search covers only checked-in and published flows, and does not include prompts fetched through an expression, because those dynamic prompts are evaluated only when the flow runs?
  • Did you know that from inside a common module, bot, in-queue call or secure call flow, Architect's Find consuming flows lists the other flows that consume it?
  • Did you know Architect's Dependencies pane, under a flow's Resources, lists every resource the flow uses, such as queues, skills, users and wrap-up codes, with a link to each place it is used?
Sources for these facts
  1. View dependencies in the flow
  2. Dependency Search tab
  3. Search for flows by dependency
  4. Navigate the Architect home page
  5. Use replay mode to troubleshoot an Architect flow

Flow Narrator: a plain-English as-built of every journey through your Architect flows

  • Did you know Architect can export a flow in YAML as well as its own configuration format, and can optionally include the tracking ID of every action, menu and task in the exported file?
  • Did you know sequence builders are not supported when Architect exports a flow in YAML, and are rendered as equivalent expressions that still function as expected?
  • Did you know Architect's Dependency Search applies only to checked-in and published flows, so working flows and flows saved but not checked in or published are not included in its results?
Sources for these facts
  1. Import or export a flow
  2. Define Architect flows using YAML
  3. View dependencies in the flow
  4. Dependency Search tab
  5. Welcome to Archy

Genesys Cloud IP addresses and ranges for firewall allow lists, by region and purpose

  • Did you know that GET /api/v2/ipranges takes no parameters and, in the Platform API definition, lists no required permission – any valid OAuth token for your org can read it – while each entry carries its own CIDR, service, region and direction?
  • Did you know the direction field on each Genesys Cloud IP range is defined from the perspective of Genesys Cloud – inbound to Genesys or outbound from Genesys – rather than from your network’s point of view?
  • Did you know Genesys recommends that, wherever you build an allow-list from the Amazon AWS IP address file, the AWS Global region must always be included, even if you otherwise limit the list to your region?
Sources for these facts
  1. IP addresses for the firewall allowlist
  2. Bot Connector IP address range for your allowlist (FAQ)
  3. Allow IP addresses – Genesys Cloud Resource Center
  4. Ports and services for your firewall overview
  5. API Explorer – Genesys Cloud Developer Center
  6. AWS regions for Genesys Cloud – Genesys Cloud Resource Center

Genesys Cloud workitems and task routing: a practical guide to Work Automation

  • Did you know that every Genesys Cloud workitem always sits in exactly one workbin, even while it is queued for or assigned to an agent, and that a workbin's division can never be changed?
  • Did you know that once a Work Automation schema is saved, neither the schema nor its custom attributes can be deleted, and Genesys advises against storing PII, PCI or PHI data in them?
  • Did you know a workitem can wait in a queue for assignment for up to 60 days, after which it is removed from the queue and its assignment state becomes AcdExpired?
  • Did you know that conditional group routing and predictive routing are not available for workitems, which route with standard, bullseye or preferred agent routing, or by direct assignment through the API?
Sources for these facts
  1. Work automation overview
  2. Define a worktype
  3. Create custom attributes for work automation
  4. Create a workbin
  5. Work with workitem flows
  6. Task Management (Developer Center)
  7. Workitem assignment (Developer Center)
  8. Can I blend workitems into a queue with other media types?
  9. What are the billing rules for the work automation add-on?
  10. Work Automation introduces a consumption-based pricing model

How to build a secure Genesys Cloud callback request form for your website

  • Did you know Architect's Create Callback action, available in inbound, in-queue and outbound call flows, does not let callers schedule a callback for a specific date or time, whereas the Create Callback API accepts a callbackScheduledTime?
  • Did you know the key-value pairs you send in the data property of a Create Callback request appear in the attributes property on the conversation participant, ready for scripts and flows to use?
  • Did you know a client credentials token is not in the context of a user, so endpoints such as /api/v2/users/me are unavailable, and the OAuth client's access comes from the role and division pairs assigned to it?
  • Did you know that when the Genesys Cloud Platform API rate-limits a request it returns HTTP 429 with a Retry-After header, and the unit of that header is seconds?
Sources for these facts
  1. Schedule callbacks from a website
  2. Create Callback action
  3. Schedule a callback
  4. Callbacks overview
  5. Create an OAuth client
  6. OAuth client secret no longer visible after creation
  7. Restrict OAuth client credentials grants to allowed IP addresses
  8. Client credentials grant (Developer Center)
  9. Platform API regions and hosts (Developer Center)

IVR Sankey: every call through your Genesys Cloud IVR, on one map

  • Did you know Architect's journey flows show up to seven days of data, a fixed 168-hour period counted back from the most recent midnight UTC, and that Genesys recalculates the paths overnight?
  • Did you know the analytics conversation detail jobs API returns participant attributes for each conversation, with keys and values truncated to 1,024 characters, but that its data can run hours to a full day behind real time?
  • Did you know Genesys describes journey flow counts as directional and not intended to be exact, and that for flows with many milestones or outcomes the view may be limited to the most frequent paths?
Sources for these facts
  1. Journey flows overview
  2. Differences between Journey Management and journey flows
  3. Use Flow Insights to view the frequency of executed flow components
  4. Historical execution data overview
  5. Conversation detail record jobs
  6. Conversation data model

Importing external call recordings into Genesys Cloud EX: a practical guide

  • Did you know a Genesys Cloud EX organisation does not handle voice, email or digital interactions itself, yet can synchronise voice and email interactions, and voice recordings, from an external platform so supervisors can evaluate calls taken elsewhere?
  • Did you know Genesys supports one presence source per organisation, and expects the external platform to be the source of truth for both agent presence and routing status in a Genesys Cloud EX organisation?
  • Did you know Genesys Cloud EX bills an employee when an interaction event is injected for them, and that this billing scenario does not require the employee to log in during the month?
  • Did you know the fair use policy for a Genesys Cloud EX organisation allocates 75,000 API requests per named user licence per month, so the synchronisation design has a documented API budget to respect?
Sources for these facts
  1. About Genesys Cloud EX
  2. Synchronization of external platform data
  3. Genesys Cloud EX configuration management
  4. Understand your Genesys Cloud EX subscription
  5. Release notes: June 28, 2023
  6. EX Engage Connector Recording Provider (EXRP)
  7. Recording injection (EX integration guide)
  8. About call recording
  9. Protect recordings from deletion

Innov8r: how QVCCS tests Genesys Cloud CX numbers, IVRs and DTMF from the caller's side

  • Did you know that the Genesys Cloud Platform API still calls call routes "IVR configs"? Each one returned by /api/v2/architect/ivrs carries its phone numbers and the open-hours, closed-hours and holiday flows they reach, which is exactly the list a tester needs.
  • Did you know that Genesys Cloud external trunks offer three DTMF methods: RTP Events (RFC 2833 or 4733), in-band audio, or none? When the two ends of a call disagree, an IVR menu can simply stop hearing the caller's key presses.
  • Did you know that Genesys Cloud rates the voice quality of calls with a Mean Opinion Score from 1 to 5, which you can view in its interaction views? Innov8r estimates the same kind of score live, ten times a second, while a test call is running.
Sources for these facts
  1. Call routing overview
  2. Add a call route
  3. Use the client credentials grant
  4. AWS regions for Genesys Cloud
  5. Telephony connection options overview
  6. External trunk settings
  7. About WebRTC
  8. Mean Opinion Score (MOS) overview
  9. About Genesys Virtual Agent

Journey Management and Journey Analyser: funnels for the inside of your IVR

  • Did you know Genesys Cloud keeps historical flow execution data for 10 days, and that execution data storage is disabled by default until an administrator enables it and the flows are republished?
  • Did you know that Journey Management is included with Genesys Cloud CX 4, and is an add-on for CX 1, CX 2 and CX 3 (including the Digital variants), with a 60-day trial available through AppFoundry?
  • Did you know an organisation can run up to 15 Journey Management calculation queries per day, and that saving edits to a journey deletes its previous calculations, so it must be calculated again?
  • Did you know the flow-level analytics detail events in Journey Management are Flow Start, Flow End, Flow Milestone and Flow Outcome, so steps inside a flow surface through the milestones and outcomes its author designs in?
Sources for these facts
  1. Differences between Journey Management and journey flows
  2. Journey Management overview
  3. Journey Management availability in Genesys Cloud licenses
  4. Funnel analysis in Journey Management
  5. Create a new journey visualization with Journey Management
  6. Analytics detail events in Journey Management
  7. Calculate journey events
  8. Historical execution data overview
  9. Journey flows overview

Live Call Map: every active Genesys Cloud conversation on a world map, placed with care

  • Did you know that Genesys Cloud analytics records the caller’s number as ani and the dialled number as dnis on each session, and that sessionDnis can differ from dnis – for example when the call was transferred?
  • Did you know that Genesys Cloud conversation detail jobs are built for bulk access, but the data they search may be hours to a full day behind real time? For up-to-date results, the conversation detail query is the intended endpoint.
  • Did you know that Genesys Cloud lets an application hold up to 20 notification channels, and when that limit is reached a new channel replaces the oldest one that has no active connection?
Sources for these facts
  1. Interactions view
  2. Queues Activity Detail view
  3. Conversation detail jobs – Genesys Cloud Developer Center
  4. Conversation detail queries – Genesys Cloud Developer Center
  5. Analytics APIs – Genesys Cloud Developer Center
  6. Notifications – Genesys Cloud Developer Center

One call, every layer: reconstructing a Genesys Cloud conversation end to end

  • Did you know that a Genesys Cloud conversation record is layered? A conversation holds participants, each participant holds sessions per media type, and each session is broken into segments such as ivr, alert, interact, hold and wrapup – with flow data and, for voice, call-quality stats attached to the session.
  • Did you know that historical Architect flow execution data storage is disabled by default? Once an administrator enables it, Genesys retains the step-by-step execution data for 10 days, so a flow path can only be replayed for recent calls.
  • Did you know that when an agent puts a customer on hold, the interaction timeline shows hold on the agent's row while the customer's row shows interacting? Reading a conversation means reading each participant's own segments.
  • Did you know that Genesys documents a 60-day time to live for participant data in the interaction details view? After that, the attributes your flows set can only be accessed when exported.
Sources for these facts
  1. Conversation Data Model – Genesys Cloud Developer Center
  2. View an interaction's details – Genesys Cloud Resource Center
  3. View an interaction's timeline – Genesys Cloud Resource Center
  4. View participant data attributes – Genesys Cloud Resource Center
  5. Historical execution data overview – Genesys Cloud Resource Center
  6. Interactions view – Genesys Cloud Resource Center
  • Did you know participant data attributes are name and value strings that persist when a call transfers from one Architect flow to another, while ordinary flow variables, such as the caller's number in Call.Ani, do not?
  • Did you know Genesys documents that participant data set after the customer disconnects, for example by an agent script during wrap-up, is synchronised in Conversation Services but not in Analytics Services?
  • Did you know analytics conversation detail jobs return participant attributes, with keys and values truncated to 1,024 characters, while the response schema of the synchronous conversation details query leaves attributes out?
  • Did you know Genesys gives participant data shown in an interaction's details a time to live of 60 days, after which it can only be accessed when exported?
Sources for these facts
  1. View participant data attributes
  2. Set Participant Data action
  3. Export view data
  4. Interactions view
  5. Conversation detail record jobs
  6. Conversation detail queries
  7. Analytics API explorer

SIP Trace Analyser: from “why did this call fail?” to the trunk and the response code

  • Did you know that Genesys Cloud analytics segments can carry sipResponseCodes alongside a disconnectType such as error, system or transportFailure – so some SIP failures are visible in the conversation detail record before you download a single trace?
  • Did you know that the Genesys Cloud analytics session record carries an edgeId and a provider, but no trunk field? Working out which trunk carried a call means looking at the SIP signalling itself.
  • Did you know that Genesys Cloud generates PCAP files for calls that traverse an external trunk, keeps them available for 21 days, and does not generate them for station-to-station calls? PCAP generation is best-effort and always gives way to call handling.
Sources for these facts
  1. SIP Diagnostics
  2. View an interaction’s Details tab
  3. Telephony APIs – Genesys Cloud Developer Center
  4. Conversation detail queries – Genesys Cloud Developer Center
  5. Analytics APIs – Genesys Cloud Developer Center
  6. Get trunk status information

Salesforce data actions for Genesys Cloud CX: caller lookup, verification and screen pop

  • Did you know Salesforce stores an 11-digit number entered with a leading 1 as a 10-digit number, while the Salesforce data actions integration searches for exactly the number passed in the PHONE_NUMBER input, so Call.Ani must match how Salesforce holds it?
  • Did you know a data action in an Architect call flow times out after 60 seconds by default, which administrators can set anywhere from 1 to 60 seconds, while data actions run from Scripter or the Public API time out after 20 seconds?
  • Did you know Salesforce will retire Open CTI on 28 February 2028, and Genesys has announced that the Genesys Cloud for Salesforce Open CTI integration will retire at the same time?
  • Did you know that moving a Salesforce data actions integration from the deprecated username-password credential type to the OAuth Client Credential Flow type needs no change to the actions' request or response configuration?
Sources for these facts
  1. Deprecation: Salesforce open CTI integration
  2. About Genesys Cloud for Salesforce
  3. About CX Cloud from Genesys and Salesforce
  4. Screen pop in CX Cloud from Genesys and Salesforce
  5. About the Salesforce data actions integration
  6. Response configuration for data actions
  7. Phone number searches with the data action integration
  8. How many seconds before a data action times out?
  9. Salesforce OAuth Client Credentials Flow migration guide
  10. Work with secure call and bot flows

Trunk Monitor: sub-second SIP trunk health for Genesys Cloud, with the evidence

  • Did you know that the Genesys Cloud trunk metrics endpoint, GET /api/v2/telephony/providers/edges/trunks/metrics, takes its trunk IDs as one comma-separated list and returns inbound and outbound call counts per trunk, plus a QoS mismatch count?
  • Did you know that Genesys Cloud reports a trunk as “Working partially” when not all Edge interfaces are operational, or when some of its SIP servers or proxies are not available for calls – a state between fully up and fully down?
  • Did you know that on the Genesys Cloud Telephony Metrics dashboard, trunk QoS mismatches are measured over a 24-hour sliding window, while trunk call counts show the current number of calls passing through the trunk?
Sources for these facts
  1. Get trunk status information
  2. Trunk status indicators
  3. View telephony metrics
  4. Troubleshoot using the Genesys Cloud Operational Console
  5. Telephony APIs – Genesys Cloud Developer Center
  6. Notifications – Genesys Cloud Developer Center

What callers actually said: bot journeys, turn-by-turn replay and the no-match backlog

  • Did you know the Utterance History view and Bot Conversation Library in the Genesys Optimization dashboard retain only the last 10 days of data, whatever date range the dashboard is set to?
  • Did you know the Genesys Platform API documents bot flow sessions and reporting turns as deleted after approximately, but not before, 10 days, so turn-level history must be collected if you want to keep it?
  • Did you know the Optimization dashboard shows metrics for core bot flows only, not for subflows that the core bot flow invokes?
  • Did you know the Bot Performance Detail view in Analytics Workspace accepts custom date ranges of up to 6 weeks for its aggregate bot metrics?
Sources for these facts
  1. View bot and digital bot metrics in the Optimization dashboard
  2. Insights and Optimizations menu overview
  3. Bot Performance Detail view
  4. Analytics API explorer (bot flow sessions and reporting turns)

What is really in your knowledge bases? A point-in-time Genesys Cloud knowledge inventory

  • Did you know that a Genesys Cloud knowledge article can carry touchpoint variations, so the same answer is tailored for Agent Assist, bot flows, the knowledge portal and the Knowledge app for Messenger? One article can therefore hold several versions of its content.
  • Did you know that when you import or export knowledge articles, the externalID attributes and the category and label structure are only available in JSON format? CSV and XLSX suit basic FAQs and spreadsheets.
  • Did you know that every knowledge article has a draft side and a published side, each with its own set of content variations? Reviewing only what is live misses what is about to go live.
Sources for these facts
  1. About the knowledge workbench V2 – Genesys Cloud Resource Center
  2. Import or export articles in a knowledge base V2 – Genesys Cloud Resource Center
  3. Limits – Genesys Cloud Developer Center

Where does every number go? Auditing Genesys Cloud DIDs, flows and caller IDs

  • Did you know that, in the Genesys Cloud Platform API, call routes are served as IVR configurations at /api/v2/architect/ivrs, with their phone numbers in a dnis list – and that reading them needs the Routing > Call Route > View permission?
  • Did you know a single Genesys Cloud call route can hold up to 4,500 phone numbers, but Genesys notes that the more numbers a route holds, the slower the Edge is to process them?
  • Did you know a DID record’s ownerType in the API can be USER, PHONE, IVR_CONFIG or GROUP – so a number in your DID ranges may belong to a person or a handset rather than to any call flow at all?
Sources for these facts
  1. Call routing overview – Genesys Cloud Resource Center
  2. Add a call route – Genesys Cloud Resource Center
  3. Manage DID and toll-free number assignments
  4. Manage DID and toll-free number ranges
  5. Architect APIs – Genesys Cloud Developer Center
  6. Telephony APIs – Genesys Cloud Developer Center
  7. Outbound APIs – Genesys Cloud Developer Center

Which permission put this user on CX 2? Licence attribution, traced to the role

  • Did you know Genesys Cloud enables automatic licence assignment by default, and that each role has an associated licence reflecting the level of permissions it grants, so assigning a role also assigns its licence?
  • Did you know the licence a Genesys Cloud role uses corresponds to the highest-tier permission assigned to it, so a single permission can decide the tier of every user who holds that role?
  • Did you know Genesys deprecated the 'including any future permissions' logic of All Permissions, effective 1 June 2026, noting it could cause unintended billing impacts when new permissions require higher licence tiers?
  • Did you know that under the concurrent licensing model, Genesys charges reflect the highest licence level users were assigned during the billing period, so the licence a user's permissions require and the licence they are billed for can differ?
Sources for these facts
  1. Manage licenses
  2. Assign roles, divisions, licenses, and add-ons
  3. Roles and permissions overview
  4. Edit a role
  5. Deprecation: Changes to logic in All Permissions
  6. What defines a billable concurrent user for Genesys Cloud contact center services?

Zendesk data actions in Genesys Cloud CX: tickets in the IVR and the screen pop

  • Did you know Zendesk documents that it can take up to a few minutes for new tickets, users and other resources to be indexed for search, so a ticket created moments ago may not yet appear in Search API results?
  • Did you know that when you add and activate the Zendesk data actions integration, Genesys Cloud automatically creates static actions such as Get User By Phone Number and Get Most Recent Ticket By User Id, which you can copy as templates for custom actions?
  • Did you know a data action in an Architect call flow times out after 60 seconds by default, which administrators can now set anywhere from 1 to 60 seconds, while data actions run from Scripter or the Public API time out after 20 seconds?
  • Did you know the output contract of a Genesys Cloud custom action does not support nested arrays, and a resolved response that does not conform to the action's success schema causes an error?
Sources for these facts
  1. About the Zendesk data actions integration
  2. Announcing the removal of API tokens as an authentication method for API requests – Zendesk help
  3. Genesys Cloud release notes, 9 November 2026 (Zendesk data actions OAuth client credentials grant support)
  4. Add contracts to custom actions for integrations
  5. Request configuration for data actions
  6. Response configuration for data actions
  7. How many seconds before a data action times out?
  8. Administrator requirements for the Genesys Cloud embedded clients
  9. Zendesk Search API reference
  10. Zendesk Tickets API reference (List User Requested Tickets)

Last reviewed

Questions about what you have read?

Clients, partners and people introduced to us can reach the specialists behind our applications and articles directly.

Who to contact