CUSTOMER SUPPORT
Fan a confirmed PagerDuty incident out to every customer channel at once
When a PagerDuty incident is triggered and acknowledged, it fans a single approved status message out to your in-app banner, status page, and Discord community so all cohorts see…
How it runs
The automated pipeline, trigger to output.
- TriggerPagerDuty incident triggered and acknowledgedPagerDuty
- LogicFilter to incidents above severity floor
- ActionPost in-app status bannerIntercom
- ActionPublish status page banner via HTTPHTTP webhook
- OutputPost community update to DiscordDiscord
What it does
It waits for a PagerDuty incident to be triggered and acknowledged, then takes one canonical status message and broadcasts it to every customer-facing surface in parallel. Customers across in-app, status page, and community all see a consistent acknowledgement, killing the duplicate-report wave at the source.
When to use it
Use it when an on-call engineer has already confirmed a real incident and you want a one-click, multi-channel announcement instead of copy-pasting the same message into three places under pressure.
How it works
- 1A PagerDuty incident trigger fires on triggered-and-acknowledged events via webhook.
- 2A logic step filters to incidents above a severity floor so low-priority pages stay quiet.
- 3An action posts the in-app status banner through Intercom.
- 4An HTTP action publishes the same message to the status page provider.
- 5An action posts a community update to Discord.
- 6The flow records each delivery so a later resolve event can clear all surfaces together.
Set it up
What you configure once, before turning it on.
- 1Connect PagerDutyIncidents, on-call, escalations.
- 2Connect IntercomConversations, contacts, articles.
- 3Connect HTTP webhookTrigger any URL on agent actions.
- 4Connect DiscordCommunity channels + voice + bots.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Customer Support workflows
Send a tailored Loom onboarding sequence on Front first-reply
When a new customer's first email lands in Front, this picks the Loom onboarding walkthroughs matching their plan and use case, builds a friendly sequenced reply.
Suggest the right Loom video by classifying Intercom message intent
Reads each new inbound Intercom conversation, classifies what the customer is trying to do, and surfaces the best-matching Loom walkthrough to the agent as an internal note.
Draft personalized fix-live replies for support to review
When a Sentry issue resolves, an agent reads each linked ticket's full thread and drafts a tailored 'your fix is live' reply per requester.
Close the loop with requesters when a Linear bug moves to Done
When a Linear issue created from a support escalation moves to Done after deploy, look up the originating Zendesk tickets and notify each requester that their reported bug is…
Reopen and notify Front conversations when their bug fix deploys
When a deploy resolves a Sentry issue, find the snoozed or closed Front conversations linked to it, reopen them, and send the customer a reply that the fix is now live.
Tell Intercom users their reported bug shipped after a Vercel deploy
On a successful Vercel production deployment, match the release's resolved Sentry issues to Intercom conversations and message each affected user that their reported issue is…
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.