✅ PRECONDITIONS
Companion - Summarization is an optional feature as part of Transcription:
- The Transcription feature must be enabled on the Companion Service Settings, as the Summarization is generated from it.
- Companion Service Settings also steer the individual feature availability to users, as well as the data storage retention time.
- Each user accessing the feature requires a Companion License, applied via General User Settings.
The Nimbus Companion integrates AI summarization as part of a broader suite of Transcription features, aimed at improving service performance and agent efficiency. During a call - when Live Captioning is enabled - Nimbus transcribes the conversation in real time. After the call, the transcript is processed by an AI service to generate a summary with the following aspects:
| Aspect | Description |
|---|---|
| Title | A title generated from Call Direction, Service, and User that accepted the task. |
| Issue | Shortened problem description by the Customer. |
| Resolution | Summary of how the issue was resolved. |
| Recap | A brief paragraph summarizing the interaction. |
| Narrative | Detailed call notes or chat summary of the entire Customer/User Interaction. |
Summarization Outputs
Via My Sessions: Summarization outputs can be presented to the agent via My Sessions > Companion widget.
💡All aspects shown within the Companion Widget > Summarization can be hovered over and copied.
✅ Precondition: The “Companion” widget itself needs to be enabled in the Extensions Service Settings in order to be shown to users.
Via Nimbus Power Automate Connector: Administrators also have the possibility to flexibly retrieve and store Summarization outputs using Companion Flow Actions and the User/Service SessionID. This can be useful to keep a record of calls, e.g. within a CRM or long-term data storage and evaluation platform.
Known Limitations
Summarization relies on the Transcription feature and therefore shares the same design limitations.
INC Transcription Limitations
KNOWN TRANSCRIPTION & SUMMARIZATION LIMITATIONS
💡We are actively working on further improvements to the following limitations:
- Transcription data is not part of service/user transfers. Data is kept within the current customer/user session.
- Transcription is currently only supported for direct inbound calls. Outbound Calls (i.e. Call On Behalf), and Consultation calls (either to user or Services) are not yet supported.
- Transcription > Summarization features are still in preview. The Summarization is only available on My Sessions.
Troubleshooting FAQ
INC Transcription Troubleshooting
Not seeing any transcripts in the Transcript widget can have several causes. The following table lists error messages and explains why they are shown.
| Message shown | 🤔 Why do I see the message? |
|---|---|
| No transcription is available for this interaction. |
There was no transcription generated for the selected conversation. This could happen …
|
|
No transcription is available for this interaction OR Task was not accepted. |
|
| User Transcription License is missing. |
|
BY DESIGN
💡The following points are not limitations.
-
Feature availability:
- Transcription is a prerequisite to Live Captioning and Summarization. A working Speech Recognizer must be configured to use all features.
- Transcription relies on external services and APIs. When the feature is disabled or unavailable (e.g. throttling, settings or Microsoft service impediments) info messages are shown in the frontend UI widget. Nimbus task handling and user-customer interactions themselves are not affected by this and will continue normally.
-
Transcription scope:
- 3rd-party participants: Third parties and call conference attendees are not part of the content transcribed. Only the transcription between the Nimbus user and the customer is kept.
- Supervision - As long as Supervisors remain in Listen or Whisper mode during a conversation, their voice is not being transcribed. Only during ”Barge In" they are part of the conversation and transcription is active.
- Summarization items generated from the Transcription might be missing when there is not enough data to draw from.