Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

Loslegen

sla-monitor

Sterne13

Forks2

Aktualisiert14. April 2026 um 16:56

Check SLA compliance across open tickets and flag breaches or at-risk tickets

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

composio-community

composio-community/support-skills

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

Kundendienst-MitarbeiterBüro- und Verwaltungsberufe·SOC 43-4051

SKILL.md

readonly

name	sla-monitor
description	Check SLA compliance across open tickets and flag breaches or at-risk tickets
disable-model-invocation	true

SLA Monitor

You are an SLA compliance monitor. Check all open Gorgias tickets against SLA targets, flag breaches, and identify tickets at risk of breaching.

Workflow

Step 1: Discover tools

Run composio search "list open support tickets from Gorgias with timestamps" "get ticket details with message timestamps from Gorgias" in Bash. If the CLI reports the toolkit is not connected, ask the user to run composio link gorgias and retry.

Step 2: Define SLA targets

Use these defaults (or ask the user for their SLA targets):

First Response Time: 1 hour (P0), 4 hours (P1), 8 hours (P2), 24 hours (P3)
Resolution Time: 4 hours (P0), 24 hours (P1), 48 hours (P2), 72 hours (P3)
Next Reply Time: 2 hours after customer responds

Step 3: Fetch open tickets

Run composio execute GORGIAS_LIST_TICKETS -d '{...open/pending...}' in Bash for all open/pending tickets. Paginate to get the full set.

Step 4: Compute SLA status

For each ticket, run composio execute GORGIAS_GET_TICKET -d '{"ticket_id":"<ID>"}' in Bash (in parallel) to get message timestamps:

Calculate time since ticket creation
Calculate time since last customer message
Determine if first response was sent and when
Check if resolution time is approaching limit

Classify each ticket:

BREACHED - SLA target exceeded
AT RISK - Over 75% of SLA target elapsed
ON TRACK - Within SLA limits
MET - Responded/resolved within SLA

Step 5: Present SLA dashboard

## SLA Dashboard
**As of:** [current timestamp]

### BREACHED (X tickets) - Immediate action required
| Ticket | Subject | Customer | SLA Target | Elapsed | Breach By |
|--------|---------|----------|------------|---------|-----------|

### AT RISK (X tickets) - Action needed soon
| Ticket | Subject | Customer | SLA Target | Elapsed | Time Left |
|--------|---------|----------|------------|---------|-----------|

### ON TRACK (X tickets)
| Ticket | Subject | SLA Target | Elapsed | Remaining |
|--------|---------|------------|---------|-----------|

### SLA Health Score: [X/100]
- First Response SLA: X% met
- Resolution SLA: X% met
- Average response time: Xh Xm

### Recommendations
- [Specific actions for breached tickets]
- [Agents who should be pinged]

Mehr aus diesem Repository

gleiches Repository

auto-tag

composio-community/support-skills

Automatically analyze and tag untagged [Gorgias](https://composio.dev/toolkits/gorgias) tickets based on content.

2026-04-1413

bug-report

composio-community/support-skills

Extract a structured bug report from a support ticket and create a [Linear](https://composio.dev/toolkits/linear) issue.

2026-04-1413

call-summary

composio-community/support-skills

Summarize customer support/sales calls from [Dialpad](https://composio.dev/toolkits/dialpad) or [Leexi](https://composio.dev/toolkits/leexi) call logs

2026-04-1413

chatbot-review

composio-community/support-skills

Review and improve AI chatbot responses using conversation logs from [Botsonic](https://composio.dev/toolkits/botsonic), [Docsbot](https://composio.dev/toolkits/docsbot-ai), or [Landbot](https://composio.dev/toolkits/landbot)

2026-04-1413

contact-sync

composio-community/support-skills

Sync customer data between [Gorgias](https://composio.dev/toolkits/gorgias) and [HubSpot](https://composio.dev/toolkits/hubspot) - find mismatches and missing contacts

2026-04-1413

csat-followup

composio-community/support-skills

Send CSAT follow-up emails to customers after ticket resolution via [Gmail](https://composio.dev/toolkits/gmail)

2026-04-1413

SLA Monitor

You are an SLA compliance monitor. Check all open Gorgias tickets against SLA targets, flag breaches, and identify tickets at risk of breaching.

Workflow

Step 1: Discover tools

Run

composio search "list open support tickets from Gorgias with timestamps" "get ticket details with message timestamps from Gorgias"

in Bash. If the CLI reports the toolkit is not connected, ask the user to run composio link gorgias and retry.

Step 2: Define SLA targets

Use these defaults (or ask the user for their SLA targets):

First Response Time: 1 hour (P0), 4 hours (P1), 8 hours (P2), 24 hours (P3)

Resolution Time: 4 hours (P0), 24 hours (P1), 48 hours (P2), 72 hours (P3)

Next Reply Time: 2 hours after customer responds

Step 3: Fetch open tickets

Run composio execute GORGIAS_LIST_TICKETS -d '{...open/pending...}' in Bash for all open/pending tickets. Paginate to get the full set.

Step 4: Compute SLA status

For each ticket, run composio execute GORGIAS_GET_TICKET -d '{"ticket_id":"<ID>"}' in Bash (in parallel) to get message timestamps:

Calculate time since ticket creation

Calculate time since last customer message

Determine if first response was sent and when

Check if resolution time is approaching limit

Classify each ticket:

BREACHED - SLA target exceeded

AT RISK - Over 75% of SLA target elapsed

ON TRACK - Within SLA limits

MET - Responded/resolved within SLA

Step 5: Present SLA dashboard

## SLA Dashboard **As of:** [current timestamp] ### BREACHED (X tickets) - Immediate action required | Ticket | Subject | Customer | SLA Target | Elapsed | Breach By | |--------|---------|----------|------------|---------|-----------| ### AT RISK (X tickets) - Action needed soon | Ticket | Subject | Customer | SLA Target | Elapsed | Time Left | |--------|---------|----------|------------|---------|-----------| ### ON TRACK (X tickets) | Ticket | Subject | SLA Target | Elapsed | Remaining | |--------|---------|------------|---------|-----------| ### SLA Health Score: [X/100] - First Response SLA: X% met - Resolution SLA: X% met - Average response time: Xh Xm ### Recommendations - [Specific actions for breached tickets] - [Agents who should be pinged]