Genesys Cloud - Main

 View Only

Sign Up

Expand all | Collapse all

Agent Co-Pilot AI Summarization Reporting

  • 1.  Agent Co-Pilot AI Summarization Reporting

    Posted 09-13-2025 12:56

    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
    ------------------------------


  • 2.  RE: Agent Co-Pilot AI Summarization Reporting

    Posted 09-13-2025 19:51
    Edited by Deepa Galaiya 09-13-2025 19:51

    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
    ------------------------------



  • 3.  RE: Agent Co-Pilot AI Summarization Reporting
    Best Answer

    Posted 09-16-2025 05:02

    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
    ------------------------------



  • 4.  RE: Agent Co-Pilot AI Summarization Reporting

    Posted 09-16-2025 20:21

    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
    ------------------------------



  • 5.  RE: Agent Co-Pilot AI Summarization Reporting

    Posted 09-17-2025 04:20

    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
    ------------------------------



  • 6.  RE: Agent Co-Pilot AI Summarization Reporting

    Posted 09-18-2025 13:52

    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:

    1. Summarization generation and availability at call disconnect (before wrap-up).

    2. Ability for integrations (e.g., Softphone IT D365 Connector) to retrieve and push the summary during ACW.

    3. Confirmation of expected timelines or product roadmap for this change if it cannot be immediately enabled.



    ------------------------------
    Alex Slocum
    ------------------------------



  • 7.  RE: Agent Co-Pilot AI Summarization Reporting

    Posted 09-18-2025 15:45

    Alex, is this using the Microsoft Dynamics Connector from Genesys PS, with the Agent Copilot view open during the call in the embedded client?



    ------------------------------
    George Ganahl GCCX-AI, GCP, GCSME
    Technical Adoption Champion
    Genesys
    2024 Community Member of the Year
    ------------------------------



  • 8.  RE: Agent Co-Pilot AI Summarization Reporting

    Posted 09-19-2025 04:11

    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
    ------------------------------



  • 9.  RE: Agent Co-Pilot AI Summarization Reporting

    Posted 09-19-2025 04:24
    Can we get an ETA on this, as it will impact our roll out of Agent Copilot





  • 10.  RE: Agent Co-Pilot AI Summarization Reporting

    Posted 09-19-2025 07:12

    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
    ------------------------------



  • 11.  RE: Agent Co-Pilot AI Summarization Reporting

    Posted 09-19-2025 10:00
    Amanda, that is good to hear.  Please reach out so we can be a part of Agent Copilot Betas moving forward





  • 12.  RE: Agent Co-Pilot AI Summarization Reporting

    Posted 09-19-2025 11:04
    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.





  • 13.  RE: Agent Co-Pilot AI Summarization Reporting

    Posted 09-19-2025 11:30

    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
    ------------------------------



  • 14.  RE: Agent Co-Pilot AI Summarization Reporting

    Posted 09-19-2025 12:10
    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.






  • 15.  RE: Agent Co-Pilot AI Summarization Reporting

    Posted 09-19-2025 12:12
    Amanda

    We have tested and summaries are not available on call disconnect via agent or customer.  It is only available when wrap up code is selected 

    We can get on a meeting to validate





  • 16.  RE: Agent Co-Pilot AI Summarization Reporting

    Posted 09-19-2025 12:21
    Amanda

    Posted Interaction ID's to support ticket for review.  


    Received the following feedback





  • 17.  RE: Agent Co-Pilot AI Summarization Reporting

    Posted 09-19-2025 12:37
    Done





  • 18.  RE: Agent Co-Pilot AI Summarization Reporting

    Posted 09-17-2025 11:40

    Thanks for the response Amanda, can't wait to see AI Summarization a part of Performance Reporting.  Question is there a option of being a part of beta development for AI Summarization into CRM accounts?  This is critical for Healthcare Compliance as it blocks our ability to roll it out to our Provider Agents, who call on multiple members and summarization only occurs on the first member inquiry.   This would be a came changer.



    ------------------------------
    Alex Slocum
    ------------------------------



  • 19.  RE: Agent Co-Pilot AI Summarization Reporting

    Posted 09-17-2025 12:14

    Hi Alex,

    You can use API's and data actions to send the summary to a CRM today. We haven't made it a setting that you can turn on in the UI just yet though.

    I think your use case is slightly different though. How is the Provider calling the members and are all the members are on the same call?

    Amanda



    ------------------------------
    Amanda Halpin
    Agent Copilot Product Manager @ Genesys
    ------------------------------



  • 20.  RE: Agent Co-Pilot AI Summarization Reporting

    Posted 09-19-2025 04:02

    Amanda can we get Agent Copilot Summarization be available on disconnect instead of on wrap up code.  It will allow the agent to review and update the summary when applicable,  Now agents have to manually put themselves on queue.  If summarization is available on disconnect, agent can be automatically placed back on queue after the click wrap up code and done



    ------------------------------
    Alex Slocum
    ------------------------------



  • 21.  RE: Agent Co-Pilot AI Summarization Reporting

    Posted 09-23-2025 14:36

    Hi Amanda, could you please advise if turning this on in the UI is on the Genesys road map? That would help us out as our Devs are tied up with other work at the moment.

    Thanks :-)



    ------------------------------
    Lee Smith
    Senior Business Analyst Contract
    Genesis Energy
    lee.smith@genesisenergy.co.nz
    ------------------------------



  • 22.  RE: Agent Co-Pilot AI Summarization Reporting

    Posted 09-24-2025 09:31

    Hi Lee,

    We may revisit it in the future but it's not something that's planned to be enabled in the UI this year.

    Thanks,
    Amanda



    ------------------------------
    Amanda Halpin
    Agent Copilot Product Manager @ Genesys
    ------------------------------



  • 23.  RE: Agent Co-Pilot AI Summarization Reporting

    Posted 09-18-2025 15:21

    Thank you, Deepa...I find that to be helpful insight as I decide where and how to recommend its use.



    ------------------------------
    George Ganahl GCCX-AI, GCP, GCSME
    Technical Adoption Champion
    Genesys
    2024 Community Member of the Year
    ------------------------------



  • 24.  RE: Agent Co-Pilot AI Summarization Reporting

    Posted 09-19-2025 04:21

    Hi Deepa,

    A few comments to add to your observations.

    An initial increase in ACW time is normal as we find there is a transition period for agents. This will level out once they've adapted to having the summary generated for them. We also have an upcoming feature, https://genesyscloud.ideas.aha.io/ideas/EPAGCOP-I-233 which will allow the agent to generate the summary before the call ends.

    Our first release of custom summaries allows you to choose if you want the summary to be verbose of concise. You can try this out in AI Studio. We also introduced custom insights, allowing you to pull out certain information into the summary what was discussed, eg account number. If you have tried these and it's still missing your needs, then yes, advanced custom prompt summaries is worth testing when it's released in Q4.

    Thanks,

    Amanda



    ------------------------------
    Amanda Halpin
    Agent Copilot Product Manager @ Genesys
    ------------------------------



  • 25.  RE: Agent Co-Pilot AI Summarization Reporting

    Posted 09-19-2025 04:28
    Genesys Cloud ACW Configuration Admin Guide for AI Summary Validation
    This guide provides administrators with clear instructions to configure After Call Work (ACW) in Genesys Cloud queues where Agent Copilot summarization must be validated by agents before they return to the queue. The settings described here use only the ACW options available in Genesys Cloud today.
    1. Understanding ACW Options
    Genesys Cloud provides four ACW modes:

    - Mandatory, Discretionary: Agents must complete wrap-up and remain in ACW until they manually exit.
    - Mandatory, Time-boxed: Agents must complete wrap-up and have a set time window to complete ACW. They may exit early.
    - Mandatory, Time-boxed (No Early Exit): Agents must complete wrap-up and are held in ACW for the full set time.
    - Agent Requested: ACW is only provided if the agent requests it.

    For AI summary validation, administrators should use one of the Mandatory options to ensure wrap-up code selection and protected time for summary review.
    2. Queue Configuration
    1. Navigate to Admin → Contact Center → Queues.
    2. Select the queue to configure.
    3. In the ACW section, select one of the following modes:
       - Mandatory, Time-boxed: Recommended for balancing validation needs and efficiency. Set the time box to the average time agents need to validate summaries (e.g., 60–90 seconds). Enable early exit if you want agents to return to the queue sooner when validation is completed quickly.
       - Mandatory, Time-boxed (No Early Exit): Recommended if you want every agent to use the full validation window.
       - Mandatory, Discretionary: Recommended if agents require variable time. This allows unlimited time but may reduce queue availability if agents linger.
    4. Save the queue configuration.
    3. Wrap-up Code Enforcement
    Genesys Cloud does not support assigning a default wrap-up code at the queue level. Instead, supervisors must enforce use of a standard wrap-up code (e.g., 'AI Summary Required') through SOPs and reporting. Configure the list of wrap-up codes for the queue and train agents to always select the designated code. Supervisors should use reports to monitor compliance.
    4. Agent Workflow
    1. End the call and select the required wrap-up code.
    2. Click Done to complete ACW. This action triggers Agent Copilot summarization.
    3. Remain in ACW for the configured duration (Mandatory, Time-boxed) or until manual exit (Mandatory, Discretionary).
    4. Validate and edit the AI-generated summary.
    5. Return to the queue either automatically after the time-box or manually when validation is complete.
    5. Supervisor Monitoring
    Supervisors are responsible for ensuring compliance with ACW and summary validation:

    - Use Performance → Interactions → Wrap-up to monitor wrap-up code usage.
    - Use Performance → Agents → Agent Status to observe ACW time and return-to-queue behavior.
    - Coach agents who skip summary validation or misuse ACW.
    - Escalate repeated non-compliance through performance management.
    6. Best Practice Recommendations
    - Set ACW to Mandatory, Time-boxed with a 60–90 second window for most environments.
    - Allow early exit if summaries are usually quick to validate.
    - Use Time-boxed (No Early Exit) if you want to guarantee the full validation window is always used.
    - Use Discretionary only if summary validation times vary widely and supervisors can closely monitor compliance.
    - Reinforce SOPs with agents and use monitoring reports to ensure adherence.
    Conclusion
    By configuring queues with Mandatory ACW settings and enforcing wrap-up code compliance, administrators ensure that agents always have protected time to validate AI summaries before returning to the queue. This guarantees accuracy, supports compliance, and balances efficiency with quality control.





  • 26.  RE: Agent Co-Pilot AI Summarization Reporting

    Posted 09-19-2025 04:30

    Impact of Genesys Cloud AI Summarization on Agent Call Handling Time

    This document provides a clear understanding of how Genesys Cloud AI Summarization impacts Agent Call Handling Time (AHT) and After Call Work (ACW). It highlights the differences between traditional manual documentation and automation with AI Summarization, showing how automation reduces handling time rather than increasing it.

    1. Traditional Call Handling Without AI Summarization

    - Talk Time: Duration of the live conversation between the agent and the customer.
    - Documentation Time: Agents typically spend 2–5 minutes documenting the call after it ends.
    - ACW (Default Wrap-Up Time): A standard wrap-up window (e.g., 30–60 seconds) for tagging outcomes and finalizing dispositions.

    Impact: A call that lasts 10 minutes could extend to 12–15 minutes total handling time once documentation and wrap-up are included, which inflates AHT and reduces agent availability.

    2. Call Handling With Genesys AI Summarization

    - Talk Time: The conversation length remains the same (e.g., 10 minutes).
    - AI Summarization: Automatically generates structured call notes in real time and delivers them at call end.
    - ACW (Default Wrap-Up Time): Remains, but agents only spend seconds validating/editing AI notes instead of typing from scratch.

    Impact: The same 10-minute call now has a total handling time of 10–10.5 minutes (instead of 12–15), reducing post-call work dramatically.

    3. Why ACW Doesn't Inflate AHT

    The key is that AI Summarization streamlines ACW instead of adding to it:
    - Before AI: ACW + manual note taking extended handling time.
    - After AI: ACW is streamlined-agents quickly validate AI notes.

    Result: AHT decreases because manual effort is replaced, not duplicated.

    4. Comparing Metrics: Pre vs. Post Summarization

    Metric Component

    Pre-AI Summarization

    Post-AI Summarization

    Impact

    Talk Time

    10 min

    10 min

    No change

    Documentation Time

    2–5 min

    0 min

    Automation replaces manual notes

    ACW

    1–2 min

    0.5–1 min

    Streamlined to quick validation

    Total Handling Time

    13–17 min

    10–11 min

    Overall AHT reduced

    AHT Reduction

    -

    20–35%

    Increased productivity

    5. Conclusion

    - AI Summarization doesn't add to ACW-it compresses it.
    - AHT decreases because documentation no longer extends beyond the conversation.
    - Organizations benefit from improved productivity, more calls handled per shift, and better consistency in captured notes.



    ------------------------------
    Alex Slocum
    ------------------------------



  • 27.  RE: Agent Co-Pilot AI Summarization Reporting

    Posted 09-19-2025 04:30
    Impact of Genesys Cloud AI Summarization on Agent Call Handling Time
    This document provides a clear understanding of how Genesys Cloud AI Summarization impacts Agent Call Handling Time (AHT) and After Call Work (ACW). It highlights the differences between traditional manual documentation and automation with AI Summarization, showing how automation reduces handling time rather than increasing it.
    1. Traditional Call Handling Without AI Summarization
    - Talk Time: Duration of the live conversation between the agent and the customer.
    - Documentation Time: Agents typically spend 2–5 minutes documenting the call after it ends.
    - ACW (Default Wrap-Up Time): A standard wrap-up window (e.g., 30–60 seconds) for tagging outcomes and finalizing dispositions.

    Impact: A call that lasts 10 minutes could extend to 12–15 minutes total handling time once documentation and wrap-up are included, which inflates AHT and reduces agent availability.
    2. Call Handling With Genesys AI Summarization
    - Talk Time: The conversation length remains the same (e.g., 10 minutes).
    - AI Summarization: Automatically generates structured call notes in real time and delivers them at call end.
    - ACW (Default Wrap-Up Time): Remains, but agents only spend seconds validating/editing AI notes instead of typing from scratch.

    Impact: The same 10-minute call now has a total handling time of 10–10.5 minutes (instead of 12–15), reducing post-call work dramatically.
    3. Why ACW Doesn't Inflate AHT
    The key is that AI Summarization streamlines ACW instead of adding to it:
    - Before AI: ACW + manual note taking extended handling time.
    - After AI: ACW is streamlined-agents quickly validate AI notes.

    Result: AHT decreases because manual effort is replaced, not duplicated.
    4. Comparing Metrics: Pre vs. Post Summarization
    Metric Component
    Pre-AI Summarization
    Post-AI Summarization
    Impact
    Talk Time
    10 min
    10 min
    No change
    Documentation Time
    2–5 min
    0 min
    Automation replaces manual notes
    ACW
    1–2 min
    0.5–1 min
    Streamlined to quick validation
    Total Handling Time
    13–17 min
    10–11 min
    Overall AHT reduced
    AHT Reduction
    -
    20–35%
    Increased productivity
    5. Conclusion
    - AI Summarization doesn't add to ACW-it compresses it.
    - AHT decreases because documentation no longer extends beyond the conversation.
    - Organizations benefit from improved productivity, more calls handled per shift, and better consistency in captured notes.






  • 28.  RE: Agent Co-Pilot AI Summarization Reporting

    Posted 09-19-2025 06:09

    Thanks Amanda, It would be good to get a timeframe for this enhancement to communicate internally? Also, would this mean that once the summary has been generated this would be final and it wouldn't then update the generated summary once the interaction ended?



    ------------------------------
    Deepa Galaiya
    Product Owner, Customer Interactions
    ------------------------------



  • 29.  RE: Agent Co-Pilot AI Summarization Reporting

    Posted 09-19-2025 06:59

    Hi Deepa,

    I don't have details on timelines yet, I would say at this stage it's a Q1 2026 deliverable. I'd suggest reaching out to your account team in a month or so who will be updated on timelines as details are confirmed.

    Your assumption is correct- if the agent requests for the summary to be generated early then they will only receive that summary and not a second one at the end of the conversation.

    Amanda



    ------------------------------
    Amanda Halpin
    Agent Copilot Product Manager @ Genesys
    ------------------------------



  • 30.  RE: Agent Co-Pilot AI Summarization Reporting

    Posted 09-19-2025 07:04

    Thanks Amanda - keen to keep across these enhancements

    Cheers



    ------------------------------
    Deepa Galaiya
    Product Owner, Customer Interactions
    ------------------------------



  • 31.  RE: Agent Co-Pilot AI Summarization Reporting

    Posted 09-19-2025 20:13

    @Amanda - I am interested in understanding how this would work? So if I am on an active call and want to generate the auto summary before the interaction ends, will there be a new button on the Genesys UI to "Generate summary"



    ------------------------------
    Deepa Galaiya
    Product Owner, Customer Interactions
    ------------------------------



  • 32.  RE: Agent Co-Pilot AI Summarization Reporting

    Posted 09-22-2025 04:36

    Hi Deepa,

    The finer details of new functionality are being worked out. Please keep an eye on the aha idea and keep in touch with your account team for updates.

    Thanks,

    Amanda



    ------------------------------
    Amanda Halpin
    Agent Copilot Product Manager @ Genesys
    ------------------------------



  • 33.  RE: Agent Co-Pilot AI Summarization Reporting

    Posted 09-18-2025 15:30

    This info is very helpful to me, Alex. Thanks!



    ------------------------------
    George Ganahl GCCX-AI, GCP, GCSME
    Technical Adoption Champion
    Genesys
    2024 Community Member of the Year
    ------------------------------



  • 34.  RE: Agent Co-Pilot AI Summarization Reporting

    Posted 09-22-2025 19:44

    AI Summarization

    Annunciation Quick Reference Cheat Sheet

    Purpose: Provide agents with fast, at-a-glance rules for annunciation of numbers, dates, medications, IDs, and addresses. Use this sheet during calls to ensure clarity and consistency.

    Numbers

    • Always state the number in words, then repeat with digit groups.

    Example: 'Five-hundred dollars - five-zero-zero.'

    Dates

    • State month and day in words, then repeat in digit format.

    Example: 'August fifth, twenty-twenty-five - zero-eight slash zero-five slash two-zero-two-five.'

    Medications

    • Spell out the medication name clearly using the alphabet.

    Example: 'Zylera - spelled Z-Y-L-E-R-A.'

    IDs and Authorization Numbers

    • Annunciate one digit at a time or in small groups; include hyphens or dashes.

    Example: 'Authorization number P-A dash nine-eight-seven-six-five.'

    Addresses & Phone Numbers

    • Read out digits in groups; spell out street names when necessary.

    Example: 'One-zero-one-zero Maple Avenue, Orlando, Florida, ZIP three-two-eight-zero-one.'

    Example: 'Phone: eight-eight-eight, eight-nine-two, seven-one-eight-zero.'

    Interaction Summary Reminders

    • Capture four elements: Reason for Contact, Resolution, Action Items, Reason for Sentiment.

    • Always close by summarizing: 'To summarize: …'



    ------------------------------
    Alex Slocum
    ------------------------------