Innovation reference
Native Genesys Cloud CX and the QVCCS App Suite, side by side
Every comparison table from our Innovation articles in one place: what Genesys Cloud CX does natively, objectively, and where a QVCCS application adds depth. Each table links to its article and its sources.
Native configuration views, CX as Code export and Config Validator
| Aspect | Native Genesys Cloud CX | QVCCS Config Validator |
|---|---|---|
| Where users are reviewed | People page with name, status, licence, last login, roles, email and division columns, plus filter and search. | One 13-column row per user joining identity, roles, telephony, queues and groups, with eight combinable filters. |
| Phones and stations | Configured and reviewed on their own admin pages, per object. | User to station to phone resolved through three paths, with allocated and default-station badges per user. |
| Queue and group membership | Visible per queue and per group in their admin views. | Every user's queues and groups as pills and filters; member lists fetched with timeouts and pacing. |
| Configuration as code | CX as Code genesyscloud_tf_export writes existing resources to a Terraform JSON configuration file. | Not a configuration-as-code tool; a joined, human-readable evidence report that complements a CX as Code export. |
| Runtime phone status | Reviewed phone by phone in telephony administration. | Edge-reported operational status preferred, administrative state as fallback, grouped into filterable buckets. |
| Deactivated accounts | People page filter shows active, inactive or deleted members. | All user states fetched on purpose, so lingering roles, queues and groups on deactivated accounts are visible. |
| Evidence output | Bulk import file format for adding and updating people. | CSV, XLSX and landscape PDF of exactly the filtered rows, generated in the browser. |
Config Validator is read-only: it never changes configuration, and fixes are made in Genesys Cloud or through CX as Code.
Anonymous and authenticated web messaging in Genesys Cloud CX
| Aspect | Anonymous Messenger session | Authenticated Messenger session |
|---|---|---|
| Who can start a conversation | Any website visitor. | Only customers who have signed in through your OpenID Connect identity provider; step-up lets them sign in mid-conversation. |
| Identity on the conversation | Whatever the customer types, to be verified by the agent or a bot. | Verified claims: sub, name from given_name and family_name, email, and phone_number when requested. |
| Architect | Message.IsAuthenticated is false. | Message.IsAuthenticated is true, and senderAddressInfo carries the identifier, name and email. |
| Continuity | The session lives in the visitor's browser for the guest session duration. | Customers can resume existing conversations in any browser where they sign in. |
| Identity stitching | Contacts are stitched by cookie ID only. | With identity resolution and an external source, contacts are stitched by external ID and appear in the customer journey. |
| Set-up | Messenger configuration and deployment, plus an inbound message flow. | Also an identity provider client, the OpenID Connect Messenger Configuration integration and an AuthProvider plugin on your pages. |
Licence requirements for authenticated web messaging are listed on Genesys's Enable authenticated web messaging page.
Sources
- Authenticated web messaging overview
- Enable authenticated web messaging
- Get started with authenticated web messaging
- Authenticated web messaging attributes
- Authenticated web messaging quick start guide
- Authenticated web messaging (Developer Center)
- Identity stitching and journey support coming to authenticated web messaging
- Release notes: November 3, 2025
- Guest session duration for web messaging
- Deprecation: Removal of ACD Web Chat (version 2)
Queue-level and agent-level auto answer
| Aspect | Queue level | Agent level |
|---|---|---|
| Where it is set | On the queue: the General tab for the whole queue, then each channel's settings. | In the user's profile under Admin, People: the Auto Answer section. |
| Scope | All agents and groups currently members of the queue. | One user, across all their queues. |
| Channels | All supported voice and digital channels, with per-channel overrides. | All channels selected by default when switched on; can be narrowed. |
| Combination | No hierarchy: enabled at either level means the interaction is auto answered. | No hierarchy: enabled at either level means the interaction is auto answered. |
| Watch out for | Changing the queue-level setting clears channel-level overrides. | For voice, the agent's phone must support auto answer. |
| Public API | enableAutoAnswer in the queue's mediaSettings, per media type and message subtype. | /api/v2/users/agentui/agents/autoanswer/{agentId}/settings |
Sources
- Auto answer incoming interactions
- Turn on auto answer for agents
- Work with auto answer enabled interactions
- Set behavior and thresholds for voice and chat channels
- Agent utilization
- Improved auto-answer configuration and toast message control
- Digital reporting revision for auto answer
- Deprecation: Removal of ACD Web Chat (version 2)
Conditional group routing and Conditional Group Activation side by side
| Aspect | Conditional group routing (CGR) | Conditional Group Activation (CGA) |
|---|---|---|
| What it is | A routing method selected on the queue. | A gatekeeper that works alongside the queue's routing method. |
| When it evaluates | When each interaction arrives, then rule by rule as wait periods expire; conclusions also apply to interactions already waiting. | Periodically, for example every 30 seconds, for the queue as a whole. |
| First check | Rule 1 always tests the current queue; if it is not met, no further rules are evaluated. | An optional pilot rule tests the current queue; if it is not met, groups in the numbered rules are deactivated. |
| Rules and conditions | Up to five rules, each with one EWT condition and a wait period. | Up to five rules, each with up to ten conditions; no per-interaction wait period. |
| KPIs | Estimated wait time. | Estimated wait time and idle agents. |
| Routing methods | Is the routing method, and can be the timeout method for preferred agent routing; no last agent routing. | Works with standard, bullseye, preferred agent and predictive routing; ignored by direct and last agent routing. |
| Groups | General groups, skill expression groups and work teams that are members of the queue; queues in the same division. | Groups that are members of the queue; queues in the same division. |
| Outlook | Still supported, but Genesys plans no further enhancements and recommends migrating to CGA. | The target Genesys recommends for CGR rules. Never configured on the same queue as CGR. |
Workitems: Genesys documents that CGR does not support workitem routing.
Sources
Web messaging in a mobile browser and a native app on the Transport SDK
| Aspect | Messenger in a mobile browser | Native app on the Messenger Transport SDK |
|---|---|---|
| Interface | Genesys's ready-made Messenger window, configured and styled in Genesys Cloud | The organisation's own screens, built around the conversation |
| Sign-in | Anonymous, or authenticated through the website's own sign-in with OpenID Connect | Authenticated once in the app, here with an SMS code, and reused for every conversation |
| History across devices | Authenticated customers resume conversations in any browser where they sign in | The same thread follows the identity across launches, days and devices |
| Rich media | Attachments within the deployment's supported content profile | Camera and library photos, a one-tap precise location with what3words, and live video |
| Context for the agent | Whatever the web page passes as custom attributes | Device, battery, network, language, accessibility and permissions, with trusted facts kept apart from reported ones |
| Notifications | Visible while the page is open | Push notifications documented by Genesys for the SDK, through Apple's and Google's push services |
Sources
- Messenger Transport Mobile SDK overview – Genesys Cloud Developer Center
- Authenticated session (Messenger Transport Mobile SDK) – Genesys Cloud Developer Center
- Generic file attachment (Messenger Transport Mobile SDK) – Genesys Cloud Developer Center
- Mobile Messenger feature comparison matrix – Genesys Cloud Resource Center
- Mobile apps for iOS and Android – Genesys Cloud Resource Center
- Deploy Messenger – Genesys Cloud Resource Center
- Authenticated web messaging attributes – Genesys Cloud Resource Center
- Agentless SMS notifications – Genesys Cloud Resource Center
- Manage script properties – Genesys Cloud Resource Center
- Configure mobile push notifications – Genesys Cloud Resource Center
Native Genesys Cloud CX views and CX Pulse
| Aspect | Native Genesys Cloud CX | QVCCS CX Pulse |
|---|---|---|
| Real-time agent status | Agents Status Summary and Detail views show statuses in real time for current date ranges, with Duration, Timeline and Log In – Log Out displays. | A wallboard with one dot per agent, re-clustered on every pushed presence or routing-status event. |
| Dashboards | Performance dashboards with Metric, Chart, Web Content and Agent Status widgets, refreshed in near real time. | A fixed wallboard layout: 270° gauge, nine KPI tiles, group and queue cards and a live transition ticker. |
| Organisation (secondary) statuses | Shown to administrators in views such as Agents Status Summary and Queues Activity Detail. | Resolved through a cached presence-definitions set, so each custom label appears in the tooltip and rolls up under its primary. |
| Not Responding | A system-set routing status applied when an agent does not answer within the queue’s timeout. | Counted as its own Ineligible tile, separate from On Queue. |
| Long-held states | Time in each status by interval in the Agents Status Detail view. | A 15-minute stale ring on cards and a 61-minute Overdue tile for likely “forgot to log off” cases. |
| Agent control | Supervisors with the required permissions can change an agent’s status or log them off. | Read-only by construction; it never changes an agent’s state. |
| History and export | Historical date ranges, saved views and export. | No history or export by design; nothing is persisted. |
Native capabilities are as described in the Genesys Cloud Resource Center at the time of writing; what each user sees depends on their permissions.
Native export paths and Conversation Detail
| Aspect | Native Genesys Cloud CX | QVCCS Conversation Detail |
|---|---|---|
| Synchronous detail query | Up to 7 days unfiltered or 32 days filtered per query, start dates up to 558 days back; not intended for bulk export. | Used only for a one-record totalHits probe that drives the progress bar. |
| Asynchronous detail jobs | Recommended for historical queries; cursor paging up to 10,000 per page; data can lag real time by hours to a day. | Ranges split into seven-day windows, one job each, polled, cursor-paged and de-duplicated across windows. |
| Interactions view export | CSV or PDF, on demand or scheduled; custom ranges up to 31 days; up to 1,000,000 older conversations per export. | One run over an arbitrary range, up to 250,000 records per collection, with JSON and Excel downloads. |
| Participant attributes | Exportable from views with the Custom Participant Attributes permission; job results carry attributes, truncated to 1,024 characters. | Fetched per conversation from the live object, kept per participant, merged per conversation, junk keys filtered, one column per key. |
| IVR variables and DTMF | Historical flow execution data in Architect, with flow execution history and Replay Mode, retained for 10 days. | Optional extraction of every flow variable and each input's attempt trail into columns, cached beyond the 10-day window. |
| Rate limits | Services answer with 429 and Retry-After; clients are expected to back off. | Adaptive per-session pacer, Retry-After honoured with jitter, proactive token refresh. |
| Output shape | Tabular view columns chosen in the view. | Flat single-sheet workbook plus the complete nested JSON and a meta summary. |
Limits quoted for native features are from current Genesys documentation and may change; check the linked articles.
Sources
- Analytics Conversation Detail Endpoint API query interval change – Genesys Cloud Resource Center
- Conversation detail record jobs – Genesys Cloud Developer Center
- Conversation detail queries – Genesys Cloud Developer Center
- Conversation Data Model – Genesys Cloud Developer Center
- Export view data – Genesys Cloud Resource Center
- Interactions view – Genesys Cloud Resource Center
- Historical execution data overview – Genesys Cloud Resource Center
- Limits – Genesys Cloud Developer Center
Native controls and the QVCCS PII/PCI Finder
| Aspect | Native Genesys Cloud CX | QVCCS PII/PCI Finder |
|---|---|---|
| Preventing capture | Secure Pause and Secure Call Flows, validated by a QSA as Level 1 PCI DSS compliant. | Does not prevent capture; audits transcripts afterwards and never replaces these controls. |
| Redaction | Best-effort STA redaction of payment card and personal information entities into bracketed placeholders, when analytics is enabled. | Recognises those placeholders, counts them, and flags detector matches found outside them. |
| Searching transcripts | Keyword search within a transcript in the interaction view. | Scans every phrase of every harvested conversation in a date range and lists only those with findings. |
| Card detection | Card number, expiry and CVV entities detected by STA. | 12–19 digits, Luhn checksum, real issuer range and length, context scoring, spoken-digit reconstruction. |
| Who sees unredacted data | Users with View Sensitive Data, which no role includes by default. | Recommends an OAuth client without it, so findings are true exposure gaps. |
| Coverage gaps | Redaction applies only where speech or text analytics is enabled; national IDs for Australia, Canada, the UK and the US. | Conversations with no transcript are tallied as an unscannable blind spot; an honest-zero banner explains empty results. No detectors for UK National Insurance numbers, sort codes or bank account numbers. |
| Licensing | Automatic redaction lists Genesys Cloud CX licence options plus the Speech and Text Analytics Upgrade Add-On. | Reads STA transcripts, so it relies on STA being in place. |
Native behaviour is as described in the Genesys Cloud Resource Center at the time of writing. The QVCCS app is an audit aid; it is not a PCI DSS control.
Architect execution history and replay, and QVCCS Flow Journey
| Aspect | Native Genesys Cloud CX | QVCCS Flow Journey |
|---|---|---|
| Starting point | Open a flow's Execution History, or search the Query Builder by one criterion such as conversation ID. | Paste a conversation ID; every flow instance it produced is found automatically. |
| What one view covers | One flow instance, replayed in that flow's editor in read-only mode. | Every instance of the conversation, inbound, bot and in-queue, in execution order on one page. |
| Navigation | Step in, over and out, breakpoints, a timeline and keyboard shortcuts. | A numbered written analysis and a lane diagram, with filters for decisions and input only. |
| Caller detail | Execution items highlighted on the flow design, with values captured at the configured data level. | Prompt wording played, digit pressed with think-time, lookup inputs and results, transfer targets. |
| Verdict | Error and warning codes on the instance, searchable in the Query Builder. | Four tones per step, rolled up per flow, and a journey outcome such as Completed in IVR. |
| Sharing | Within Architect, for users with Flow Instance View and Search permissions. | Copy as text for tickets and post-mortems; raw step JSON in the inspector. |
| Data held | Genesys stores execution data for 10 days. | Nothing stored; every lookup is a fresh fetch within Genesys's retention. |
Replay Mode remains the flow author's tool for debugging a design in Architect; Flow Journey is built for answering what happened on one call.
Architect's native views and QVCCS Flow Mapper
| Aspect | Native Genesys Cloud CX | QVCCS Flow Mapper |
|---|---|---|
| Seeing a flow | The Architect editor for the flow you open, with its resources under the Dependencies pane. | An interactive diagram of any flow with the happy path pinned, prompt wording, queue targets and data action contracts inline. |
| Where a resource is used | Dependency Search lists checked-in and published flows containing a named resource; Find consuming flows for modules, bots, in-queue and secure flows. | Inventory pages for prompts, data tables, data actions, integrations and queues, plus deep links from every audit finding. |
| References that resolve to nothing | Dependency Search works from resources that exist and can be named. | Tier 1 audit: broken references, case mismatches and typo suggestions across every flow. |
| Data tables | Data tables appear as a dependency type in Dependency Search. | Tier 2 audit: every cell checked against queue, data action, prompt and flow names. |
| Naming drift | Variables and participant data are defined flow by flow in the editor. | Tier 3 audit: attribute and variable names that differ by case or one or two edits, clustered across all flows. |
| Walking a path | Replay Mode plays back recorded flow executions, where execution data is stored. | The Walker steps through the design itself, building a caller-facing transcript, with no call needed. |
| As-built record | Configuration is viewed flow by flow in Architect, or retrieved through the Platform API. | A Word document with scope presets, redaction, a configuration-health appendix and embedded diagrams. |
Flow Mapper reads the most recent published build of each flow, or the latest checked-in or saved configuration for a never-published flow; it never sees an in-progress editor state.
Understanding a flow in native Architect and in QVCCS Flow Narrator
| Aspect | Native Genesys Cloud CX | QVCCS Flow Narrator |
|---|---|---|
| Exporting a flow | Export flow from the Save menu, in Architect's configuration format or YAML, optionally with tracking IDs. | Word and PDF narrative of the chosen version, with every step's tracking id and a block index. |
| Intended reader | Flow engineers working in Architect or in YAML with Archy. | Executive summaries for managers and owners, followed by full detail for engineers. |
| Scope | One flow per export; Find consuming flows shows callers of a module or bot. | The starting flow plus every bot, module, transfer flow, in-queue flow and post-call workflow it reaches. |
| Dependencies | Dependencies pane per flow; Dependency Search across published and checked-in flows. | Inventory of every referenced resource with every block that uses it and where each flow is reached from. |
| Conditions | Expressions in Architect's expression language. | Translated to plain English from the parsed tree; anything untranslatable is quoted and counted. |
| Changing flows | Architect UI and Archy create, update and publish flows. | Read-only: every call is a GET, and nothing is written to Genesys. |
Flow Narrator complements Architect, export and Archy; it explains configuration and never changes it.
The native IP range sources and the QVCCS IP Ranges app
| Aspect | Native Genesys Cloud CX | QVCCS IP Ranges |
|---|---|---|
| Source of truth | GET /api/v2/ipranges for outbound service ranges, plus the firewall allowlist article for media and AWS guidance. | Calls the same API live, one call per load or refresh. |
| Filtering | The endpoint takes no parameters; each entry is tagged with service, region and direction. | Region dropdown, multi-select purpose chips with counts, direction control and free-text search, all stackable. |
| Ordering | A JSON entities array. | Numeric CIDR sort by address then prefix, IPv6 after IPv4; every column sortable. |
| Sizing the change | Ranges expressed in CIDR notation. | Derived Addresses column and live totals of ranges, purposes, IPv4 addresses and regions. |
| Evidence | Raw JSON response. | CSV, themed Excel and JSON of exactly the filtered view, with the region in the file name and a fetch timestamp. |
| Access | Requires an OAuth token; no specific permission is listed in the API definition. | Any client-credentials client in the org; strictly read-only. |
| Media and AWS ranges | Genesys-owned media CIDRs and AWS guidance are published in the firewall allowlist article. | Shows what the API returns; we cross-check the article for media and AWS rules. |
| Keeping current | Changes to data action and SMTP addresses are announced under Features coming soon where possible. | Refresh before every ticket; the timestamp travels with the export. |
Native behaviour is as described in the Genesys Cloud Resource Center and the Platform API definition at the time of writing.
Sources
Conversations and workitems in Genesys Cloud CX
| Aspect | Conversations (voice, messaging, email) | Workitems (Work Automation) |
|---|---|---|
| What it is | A customer interaction on a media channel. | A non-conversational unit of work, such as a claim, a request or a case step. |
| Where it lives | On the conversation, with its participants, while it is handled. | Always in exactly one workbin, typed by one worktype, until its life span ends. |
| Tracking progress | Conversation and participant states as the interaction is routed and handled. | A business status in the Open, In progress, Waiting or Closed category, plus a separate assignment state. |
| Routing methods | Standard, bullseye, preferred agent, conditional group and predictive routing, depending on media. | Standard, bullseye and preferred agent routing, or direct assignment through the API; not conditional group or predictive routing. |
| Automation | Architect flows for the channel, such as inbound call, message and email flows. | Worktype rules with an Architect workitem flow, and Process Automation triggers that launch Architect workflows. |
| Time and SLA | Service level and wait times measured in queue. | Due date, expiration date and life span on every workitem; up to 60 days queued before AcdExpired. |
| Reporting | Queue and agent performance views. | Queue and Agent Workitems Performance views; Genesys recommends dedicated queues for workitems. |
Workitems and conversations have no direct relationship today; Genesys suggests writing conversation IDs into workitem attributes.
Sources
- Work automation overview
- Define a worktype
- Create custom attributes for work automation
- Create a workbin
- Work with workitem flows
- Task Management (Developer Center)
- Workitem assignment (Developer Center)
- Can I blend workitems into a queue with other media types?
- What are the billing rules for the work automation add-on?
- Work Automation introduces a consumption-based pricing model
Ways to offer a callback in Genesys Cloud CX
| Aspect | Native Genesys Cloud CX options | Website form through the Platform API |
|---|---|---|
| Where the request starts | In a call: Architect's Create Callback action in inbound, in-queue or outbound call flows, or an agent scheduling a callback during a voice interaction. | On your website, from a customer who is not on a call, through POST /api/v2/conversations/callbacks. |
| Scheduled time | Architect does not let callers schedule a specific date or time; agents can schedule within the window an administrator allows. | The customer chooses; callbackScheduledTime carries it, within the window your business rules allow. |
| Number to call | The caller's ANI, or a number collected in the flow; agents can edit the number when scheduling. | The number the customer enters, validated as E.164 on your server. |
| Context for the agent | Callback script inputs set in the flow; attributes already on the conversation. | callbackUserName, an optional scriptId and data key-value pairs that appear as participant attributes. |
| Security responsibility | Handled within Genesys Cloud. | Yours: OAuth client secret custody, least-privilege role, CORS, validation, rate limiting and bot protection. |
| Build effort | Configuration in Architect and scripts. | A small server application to design, test, host and support, plus configuration. |
The approaches combine: many organisations offer in-queue callbacks to callers and a scheduled callback form to website visitors, both landing on the same queues.
Sources
- Schedule callbacks from a website
- Create Callback action
- Schedule a callback
- Callbacks overview
- Create an OAuth client
- OAuth client secret no longer visible after creation
- Restrict OAuth client credentials grants to allowed IP addresses
- Client credentials grant (Developer Center)
- Platform API regions and hosts (Developer Center)
Journey flows in Architect and QVCCS IVR Sankey
| Aspect | Native Genesys Cloud CX | QVCCS IVR Sankey |
|---|---|---|
| Scope | A single Architect flow; cannot visualise journeys across multiple flows. | One flow's calls, followed across the flows, bots and transfers each conversation passed through to the queue outcome. |
| Time range | Up to seven days, a fixed 168-hour period, recalculated overnight. | Any harvested window, up to 31 days per run; the warehouse accumulates for longer baselines. |
| Counts | Directional, not intended to be exact; busy flows may be limited to the most frequent paths. | Every call in the window from conversation detail records; low-volume edges pruned only for readability, with connectivity preserved. |
| Nodes | Flow milestones and flow outcomes, with terminal nodes for how journeys ended. | Flows, bots, transfers and queue outcome, plus menus, data actions, prompts and outcome attainment. |
| Filtering | By exit reason, for example Abandoned. | Split or filter by any participant-data attribute; splits stack. |
| Explaining hang-ups | Filter to abandoned paths and see which nodes they passed. | Disconnect breakdown: in-IVR versus in-queue, last prompt heard and last lookup result. |
| Outputs | Interactive view inside Architect. | Shareable deep links, diagram PDF, KPI summary PDF and ranked Insights. |
Journey flows remain the quickest first look inside Architect, and Journey Management covers cross-channel journeys.
What Genesys Cloud EX synchronises from an external platform
| Aspect | Genesys Cloud EX support | What it means for the design |
|---|---|---|
| Configuration | Users and person information, ACD skills and languages, divisions, queues, wrap-up codes and secondary statuses, by initial and ongoing sync. | Synchronise these before any interaction or recording, and keep deletions manual, as Genesys recommends. |
| Agent state | Presence and routing status, with the external platform as the source of truth; one presence source per organisation. | Choose one authoritative source, and test adherence views against it. |
| Interactions | Voice and email interactions, each with an external source platform. | Agree how calls, segments and transfers map to conversations and participants. |
| Recordings | Voice interaction recordings only; no screen recordings or digital interaction recordings. | Plan other media separately; do not promise evaluations of screens or chats. |
| Analytics | Speech and text analytics is an EX capability; analysis needs higher-quality audio than archive-only recordings. | Sample-test transcription on legacy audio before committing to analytics at scale. |
| Monitoring | Upload status reports by date and status: Pending, Success, Failure, WaitForConversation. | Reconcile daily against the recorder's own inventory. |
Sources
- About Genesys Cloud EX
- Synchronization of external platform data
- Genesys Cloud EX configuration management
- Understand your Genesys Cloud EX subscription
- Release notes: June 28, 2023
- EX Engage Connector Recording Provider (EXRP)
- Recording injection (EX integration guide)
- About call recording
- Protect recordings from deletion
The agent's side and the caller's side
| Aspect | Inside the org: Genesys Cloud WebRTC phone | Caller's side: QVCCS Innov8r |
|---|---|---|
| Whose experience it proves | The person answering: a Genesys Cloud user or agent working in the browser | The person calling: a customer dialling the public number from outside |
| Where the call starts | Within Genesys Cloud, on the user's WebRTC phone | On a PBX outside the org, through a carrier trunk and the public telephone network |
| Numbers and flows | Configured as call routes in Genesys Cloud, each with its schedule and flows | Read from those call routes and listed beside their flows, ready to dial |
| Key presses | Each external trunk sets its DTMF method: RTP Events (RFC 2833 or 4733), in-band audio or none | Sent as RFC 4733 telephone events, with SIP INFO as a fallback, so menus are tested the way handsets press keys |
| Voice quality | A Mean Opinion Score from 1 to 5 for calls, shown in the interaction views | MOS, R-factor, jitter and loss estimated live during the call, ten times a second |
| Who can use it | Every Genesys Cloud user with a WebRTC phone | QVCCS engineers only |
The Genesys Cloud WebRTC phone is a full agent phone; this table compares only the viewpoint each one tests from.
Genesys Journey Management and QVCCS Journey Analyser
| Aspect | Native Genesys Cloud CX | QVCCS Journey Analyser |
|---|---|---|
| Availability | Journey Management is included with Genesys Cloud CX 4; an add-on for CX 1, CX 2 and CX 3, including Digital variants. | Part of the QVCCS App Suite, included with every QVCCS Managed Professional Services tier; signs in with a read-only OAuth client. |
| Where events come from | Genesys Event Data Platform: analytics detail, virtual agent, knowledge, web, survey and external events. | Architect flow execution traces plus each conversation's analytics record for queue, agent and wrap-up. |
| Who is counted | Unique customers, stitched across channels by a single customer view. | Unique conversations; no identity across calls or channels. |
| Steps inside a flow | Flow Start, Flow End, Flow Milestone and Flow Outcome events. | Twenty event types, including prompt played, menu choice, collect input, data action result, decision or switch case and bot verdict. |
| Getting the numbers | Save and Calculate; calculations take minutes; up to 15 queries per organisation per day. | Recalculated live on every edit; no Calculate step. |
| History | Up to 90 days at activation, rolling to as much as 400 days. | Accumulates from the day a flow is watched; Genesys keeps execution data for 10 days, so harvesting is scheduled daily. |
| Following one caller | Charts, trends and funnel conversion on the journey. | Callers list on every card, linking to a transcript and a step-by-step replay of the trace. |
| Beyond the IVR | Web, survey, knowledge and external events across channels. | None: voice flow execution and the queue and agent record only. |
Journey Analyser is designed to complement Journey Management, not replace it. Use Journey Management for cross-channel customer journeys.
Sources
- Differences between Journey Management and journey flows
- Journey Management overview
- Journey Management availability in Genesys Cloud licenses
- Funnel analysis in Journey Management
- Create a new journey visualization with Journey Management
- Analytics detail events in Journey Management
- Calculate journey events
- Historical execution data overview
- Journey flows overview
Native views and Live Call Map
| Aspect | Native Genesys Cloud CX | QVCCS Live Call Map |
|---|---|---|
| Live conversations | The Interactions view lists conversations, filterable by ANI, DNIS, direction, waiting and interacting states and more. | Every active conversation as a clustered marker on a world map, coloured by media type and state. |
| Caller location | ANI and DNIS are recorded and filterable as conversation fields. | A position derived from ANI or DNIS with a stated confidence tier; withheld numbers and emails listed as Unknown. |
| Queue operations | Queues Activity Detail shows waiting and interacting conversations, agent statuses, service level and manual assignment. | A read-only Queue Health board of agents, idle agents and waiting conversations, next to the map. |
| Call quality | The Interactions view can filter by MOS range, above or below a value. | Live toasts when MOS falls below 3.5 or 3.0, or RTP latency exceeds 200 or 400 ms. |
| History | Interactions view date ranges of up to 31 days. | Replay of up to 2,000 past conversations and a heatmap of up to 30 days. |
| Changes to your org | Supervisors can act on interactions and agents, subject to permissions. | Strictly read-only; it only manages its own notification subscriptions. |
Native capabilities are as described in the Genesys Cloud Resource Center at the time of writing. Map positions are approximate and derived from telephone numbers only.
Native interaction details and Conversation Analyser, side by side
| Aspect | Native Genesys Cloud CX | QVCCS Conversation Analyser |
|---|---|---|
| Where you look | Interaction details page: overview plus tabs for details, timeline, quality summary, transcripts, audit trail and customer journeys. | One report page per conversation ID, with deep links for tickets and a complete JSON download. |
| Timeline | Timeline tab with a segment per part of the interaction; click a segment for its duration, drag and zoom. | Swim-lane of every participant's segments on a shared clock, plus a plain-English narrative with offsets and a disconnect summary. |
| Participant data | Participant Data section on the Details tab; Genesys documents a 60-day time to live, after which data is available via export. | Participant data card per participant from the live conversation object, alongside the analytics cards and in the raw JSON. |
| Flow path | Architect flow execution history and Replay Mode, when historical execution data storage is enabled. | Flow replay embedded in the conversation report, every flow instance in execution order, with the branch taken on each connector. |
| Prompts | Prompts are created and managed in Architect's prompt library. | Click-to-play chips on the exact steps that played a prerecorded user prompt during this call. |
| Audio quality | Interactions view can be filtered by MOS range, above or below a value. | Per-leg MOS, R-factor, maximum latency and packet loss, rated on fixed, published thresholds. |
| Access model | User permissions such as Analytics > Conversation Detail > View and Conversation > Communication > View. | Read-only OAuth client credentials; analytics:readonly alone is enough, with optional scopes adding names, flow replay and audio. |
Flow replay depends on historical execution data being enabled and is limited by its 10-day retention, in both the native tooling and the app.
Sources
- Conversation Data Model – Genesys Cloud Developer Center
- View an interaction's details – Genesys Cloud Resource Center
- View an interaction's timeline – Genesys Cloud Resource Center
- View participant data attributes – Genesys Cloud Resource Center
- Historical execution data overview – Genesys Cloud Resource Center
- Interactions view – Genesys Cloud Resource Center
Participant data in native Genesys Cloud CX and in QVCCS Participant Data Analytics
| Aspect | Native Genesys Cloud CX | QVCCS Participant Data Analytics |
|---|---|---|
| One conversation | Participant Data section on an interaction's Details tab in Analytics Workspace, with copy-to-clipboard. | Conversations tab with each call's full raw map, a must-carry-key filter and up to 500 rows per page. |
| Bulk extraction | Interactions view export with Include Custom Attributes, for conversations processed by the overnight pipeline; 31-day custom date range in the view. | Org-wide harvest through analytics details jobs, one per UTC day, fetching only coverage gaps, up to 92 days per request. |
| Key inventory | Keys appear per interaction or as attribute data in an export file. | Catalogue of every key in range: class, coverage, distinct values, top values, first and last day written. |
| Change over time | Exported files for analysis in downstream tools. | Daily or hourly timelines with an improving, decaying or stable verdict, a movers board and schema drift banners. |
| History | 60-day time to live for participant data in interaction details; afterwards available through export. | Accumulating warehouse: each conversation stored once, coverage calendar shows exactly what is held. |
| API surface | Details jobs include attributes, truncated to 1,024 characters; the synchronous details query schema has no attributes. | Built on the jobs; defensive caps of 150 keys and 300 characters per conversation. |
| Messy keys | Key names are whatever each flow author wrote. | Automatic volatile-family detection and reversible ignore or fold rules. |
| Access | Role-based permissions for each user in the Genesys Cloud UI. | Read-only OAuth client credentials; analytics:conversationDetail:view required. |
Participant Data Analytics complements the native views. Values are stored unredacted for analysis, so the warehouse deserves the same care as call recordings.
Native SIP diagnostics and SIP Trace Analyser
| Aspect | Native Genesys Cloud CX | QVCCS SIP Trace Analyser |
|---|---|---|
| Starting point | The SIP Diagnostics section of one interaction’s Details tab. | A search across a date range for voice conversations that ended with error, system or transportFailure. |
| Signalling evidence | Download the interaction’s SIP traces file and PCAP for a network protocol analyser. | Trace metadata cards per SIP Call-ID, with trace-file and PCAP downloads for the same analysis. |
| Response codes | Visible inside the PCAP’s signalling history; analytics segments can record sipResponseCodes. | Shows segment sipResponseCodes and scans trace files across a page of calls for chosen codes such as 480 or 503. |
| Error classification | disconnectType per segment in the analytics record. | Purpose-aware rules: system counts only on external legs, and WebRTC, ICE and DTLS media errors are excluded. |
| Trunk attribution | The analytics session carries edgeId and provider rather than a trunk. | Positive identification from the INVITE request-URI domain, ACL IP ranges and BYOC FQDNs; never a guess. |
| Coverage and retention | PCAPs for external-trunk calls, kept for 21 days; none for station-to-station; best-effort under load. | Relies on the same data, so the same limits apply; it assumes 21 days of trace retention. |
| Permissions | Telephony > Plugin > All and Telephony > Pcap > Add and View. | Analytics conversation detail view plus telephony read, and Pcap > Add only to request a PCAP; no configuration is ever changed. |
Native capabilities are as described in the Genesys Cloud Resource Center and Developer Center at the time of writing.
Genesys Cloud CX and Salesforce: native options and the QVCCS pattern
| Aspect | Native Genesys Cloud CX options | QVCCS data-action-led integration |
|---|---|---|
| Where agents work | CX Cloud: in the Salesforce console, with Genesys capabilities embedded through managed packages. Genesys Cloud for Salesforce: an embedded client in Salesforce. | In the Genesys Cloud agent workspace, with the matched Salesforce record one click away. |
| Platform basis | CX Cloud brings Genesys Cloud into Salesforce Service Cloud Voice. Genesys Cloud for Salesforce is built on Open CTI. | The Salesforce data actions integration: API calls from Architect flows and scripts. No Open CTI dependency. |
| Caller lookup | Static actions such as GetContactByPhoneNumber, and custom actions, in the Salesforce data actions integration. | Static phone lookup plus custom actions by account number and Contact Id, with translation maps shaped to each flow decision. |
| Screen pop | CX Cloud: GC_SCREEN_POP attribute set in Architect opens a Lightning page or record; the voice call record page by default. | A Genesys Cloud script built from participant data, with a layout that adapts to verification and lookup results, and a button to open the record. |
| Verification | Secure call flows, secure variables and Set Secured Data are available to any design. | Secret collected in a secure flow and checked by a data action; only a Verified flag reaches the agent. |
| Writing back | CX Cloud syncs call attributes to VoiceCall records through field mapping; Genesys Cloud for Salesforce maps interaction attributes to activity fields. | A custom data action creates a call log record with the conversation ID, a link to the interaction and chosen __c fields; self-service can create Cases. |
| Lifecycle | Genesys Cloud for Salesforce is in maintenance mode and retires with Open CTI on 28 February 2028; CX Cloud is the embedded path. | Unaffected by the Open CTI retirement; credentials move to the OAuth Client Credential Flow type. |
The approaches combine: the same data actions and participant data design serve a CX Cloud deployment if agents later move into the Salesforce console.
Sources
- Deprecation: Salesforce open CTI integration
- About Genesys Cloud for Salesforce
- About CX Cloud from Genesys and Salesforce
- Screen pop in CX Cloud from Genesys and Salesforce
- About the Salesforce data actions integration
- Response configuration for data actions
- Phone number searches with the data action integration
- How many seconds before a data action times out?
- Salesforce OAuth Client Credentials Flow migration guide
- Work with secure call and bot flows
Native trunk visibility and Trunk Monitor
| Aspect | Native Genesys Cloud CX | QVCCS Trunk Monitor |
|---|---|---|
| Trunk status | Status icon and tooltip on the External Trunks and Phone Trunks tabs; a Status dialog per Edge and network interface; status on the Edge page. | One card per trunk base name with a green, amber or red health dot and an x/N edges up count, updated by pushed transitions. |
| Call volume | Telephony Metrics widgets for trunk call counts, as gauges or bar charts for the current value or line graphs for a time period. | Rolling five-minute chart with inbound above and outbound mirrored below, plus up to three hours of zoomable session history. |
| Transition record | Status views show the current indicator and its message. | A timestamped health event log and chart annotations at the exact moment of each UP or DOWN transition. |
| Platform events and alerting | Operational Console events kept for 10 days, with triggers, alert rules and Amazon EventBridge integration. | No thresholds or callouts; it shows the health transitions Genesys pushes, for an engineer watching live. |
| Evidence for write-ups | Interactive line graphs with hover and zoom. | PNG export of either chart with annotations included. |
| Permissions | Trunk status and Telephony Metrics need the Telephony > Plugin > All permission. | The same Telephony read permission, with read-only API use. |
Native capabilities are as described in the Genesys Cloud Resource Center at the time of writing.
Bot insight in native Genesys Cloud CX and in QVCCS Bot Flow Diagnostics
| Aspect | Native Genesys Cloud CX | QVCCS Bot Flow Diagnostics |
|---|---|---|
| Scope | Optimization dashboard for Dialog Engine bot flows and digital bot flows; metrics for core bot flows, not invoked subflows. | Architect bot and digital bot flows; nested bot calls appear as their own nodes on the map. |
| Turn-level history | Utterance History and Bot Conversation Library retain the last 10 days; API resources kept approximately, but not before, 10 days. | Gap-aware warehouse keeps every harvested session and turn; windows of up to 42 days per run. |
| Aggregate metrics | Bot Performance Detail view: entries, durations, turns and intents, custom ranges up to 6 weeks. | KPIs computed from the full harvested population, with a best-effort aggregates cross-check. |
| Journey view | Journey Flows show milestones and flow outcomes that influence containment. | Journey map of prompts, asks, results, milestones and endings, with reach and branch shares. |
| One session | Bot Conversation Library: session id, bot result and reason. | Turn-by-turn replay with prompts, utterances, ask results, confidence bars and slot values. |
| Action-level issues | Top Bot Flow Actions with Issues: no match, no input and other outcomes by action. | Per-ask result mix, match rate and low-confidence matches, exported to a five-sheet workbook. |
| New intents | Intent Miner mines intents, utterances, topics and phrases from chat and call recordings. | Ranked no-match corpus and opt-in tuning recommendations for the bot's existing asks. |
Bot Flow Diagnostics complements the native bot insights; use Intent Miner and the Optimization dashboard alongside it.
The Knowledge workbench and Knowledge Manager
| Aspect | Native Genesys Cloud CX | QVCCS Knowledge Manager |
|---|---|---|
| Purpose | Create, organise, test, publish and optimise articles, with version history and a Knowledge Performance dashboard. | Read-only, point-in-time inventory and review of everything in the workbench; never edits content. |
| Scope of export | Per knowledge base: all articles or a specific time period, in CSV, JSON or XLSX. | Every knowledge base the client can see in one harvest, plus an inventory CSV across all of them. |
| Structure | Exports include the knowledge base ID and linked category and label structures; externalID and structure only in JSON. | Full category hierarchy, labels with colours and per-node counts, rebuilt from parent references. |
| Draft and published | Articles are authored as drafts and published in the workbench. | Bodies captured for both sides of every article, shown in Published and Draft tabs side by side. |
| Change over time | View and restore previous versions of an article. | Overview deltas against the previous harvest; raw snapshot downloadable for external comparison. |
| Review workflow | Filter articles, review feedback and use the knowledge optimizer inside the workbench. | Clickable totals with row drawers, search across titles and alternative phrases, deep links to articles. |
| Platform load | Interactive use of the workbench. | Paced harvest, then browsing works entirely from the snapshot with no further Genesys calls. |
Knowledge Manager harvests Knowledge Workbench V2; legacy V1 knowledge bases are listed with their metadata, but their content is not captured.
Native number administration and the QVCCS DID Conflict Checker
| Aspect | Native Genesys Cloud CX | QVCCS DID Conflict Checker |
|---|---|---|
| Number to flow | Call Routing lists each route’s open, closed and holiday flows and its inbound numbers; DID Assignments shows each number’s assignee and type. | One view per inbound flow merging call routes, DID records, DID pools, site number plans and trunk routes, each number tagged with its source. |
| Agent profile numbers | Held on the user’s profile; no cross-check against inbound numbers is described in the Call Routing or DID Numbers documentation. | Every active user’s addresses, contact info and phones compared with every registered number on equality or the last ten digits. |
| Numbers reaching two flows | The API states an IVR’s numbers must be unique and not in use by another resource. | Registers numbers from all five sources and flags any that reach two distinct flows, ignoring same-flow provenance overlap. |
| Outbound caller IDs | Set per campaign as the caller ID number and name. | Flags every inbound DID that is also a campaign callerAddress, with the campaign’s Active or Off state. |
| Stale and orphaned flows | Flow records expose publish and modify dates through the flows API. | Staleness chip at 180 days and a no-DID toggle combine into a decommission-candidate list. |
| Access needed | Call Routing administration uses Call Route add, edit, view and delete permissions. | Read-only role; GET requests only, plus the OAuth token call. |
| Evidence | Each admin page shows its own object. | CSV, five-sheet Excel and a branded PDF built in the browser. |
Native behaviour is as described in the Genesys Cloud Resource Center and Platform API documentation at the time of writing.
Sources
- Call routing overview – Genesys Cloud Resource Center
- Add a call route – Genesys Cloud Resource Center
- Manage DID and toll-free number assignments
- Manage DID and toll-free number ranges
- Architect APIs – Genesys Cloud Developer Center
- Telephony APIs – Genesys Cloud Developer Center
- Outbound APIs – Genesys Cloud Developer Center
Licences and permissions in native Genesys Cloud CX and in QVCCS Permissions Auditor
| Aspect | Native Genesys Cloud CX | QVCCS Permissions Auditor |
|---|---|---|
| A user's licence | Divisions & Licenses tab shows the user's licence and any add-ons; licence users API returns assignments. | Assigned, attributed and inferred side by side for every user, with mismatches raised as findings. |
| Why a role needs a tier | Edit Role page shows the licence required; a role's licence follows its highest-tier permission. | Driver permissions traced to their granting roles for every user, with sole source marked. |
| Licence inference | POST /api/v2/license/infer returns licences inferred from a list of role ids. | Called for each distinct role set (up to 300) as an independent cross-check of the engine. |
| Scale of a role change | Role membership lists who holds a role. | Blast radius per role: holders, users it solely escalates and the saving at your rate card. |
| Unused access | Edit Role identifies unused permissions in a role. | Zombie seats with no login for 90+ days, and digital tiers that handled no digital work. |
| Trying a fix | Edit the role in Admin; permission updates take up to five minutes to take effect. | What-if scenarios preview the tier moves first; nothing is written to Genesys. |
| Money | Billable usage report gives licence quantities, without prices. | Editable rate card × audited counts, with provenance shown on every figure. |
Genesys's own assignment and inference remain authoritative; the auditor explains them and highlights where they differ from the permissions users actually hold.
Genesys Cloud CX and Zendesk: native options and the QVCCS pattern
| Aspect | Native Genesys Cloud CX options | QVCCS data-action-led integration |
|---|---|---|
| Where agents work | Genesys Cloud for Zendesk embeds Genesys Cloud contact centre services inside Zendesk. | In the Genesys Cloud agent workspace, with the matched Zendesk ticket one click away. |
| Zendesk prerequisites | The embedded client lists Zendesk licences including Zendesk Talk Partner Edition. The data actions integration needs a verified Zendesk user and OAuth client credentials; integrations still using API tokens must move before Zendesk retires them on 30 April 2027. | Built on the data actions integration alone, with no dependency on Zendesk Talk Partner Edition. |
| Caller lookup | Static actions such as Get User By Phone Number and Get User By Email Address, created when the integration is activated. | Static phone lookup plus custom actions by account number, shaped to each flow decision. |
| Recent tickets | Static actions return the most recent ticket by user ID or email address; custom actions can query any Zendesk REST endpoint. | A user-scoped request for live tickets, chosen and tested so a ticket created seconds earlier is returned. |
| Self-service | Custom actions can create, retrieve or update Zendesk data from Architect flows and scripts. | Callers hear their open tickets and raise a new one in a bot flow before reaching an agent. |
| Screen pop | The embedded client provides screen pop, scripts and interaction attributes inside Zendesk. | A Genesys Cloud script built from participant data, showing the caller's newest ticket and verified status. |
| Verification | Architect secure flows are available to any design for sensitive PCI and PII data. | No verification secret in readable Zendesk fields; only a verified flag and method reach the agent. |
| Timeouts and monitoring | Execution timeout configurable from 1 to 60 seconds; Data Actions Performance views show performance and failure rates. | Timeouts set per action, failure paths designed and tested, performance reviewed after go-live. |
The approaches combine: the same data actions and participant data design can serve an embedded Genesys Cloud for Zendesk deployment.
Sources
- About the Zendesk data actions integration
- Announcing the removal of API tokens as an authentication method for API requests – Zendesk help
- Genesys Cloud release notes, 9 November 2026 (Zendesk data actions OAuth client credentials grant support)
- Add contracts to custom actions for integrations
- Request configuration for data actions
- Response configuration for data actions
- How many seconds before a data action times out?
- Administrator requirements for the Genesys Cloud embedded clients
- Zendesk Search API reference
- Zendesk Tickets API reference (List User Requested Tickets)
Last reviewed