Professional Analysis Document
Why Mandatory, Discretionary ACW Is the Only Current Option for Summarization Review
1. Background
In Genesys Cloud, call summarization is generated only after an agent selects a wrap-up code. When the wrap-up code is submitted, ACW ends and the agent is automatically returned to queue by default. There is currently no system capability to insert a validation window after wrap-up selection but before re-queue.
2. Why Other ACW Settings Do Not Work
- Mandatory, Time-Boxed: Forces auto-return to queue after a set timeout. Not acceptable for manual control.
- Mandatory, Time-Boxed (No Early Exit): Enforces a fixed review period but still auto-returns to queue.
- Agent Requested: Allows skipping ACW unless requested, but if requested, it is still bound by timers and auto-return.
In all these cases, wrap-up selection still ends ACW and resumes queue routing, so they do not solve the problem.
3. Mandatory, Discretionary ACW
With Mandatory, Discretionary ACW, once the wrap-up code is selected, the agent remains off-queue until they manually change their status back to On Queue. This is the only ACW configuration that prevents automatic return to queue and gives agents control over when they are available again.
4. Implications
- Review time is not counted as ACW since ACW ends with wrap-up submission.
- Agents appear in a Not Ready/off-queue state while validating summaries.
- Average Handle Time (AHT) does not include summary review duration.
- Supervisors must rely on status reports to measure summarization review times.
5. Roadmap
Genesys has confirmed that a future enhancement, planned for Q1 2026, will make summarization available at call disconnect. Once implemented, summarization will be part of ACW, and review time will be included in AHT. Until then, the only supported option is Mandatory, Discretionary ACW.
6. Conclusion
Mandatory, Discretionary ACW is the only viable option today. It ensures agents remain off-queue after wrap-up code selection, allowing them to review and validate summaries before manually returning to queue. Other ACW settings do not meet this requirement as they all force auto-return to queue.
Original Message:
Sent: 9/19/2025 11:30:00 AM
From: Amanda Halpin
Subject: RE: Agent Co-Pilot AI Summarization Reporting
Hi Alex,
I'm reviewing your use case again and the summary generates when the call end button is selected by the agent. The agent should receive the summary the same time as they receive the wrap up code predictions. If you're not seeing this then there could be an issue specific to your interactions or Agent Copilot configuration. I suggest you create a care case with example conversation IDs.
Thanks,
Amanda
------------------------------
Amanda Halpin
Agent Copilot Product Manager @ Genesys
------------------------------
Original Message:
Sent: 09-19-2025 11:04
From: Alex Slocum
Subject: Agent Co-Pilot AI Summarization Reporting
We will have to solve for the following until the summarization availability is done on disconnect
Title: Make Agent Copilot Summarization Available at Call Disconnect with Post-Wrap-Up Validation
Body:
Today, Agent Copilot summarization is only generated after an agent selects a wrap-up code and clicks Done. At that point, the agent is immediately placed back on queue, leaving no opportunity to review or edit the AI-generated summary before becoming available for the next interaction.
We request that summarization be made available at call disconnect, so it is part of ACW by design. Agents should then be able to:
-
Select a wrap-up code (mandatory first step),
-
Stay off-queue while reviewing/editing the summary,
-
Either manually mark "done" to return to queue, or auto-return at a configurable timeout.
This ensures summaries are accurate, validated, and part of ACW - aligning with quality and compliance needs while preserving handle time accuracy.
Original Message:
Sent: 9/19/2025 7:12:00 AM
From: Amanda Halpin
Subject: RE: Agent Co-Pilot AI Summarization Reporting
Hi Alex,
I don't have firm timelines yet, best guess it will be Q1 2026.
In other news, ACW reporting will be introduced to Agent Copilot Dashboard the week of 22nd Sept.
Amanda
------------------------------
Amanda Halpin
Agent Copilot Product Manager @ Genesys
Original Message:
Sent: 09-19-2025 04:23
From: Alex Slocum
Subject: Agent Co-Pilot AI Summarization Reporting
Can we get an ETA on this, as it will impact our roll out of Agent Copilot
Original Message:
Sent: 9/19/2025 4:11:00 AM
From: Amanda Halpin
Subject: RE: Agent Co-Pilot AI Summarization Reporting
Hi Alex,
We have an idea for this- where the agent can request the summary to be generated before the wrap up. More details are here: https://genesyscloud.ideas.aha.io/ideas/EPAGCOP-I-233
Amanda
------------------------------
Amanda Halpin
Agent Copilot Product Manager @ Genesys
Original Message:
Sent: 09-18-2025 13:51
From: Alex Slocum
Subject: Agent Co-Pilot AI Summarization Reporting
Amanda got an ticket open for a change in how Genesys makes Agent Copilot Summarization available for reporting or extraction only post wrap up code .and clicking done, This triggers don't give agent the CRM push prior for validation. Can change from Wrap Up Code to Call Disconnect
Genesys Support Request
Subject: Request to Enable Agent Copilot Summarization Availability at Call Disconnect
Customer: Premera Healthcare – Group 16 Project
Product: Genesys Cloud CX – Agent Copilot Summarization, Dynamics 365 Softphone IT Connector
Environment: Genesys Cloud + D365 Integration (Softphone IT AppFoundry Connector)
Background
Premera is implementing Genesys Cloud Agent Copilot AI Summarization with integration into Microsoft Dynamics 365 via the Softphone IT connector. Currently, the AI Summarization is only available/pushed after the agent selects the default wrap-up code and clicks Done, meaning the summary is logged post-ACW.
This delays visibility and does not align with the operational need: summaries should be part of the ACW process itself, available as soon as the call is disconnected so agents can validate and confirm before wrap-up completion.
Request
We request Genesys to change the behavior so that Agent Copilot Summarization is available at call disconnect instead of waiting until wrap-up is submitted.
Business Impact
Agent Workflow Alignment: ACW includes validating notes and summaries. Having the summary only after wrap-up conflicts with this definition.
Efficiency: Delayed push forces agents back to queue without validating the CRM log, increasing rework and risk of errors.
Data Quality: Summaries may not be properly reviewed if they are pushed post-ACW.
Compliance: Our business process requires human validation of AI outputs before finalizing wrap-up.
Requested Outcome
Genesys to confirm and/or implement the following:
Summarization generation and availability at call disconnect (before wrap-up).
Ability for integrations (e.g., Softphone IT D365 Connector) to retrieve and push the summary during ACW.
Confirmation of expected timelines or product roadmap for this change if it cannot be immediately enabled.
------------------------------
Alex Slocum
Original Message:
Sent: 09-17-2025 04:20
From: Amanda Halpin
Subject: Agent Co-Pilot AI Summarization Reporting
Hi Deepa,
Release notes is updated every Monday with releases coming out that week. https://help.mypurecloud.com/release-notes-home/
Aha is also where you can see details on roadmap items that are under development: https://genesyscloud.ideas.aha.io/
Amanda
------------------------------
Amanda Halpin
Agent Copilot Product Manager @ Genesys
Original Message:
Sent: 09-16-2025 20:21
From: Deepa Galaiya
Subject: Agent Co-Pilot AI Summarization Reporting
Hi Amanda - Do you have a link to this on the knowledge resource centre or elsewhere that provides additional information on the upcoming enhancements?
------------------------------
Deepa Galaiya
Product Owner, Customer Interactions
Original Message:
Sent: 09-16-2025 05:01
From: Amanda Halpin
Subject: Agent Co-Pilot AI Summarization Reporting
Hi Alex,
Keep an eye out for After Call Work metrics (summaries and wrap up code) metrics being added to the Agent Copilot dashboard in the next couple of weeks. This should have you easily understand summary usage and feedback from within Genesys Cloud.
Amanda
------------------------------
Amanda Halpin
Agent Copilot Product Manager @ Genesys
Original Message:
Sent: 09-13-2025 19:50
From: Deepa Galaiya
Subject: Agent Co-Pilot AI Summarization Reporting
Hi Alex,
Interesting post. We have recently implemented Auto Sum and Predictive wrap codes and have received mixed feedback from our agents. We are hoping that custom prompts coming soon (ETA 15/10) will help us resolve a lot of the following issues so we can start to see real business benefits. We are also investing more in our change management to reiterate the message that good is good enough.
- After Call Work ACW has increased. Agentss were used to capturing notes during the call, but now they have to wait until the call ends to review and edit for accuracy, numbers and PII.
- Auto Summary is overly verbose. Agents are still adjusting to a new skillset of editing summaries instead of typing live. Longer calls generate lengthy summaries, which can feel overwhelming to review. This will require ongoing support as they build proficiency.
- AI is not intelligent enough to pick out the important parts of the conversation and sometimes contains non-essential information that doesn't add value. Feedback from agents is that long notes impact the next caller experience as they must read and interpret them to determine relevance, which increases AHT. They were used to typically expect only key, actionable information in the summary.
- The tool sometimes merges multiple topics into a single sentence and misrepresents role positions which takes longer to edit.
- AI auto sum flips the position of roles for third parties such as advisers calling on behalf of the member, spouses, lawyers calling on behalf of the member. Takes longer to edit these.
PROs
On a positive note we have found that accuracy is good for low complexity calls and that the extra detail adds value for our QA team in reviewing calls.
Auto sum has also created consistency across all notes which was lacking before.
Cheers
------------------------------
Deepa Galaiya
Product Owner, Customer Interactions
Original Message:
Sent: 09-13-2025 12:55
From: Alex Slocum
Subject: Agent Co-Pilot AI Summarization Reporting
Genesys Team
Can we get AI Summarization Reporting in ASAP
The option to get the AI Summarization via API does not return the AI Summarization in whole and was told this was a current defect
We are manually do reporting via Excel
Analysis of Genesys Agent Copilot Feedback
Overall Feedback Trends
Out of 35 agent feedback responses on their first use of Genesys Agent Copilot with the new AI Summarization feature (replacing "Talk and Doc"), several clear trends emerge:
Sentiment: Approximately 69% of the comments were negative in tone, about 20% were neutral, and only around 11% were positive. In other words, the majority of agents expressed some dissatisfaction or pointed out issues, while a small fraction provided positive feedback.
Adoption Behavior: Mirroring the sentiment, roughly 69% of agents appeared hesitant about adopting the AI Summarization (often due to errors or confusion), about 29% were neutral (neither particularly excited nor opposed), and only one agent (~3%) was clearly enthusiastic about the new tool.
Perceived Benefit or Issue: By far the most common theme in the feedback was Confusion/Training Need – about 83% of responses highlighted inaccuracies, misunderstandings, or confusion in the AI-generated summaries. A minority (~14% of responses) noted Increased Clarity/Ease of Use as a benefit (e.g. the summary was largely accurate or helpful). Notably, none of the agents explicitly mentioned Reduced Handle Time (RHT) or Redundancy with existing workflow in their comments, suggesting that time-saving or duplication of effort were not prominent in this initial feedback. Only one comment (~3%) indicated no notable impact (neither a clear benefit nor issue).
In general, most agents encountered accuracy and clarity issues with the AI summaries – for example, incorrect numbers, misunderstood names/terms, or missing information – which led to negative sentiment and hesitancy toward the tool. On the other hand, the few positive comments typically praised the summary's correctness or ease (indicating better clarity), albeit often still pointing out minor errors. Overall, early feedback skews critical, focusing on what the AI got wrong rather than on time savings or other benefits.
#ConversationalAI(Bots,AgentAssist,etc.)
------------------------------
Alex Slocum
------------------------------