Google introduces conversation summaries in Google Chat Spaces using the Pegasus abstractive summarization model
Information overload from the volume of incoming chat messages and documents is a significant challenge for organizations and individuals, worsened by the shift to virtual and hybrid work environments.
The abstractive summarization model occasionally produces low-quality outputs of two types: misattribution (confusing who said or did what) and misrepresentation (summaries that contradict the actual conversation). The initial hybrid model also had noticeable latency when users opened Spaces.
Google deployed conversation summaries in Google Chat Spaces, showing automatically generated digest cards when users enter Spaces with unread messages; latency was resolved by pre-generating summaries on message events and caching them ephemerally.
Show all 5 reported metrics
Frequently asked questions
What did this team achieve with this AI workflow?
Google deployed conversation summaries in Google Chat Spaces, showing automatically generated digest cards when users enter Spaces with unread messages; latency was resolved by pre-generating summaries on message even…
What tools did this team use?
Pegasus, ForumSum.
What results were reported?
ForumSum training conversations collected: over six thousand; Average speakers per training conversation: more than 6; Average utterances per training conversation: 10; Distilled model latency and memory footprint: lower latency and memory footprint while maintaining similar quality (source-reported, not independently verified).
What failed first in this deployment?
The abstractive summarization model occasionally produces low-quality outputs of two types: misattribution (confusing who said or did what) and misrepresentation (summaries that contradict the actual conversation).
How is this back office ops AI workflow structured?
Message event triggers summary update → Pegasus generates abstractive summary → Summaries cached ephemerally → Summary card shown to user.