Awish LogoAwish Logo
Log inBook a demoStart free

Customer Support · Risk & alerts

Incident Communication to Customers

Starts when: A production incident is declared or its status changes

Use this templateCustomise with AI

Free plan · Outcome verification included · You approve every connection

How it runs

Six stages, from the moment it starts to the checks that keep running afterwards.

  1. It starts

    A production incident is declared or its status changes

  2. Awish plans it and asks for each app

    The apps it needs are connected one at a time, with your permission, before anything runs.

  3. It does the work

    Exactly as the request below describes, across the connected apps.

  4. It stops where a person should decide

    Only use facts from the incident source of truth; require approval for cause, ETA or compensation statements.

  5. It verifies the outcome

    After each run, Awish checks that the ticket was routed, answered or escalated in time.

  6. It keeps monitoring

    Failures, silent failures and connection health are watched on every plan; anomalies, root cause and recommendations on Business.

The request it runs

This is what opens in chat when you use the template. Change any part of it before anything connects.

“Create an automation that manages escalated incident communication to customers end to end. Start it whenever a production incident is declared or its status changes. It should identify the affected customers and tickets, generate approved status updates from the incident facts, send and update the messages by channel, pause conflicting automated replies, and close the loop after resolution. Connect it with PagerDuty, Statuspage, Zendesk and Slack. Only use facts from the incident source of truth; require approval for cause, ETA or compensation statements.”
Apps it connects
  • PagerDuty
  • Statuspage
  • Zendesk
  • Slack

Monitoring included

What Awish watches once this template is running.

  • Outcome verificationEvery plan
  • Silent-failure detectionEvery plan
  • Connection healthEvery plan
  • Hours saved and ROIEvery plan
  • Anomaly detectionOn Business
  • Root-cause explanationOn Business
  • Recovery recommendationOn Business

How monitoring works

More Customer Support templates

See all Customer Support templates

Questions about this template

Can I change where it stops for approval?

Yes. Open the template in chat and say where you want it to stop. The plan updates before anything connects.

What if one of these apps is not connected yet?

Awish asks you to connect each app it needs, one at a time, before the workflow runs. You can decline any of them.

How does Awish know this workflow worked?

After each run it checks that the ticket was routed, answered or escalated in time, in the app where that should happen. If a run reports success but the result is missing, it flags a silent failure.

Run it on your own apps

It opens in chat with the request written. See the plan, approve each connection, and Awish verifies the outcome from the first run.

Use this templateCustomise with AI

Free plan · No credit card required