Skip to main content
Question

Scribe Agent transcript posting to service alerts channel instead of the dedicated incident channel

  • June 30, 2026
  • 1 reply
  • 93 views
S

Hi all
Looking for help pinning down where Scribe's transcript routing is decided.

Setup:
- Production incident is declared in PagerDuty, which kicks off an Incident Workflow.
- The workflow creates a Zoom meeting, then creates a dedicated Slack channel for the incident, then adds the PagerDuty Advance Scribe Agent. Scribe joins the Zoom call and posts the live transcript to Slack.

Problem:
- The Scribe transcript is being posted to our `#alerts` channel (where all our alerts land), instead of the dedicated incident channel created by the workflow.

What I've already checked:
- Workflow action ordering is correct "Create a Slack Channel for an Incident" runs before "Add PagerDuty Advance Scribe Agent."
- Scribe Agent settings have no option to select a target Slack channel.
- The "Add PagerDuty Advance Scribe Agent" workflow action also has no channel/surface input.

Questions:
1. What determines which Slack channel/surface Scribe posts the transcript to? 
2. If we have `#alerts` mapped to the service via the Slack integration, would Scribe inherit that as its surface instead of the dedicated channel?
3. What's the recommended way to force the transcript to the dedicated incident channel?

 

1 reply

maria_yarotska
Forum|alt.badge.img
  • maria_yarotska
  • Community Manager 💚
  • July 9, 2026

Hey there,

Thank you for posting this – we just checked your setup, and there’s one small fix that should help the issue. 

You are using the Incident Workflow that gives you you more control, and triggers Scribe Agent once an incident starts – which is the way we would recommend. However, you also have the Global Toggle in Agents console. This is forcing Scribe Agent to join as soon as the incident conference bridge is added to the incident which, from what we can see, is being done before the dedicated incident channel is created, causing the unwanted behavior. 

The recommendation, since you’re already using incident workflows, is to go to Agents Console and disable the global toggle. Please let us know if this helps.

Terms & ConditionsAccessibility statement