Morning Gladly support task digest posted to Slack
Every weekday morning, get a short, prioritized Slack rundown of open Gladly follow-up tasks, most overdue first, so your support team knows what to tackle.
Every weekday at 8am, build a prioritized morning triage digest of our open Gladly follow-up tasks and post it to our support team's Slack channel. Run this on a cron schedule, Monday through Friday at 8am. Gladly follow-up tasks cannot be polled, so use the schedule to kick off each run.
First, pull the open follow-up tasks from Gladly with List Tasks, which returns tasks across the whole organization. Keep the tasks that are still open or unresolved and set aside anything already completed or closed.
Then have the agent organize what is left: group the tasks by their assigned agent and by age, and flag any task that is past its due date or that has gone untouched for more than 48 hours as needing attention. Sort everything so the most overdue items lead the digest.
Post the result to our support Slack channel using the Slack Bot integration's Send a Message action, so it posts as a bot rather than as a specific person. Start the message with the total count of open tasks. Then list the aging and overdue tasks in priority order, most overdue first. For each of those tasks include the customer name, the task subject, the due date, and the assignee so the team can see at a glance who should pick up what.
Keep the whole message short and scannable so a support lead can read it and triage the day in under a minute. Use clear Slack formatting with short lines or bullets and bold for the most urgent items, and avoid long paragraphs. This workflow only reads from Gladly and posts to Slack; it does not modify, close, or reassign any tasks.
Example output
Additional information
What does this prompt do?
- Every weekday at 8am, gathers all your open follow-up tasks from Gladly in one place.
- Groups them by assignee and by age, and flags anything overdue or untouched for more than 48 hours.
- Posts a short, scannable digest to your support Slack channel, leading with the most overdue work.
- Shows a total open-task count at the top and lists the customer, subject, due date, and owner for each aging task.
What do I need to use this?
- A Gladly account with API access
- A Slack workspace and a support channel where the digest should land
- A few minutes to set the run time and pick the channel
How can I customize it?
- Change when it runs, from 8am on weekdays to any time or days you like.
- Point it at a different Slack channel or a direct message.
- Adjust the aging threshold, for example flag tasks untouched for 24 or 72 hours instead of 48.
Frequently asked questions
When does the digest arrive?
Which tasks are included?
How does it decide what is urgent?
Can it post to a private Slack channel?
Does this change anything in Gladly?
Related templates
Every weekday at 8am, your billing team gets a Slack rundown of yesterday's failed Braintree charges, the revenue at risk, and who to chase first.
Every weekday morning, roll up your sprint's work items into a clear per-person standup summary and post it to your team's Slack channel before you meet.
Every three hours we scan Braintree for new disputes and chargebacks, open a tracked ticket with a tailored evidence checklist, and alert your team in Slack before the response deadline slips.
Every weekday morning we check your most important Databricks tables for freshness and data problems, and ping Slack only when something actually looks wrong.
Every Monday, automatically find which employee accounts on your company domain turned up in data breaches and get a plain-English briefing in Slack.
When a pipeline build fails, we post a tight Slack card naming who pushed, the likely cause, and a link to the build so on-call can triage in seconds.
Start every support day already triaged.
Let your team walk in to a ranked list of what needs attention instead of digging through Gladly one queue at a time.