10 scheduled AI tasks for service management teams

In brief

Most AI assistants, including Claude, ChatGPT, Copilot and Gemini, can now run a prompt on a schedule: every morning, every Monday or monthly. You write the instructions once, and a short report is waiting when you sit down.

The useful scheduled tasks are not clever. They take the reading and sorting nobody has time for, such as supplier news, standards updates and survey comments, and turn it into a short list a person can act on.

The idea for this article came from Brandon Gaille's [Top 25 Claude Scheduled Tasks with Prompts](https://aigeniuslab.substack.com/p/top-25-claude-scheduled-tasks-with) (AI Genius Lab, 12 October 2026), which sets out 25 scheduled tasks for small businesses. We asked what the equivalent list would look like for people who run services in IT, HR, facilities, finance or legal. The tasks and prompts below are our own.

One rule runs through all of them: the AI gathers and drafts, and a named person checks and decides.

The 10 tasks

1. Major incident and outage trend scan

How often: weekly, Monday morning.

Why it matters: other organisations' outages are free lessons. Public post-incident reviews show which failure patterns are common right now, such as expired certificates or third-party dependencies, before they reach you.

Sample prompt: "Find public outage reports and published post-incident reviews from the past 7 days involving [cloud platforms, SaaS tools or sectors we care about]. Give the date, what failed, the stated cause and a link. Group them by cause and end with three questions our problem manager should ask about our own services."

2. Supplier and SLA news watch

How often: weekly.

Why it matters: your service levels are only as good as your suppliers'. Acquisitions, end-of-support notices and outages all affect the promises you make.

Sample prompt: "Search for news from the past 7 days about these suppliers: [supplier list]. Report outages, acquisitions, licensing changes and end-of-support notices, with links. If nothing changed for a supplier, say so in one line."

3. ESM tools tracker: try, watch or ignore

How often: fortnightly.

Why it matters: most launches are noise. A short, sceptical review stops the team chasing every one, while still catching the one that matters.

Sample prompt: "Find announcements from the past 14 days about service management platforms and features for HR, facilities, finance or IT service delivery. List up to five. For each, say what it does in plain words and whether we should try it, watch it or ignore it, and why. Label anything that is only a marketing claim."

4. Service desk question mining from public forums

How often: weekly.

Why it matters: public questions about tools you also use are often the questions your users will ask next.

Sample prompt: "Search public forums for questions asked in the past 7 days about [tools we support]. List the 10 most common, with links, grouped by theme, and suggest a knowledge article title for each theme."

5. Monthly service review prep

How often: monthly, three working days before the review.

Why it matters: reviews go better when everyone arrives with the same facts, and a draft pre-read saves the service owner an evening.

Sample prompt: "Using the attached performance summary for [service], draft a one-page review pre-read: what went well, what missed target, open actions and three questions for the customer. Show where every figure came from."

6. Regulatory and standards changes

How often: monthly.

Why it matters: ITIL, ISO/IEC 20000 and, for financial services, the EU's Digital Operational Resilience Act (DORA) all shape what good looks like, and guidance updates are easy to miss.

Sample prompt: "Search official sources only, such as PeopleCert, ISO, the European supervisory authorities and [our national regulator], for updates published in the past 30 days about [ITIL, ISO/IEC 20000, DORA]. Give the source, date, a two-sentence summary and a link. Say clearly if you found nothing."

7. Knowledge base gap finder

How often: monthly.

Why it matters: if a request type keeps arriving with no article, people are working out the answer from scratch every time.

Sample prompt: "Compare the attached export of last month's ticket categories and short descriptions with the attached list of knowledge article titles. List the 10 most frequent request types with no matching article, with the ticket count for each. Do not include names, email addresses or ticket references in your answer."

8. CSAT and comment theme summary

How often: monthly, from an exported file.

Why it matters: the scores tell you something is wrong. The comments tell you what.

Sample prompt: "From the attached CSAT export, with personal details already removed, group the free-text comments into no more than six themes. For each, give how many comments mention it and two short quotes copied exactly. List any comment that does not fit a theme separately rather than forcing it in."

9. Events and CPD radar

How often: monthly, first week of the month.

Why it matters: events and CPD opportunities are scattered across dozens of sites, and a monthly list gives people time to make the case for budget.

Sample prompt: "List service management and ESM events, webinars and courses in the next 90 days in [UK and online], with date, organiser, cost and link. Flag any booking or speaker deadline in the next 30 days."

10. What changed in our tools this week

How often: weekly, Friday.

Why it matters: a renamed menu or a new default in a SaaS tool can generate a wave of tickets on Monday morning.

Sample prompt: "Check the official release notes for [our service desk platform, HR system, collaboration tools] for changes in the past 7 days. Describe each in plain words, say whether users, agents or administrators would notice, and link the source."

Before you automate: what to check

Scheduled tasks are low risk when they gather and summarise, and much riskier when they act.

Who reviews the output? Name a person for every task, not "the team". If nobody would notice a wrong answer, or a report that stopped arriving, the task is not ready.

What not to schedule. Do not schedule anything that acts or sends without a human in between: no emails to customers, no posts, no ticket updates, no changes to records. Keep the AI to drafting. And do not schedule anything involving personal data, such as named tickets, staff records or survey responses with names, unless your data protection lead has agreed the tool, the data and the purpose.

Spot confident-but-wrong summaries. AI summaries read well even when they are wrong. Watch for:

- figures with no source, or sources that do not say what the summary claims - links that are broken, or point to a home page rather than the article - old news presented as this week's - a tidy theme that no actual comment supports - "no changes found" when the tool simply could not reach the page

A simple habit helps: ask every prompt to link its sources and say when it found nothing, then check two items at random each time. If a task is wrong twice in a month, pause it and rewrite the prompt.

Start with one. Run the task that saves the most reading for a month before adding a second.

Get the full prompt pack

The full 12-prompt pack, with placeholders, set-up notes and a human check for each task, is coming to the toolkit on [ESM's Exchange](https://exchange.esm.institute). In the meantime, here are the two extra prompts.

11. Problem candidates from repeat incidents

How often: monthly.

Prompt:

> The attached file is last month's incident export with only category, configuration item or service, short description, opened date and resolution notes, and all personal details removed. Find groups of incidents that look like they share a cause, for example the same service, similar descriptions or similar fixes. List up to eight groups. For each, give the number of incidents, the date range, two example descriptions copied exactly, and one sentence on why they might be linked. Label each group "likely linked" or "possibly linked". Do not name a root cause.

Human check: the problem manager reviews each group with the resolver team before raising a problem record. The AI suggests candidates; people decide what is a problem.

12. Weekly service management reading list

How often: weekly.

Prompt:

> Search for articles, research and guidance published in the past 7 days about [enterprise service management, service desk practice, knowledge management, service level management, or other topics we care about]. Choose the five most useful for a practitioner audience, preferring independent and primary sources over vendor marketing. For each, give the title, publisher, date, a two-sentence summary and a link. If a piece quotes a statistic, name the original source of the statistic, or say "original source not given". Skip anything that only restates a press release.

Human check: whoever shares the list reads each piece before passing it on, and checks any statistic against its original source.

Tell us what you schedule

Tell us what you schedule, and what went wrong, in the [Service Desk & Support space](https://exchange.esm.institute/community/service-desk-support) on ESM's Exchange. The failures are often more useful than the successes.

Tags: ai-enablement, service-desk, esm, knowledge-management, continual-improvement

Sources

- https://aigeniuslab.substack.com/p/top-25-claude-scheduled-tasks-with