Customer support automations
Notice the tickets that came back
Asks Jira weekly for tickets that were closed and then reopened, and posts them to Slack.
Add this automation
Free, and no card. It runs for real, five times.
What it does on a run
- 1Ask Jira what came back
- 2Look for the pattern behind them
- 3A ticket that came back is worth the team seeing
When it runs
Every Monday at 9am. You can change the schedule in plain words after you start it.
What it needs
JiraSlackConnected once, then reused by every automation that needs them.
Where it stops
It halts before the irreversible part and shows you what it is about to do. You see the message, the recipient and the data it read, and nothing is sent until you say so. Once you trust it, you can tell it to stop asking.
Free, and no card. It runs for real, five times.
Automations like this one
All 11 in Customer support- Sweep up the tickets nobody ownsAsks Jira each morning for open tickets with no assignee and posts them to Slack to be picked up.
- Find the tickets waiting on a replyAsks Jira each morning for open tickets nobody has touched since yesterday and posts them to Slack.
- Surface the work that is blockedAsks Jira each morning for issues flagged blocked and posts them to Slack with how long they have been stuck.
- Write the on-call handoverReads what was raised and what moved in Jira over the last day and posts a handover note to Slack.
- Find the sprint work that has stopped movingAsks Jira each morning for open sprint tickets untouched for three days and posts them to Slack.
- Sweep up the issues nobody ownsAsks Jira each morning for open issues with no assignee and posts them to Slack to be picked up.