AI Meeting Transcription
Overview
FireHydrant's meeting-aware context enriches your incidents with insights directly from meeting transcripts. This ensures comprehensive situational awareness for all team members, regardless of their physical presence in bridges. Never worry about scribing live calls again, FireHydrant will take care of that for you.
FireHydrant currently supports meeting transcription for our Google Calendar and Zoom integrations.
After enabling, the FireHydrant Scribe will be invited to your meetings to capture crucial discussions and decisions made during incident bridges, providing a richer, more nuanced overview of the incident's progression.
Prerequisites
- You will need to have either the Google Calendar or Zoom integrations installed (requires Owner permissions)
- You'll need to have enabled AI features for your org (requires Owner permissions)
- You'll need at least Member permissions to configure Runbooks
Enabling transcripts
For Zoom Users Before April 2024
If you're configuring Google Calendar or Zoom for the first time after April 2024, you can skip to the next section.
If you installed the Zoom integration before April 2024, you will need to Reauthorize to grant additional permissions for meeting recording and inviting our Zoom bot to a given bridge:
- Navigate to the FireHydrant Integrations page
- Select the Zoom integration and click "Reauthorize" button*
- Accept the request for additional permissions to enable transcription services
*Note:
Ensure you are logged in as the Service/admin account in Zoom before doing so.
Specify Transcription in Runbook Steps
![Example Zoom Runbook step with "Transcribe Meeting?" option](https://files.readme.io/103ed7c-zoom_transcribe.png)
Example Zoom Runbook step with "Transcribe Meeting?" option
The available Runbook steps for the two integrations are:
When configuring or updating Runbook steps that initiate Google Calendar or Zoom meetings for incidents, check the option to Transcribe Meeting.
FireHydrant Scribe Participation
For incidents with transcription enabled:
- The FireHydrant Scribe will automatically attempt to join the designated meeting. Someone on the call may be required to admit the Scribe depending on how your settings are configured
- Ensure recording permissions are granted to capture the meeting's context
- (Zoom) If a user has a different email in their FireHydrant than Zoom, ensure they have linked their individual accounts
Utilizing Transcribed Content
Viewing and Editing Transcripts
![Example view of the live transcription on a call](https://files.readme.io/b768532-image.png)
Example view of the live transcription on a call
- In incidents where transcription is enabled, a dedicated button within the Summary Tab allows access to the meeting transcript.
- Team members can view the entire transcript to glean insights or review discussions during the meeting.
- Note: Direct editing of the transcript within FireHydrant is not currently supported. However, you can delete or remove specific snippets from the transcript using the trash can icon, and any subsequent summaries or inputs (re)generated will reflect removed information
Automatic Inclusion in Key Areas
Transcribed meeting content is automatically incorporated into several areas of your incident:
- Incident Summaries: The incident summaries include key insights and discussions from the transcribed content, offering a richer narrative and a more comprehensive overview of the incident.
- Incident Descriptions: The description of an incident can be augmented with details from the meeting transcripts, providing a clearer understanding of the incident's scope and nature.
- Customer Impact Summaries: Insights regarding the incident's impact on customers, discussed during the call, are automatically captured and reflected in customer impact summaries.
- Status Updates: Relevant information from the meeting is included when drafting status updates to ensure accurate, up-to-date communication with stakeholders.
- Retrospective Drafts: AI-driven retrospective drafting benefits from meeting discussions, ensuring that retrospectives are aware of not just the Slack channel context but also the spoken conversation.
Updated 3 months ago