CHATBOTS

Cross-Region On-Call Handoff to Microsoft Teams

When a follow-the-sun rotation hands off between regions, this bot bundles open incidents and active alerts and posts a localized handoff briefing to the incoming region's…

CategoryChatbots
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerPagerDuty regional handoff eventPagerDutyPagerDuty
  • ActionFetch open + acknowledged incidentsPagerDutyPagerDuty
  • ActionPull active Datadog monitorsDatadogDatadog
  • LogicLocalize timestamps; flag stale items
  • OutputPost briefing card to incoming region's Teams channelMicrosoft Teams

What it does

For teams that follow the sun across time zones, this bot makes the region-to-region handoff explicit. As one region's coverage ends and another begins, it assembles the current incident and alert state and posts a briefing to the incoming region's Microsoft Teams channel, with timestamps converted to the new region's local time.

When to use it

Use this when on-call coverage rotates between geographic regions on separate Teams channels and the receiving region needs context in its own working hours. It removes the awkward overlap window where neither region is sure who owns what.

How it works

  1. 1PagerDuty fires the handoff event as coverage shifts to the next region's schedule.
  2. 2The bot fetches all open and acknowledged incidents tied to the global escalation policy.
  3. 3It pulls active Datadog monitors so the incoming region sees what is currently firing.
  4. 4A logic step adjusts every timestamp into the incoming region's local time zone and flags items older than one full shift.
  5. 5The briefing is formatted with severity, owner, and age columns.
  6. 6It is posted to the incoming region's Microsoft Teams channel as an actionable card.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect PagerDutyIncidents, on-call, escalations.
  2. 2
    Connect DatadogMetrics, traces, log search.
  3. 3
    Connect Microsoft TeamsChannels, chats, files.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.