Customer support automations
Hand engineering the bugs customers found
Collects the bugs raised in Jira this week and emails engineering a read on what customers are hitting.
Add this automation
Free, and no card. It runs for real, five times.
What it does on a run
- 1Get this week of bugs
- 2Group them the way engineering will fix them
- 3Send it to the people who can fix them
When it runs
Every Thursday at 4pm. You can change the schedule in plain words after you start it.
What it needs
JiraGmailConnected 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- Turn the mail that needs work into ticketsReads the unanswered support mail and opens a Jira issue for each one, after you have seen the list.
- Escalate the urgent tickets that have been sitting for daysAsks Jira for high-priority tickets opened more than three days ago and still open, and emails you the list.
- Read the week in supportAsks Jira for everything raised in the last seven days and emails you what people were actually asking about.
- Notice the tickets that came backAsks Jira weekly for tickets that were closed and then reopened, and posts them to Slack.
- 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.