omnichannel-helpdesk-ticket-routing

omnichannel-helpdesk-ticket-routing is a skill for Claude Code, Codex from hamzabellouch/agent-skills. It costs 87 tokens per session (1,138 once invoked), scanned A, original, MIT.

A guide to routing customer-support requests from email, chat, SMS, and webhooks into helpdesk systems. It covers ticket classification, service deadlines, and assigning work to suitable agents.

In plain words
What is it for?
Use it to normalise incoming tickets, remove duplicates, apply priority and service-level rules, and route work by agent skills, language, shift, or workload.
Why use it?
It reduces manual sorting and helps ensure urgent or specialised requests reach the right person within the required response and resolution times.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to normalise incoming tickets, remove duplicates, apply priority and service-level rules, and route work by agent skills, language, shift, or workload.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/hamzabellouch/agent-skills/omnichannel-helpdesk-ticket-routing
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add hamzabellouch/agent-skills --skill omnichannel-helpdesk-ticket-routing
Clone the repo
git clone --depth 1 https://github.com/hamzabellouch/agent-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for omnichannel-helpdesk-ticket-routing

README.md
[![agentmods](https://agentmods.dev/badge/skills/hamzabellouch/agent-skills/omnichannel-helpdesk-ticket-routing/github.svg)](https://agentmods.dev/skills/hamzabellouch/agent-skills/omnichannel-helpdesk-ticket-routing)
Your own site
<a href="https://agentmods.dev/skills/hamzabellouch/agent-skills/omnichannel-helpdesk-ticket-routing"><img src="https://agentmods.dev/badge/skills/hamzabellouch/agent-skills/omnichannel-helpdesk-ticket-routing/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for omnichannel-helpdesk-ticket-routing

Your own site · 80×15
<a href="https://agentmods.dev/skills/hamzabellouch/agent-skills/omnichannel-helpdesk-ticket-routing"><img src="https://agentmods.dev/badge/skills/hamzabellouch/agent-skills/omnichannel-helpdesk-ticket-routing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 87 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,138 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00087 $0.01138
Opus 5.5 $0.00035 $0.00455
Sonnet 5.5 $0.00017 $0.00228
Haiku 4.5 $0.00009 $0.00114

Measured 18d ago against content hash cf86a63ff514, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

omnichannel-helpdesk-ticket-routing scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 18d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Business/Customer_Operations_and_Support/omnichannel-helpdesk-ticket-routing/SKILL.md · 147 lines

How it starts

The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Omnichannel Helpdesk & Ticket Routing Skill Guide

This skill provides architectural patterns, state machine designs, and automated routing logic for high-volume customer support operations.


1. Ticket Lifecycle & Routing State Machine

[ Incoming Ingestion ] (Email / Chat / WhatsApp / Webhook)
             |
             v
[ Normalization & Deduplication Layer ]
             |
             v
[ Ticket Classifier & SLA Policy Attacher ]
  |-- Calculate Response SLA (e.g., P1 = 15m, P2 = 1h, P3 = 4h)
  |-- Tag Tier: VIP / Standard
             |
             v
[ Skill-Based Routing Engine ]
  |-- Match Agent Language, Product Domain, and Shift Status
  |-- Distribute via Round-Robin or Least-Loaded Capacity
             |
             v
[ Assigned to Agent / Auto-Resolved via AI Assistant ]

2. Production Code Implementations

A. Skill-Based Round-Robin Routing Engine (Python)

from dataclasses import dataclass, field
from datetime import datetime, timezone
from enum import Enum
import heapq


class Priority(Enum):
    URGENT = 1
    HIGH = 2
    NORMAL = 3
    LOW = 4


@dataclass
class Agent:
    id: str
    name: str
    skills: set[str]
    active_ticket_count: int = 0
    max_capacity: int = 5
    is_online: bool = True

    def is_eligible(self, required_skills: set[str]) -> bool:
        return self.is_online and (self.active_ticket_count < self.max_capacity) and required_skills.issubset(self.skills)


@dataclass
class Ticket:
    id: str
    priority: Priority
    required_skills: set[str]
    customer_id: str
    created_at: datetime = field(default_factory=lambda: datetime.now(timezone.utc))
    assigned_agent_id: str | None = None


class TicketRouter:
    def __init__(self, agents: list[Agent]):
        self.agents = agents

    def route_ticket(self, ticket: Ticket) -> Agent | None:
        """Finds eligible agent with minimum active ticket count (Least-Loaded)."""
        eligible_agents = [
            agent for agent in self.agents
            if agent.is_eligible(ticket.required_skills)
        ]

        if not eligible_agents:
            return None  # Enqueue to backlog / fallback queue

        # Sort by active tickets ascending
        selected_agent = min(eligible_agents, key=lambda a: a.active_ticket_count)
        selected_agent.active_ticket_count += 1
        ticket.assigned_agent_id = selected_agent.id
        return selected_agent

Read the full file on GitHub · 147 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 18d ago First seen · 147 lines · 87 tokens per session scan A cf86a63ff514

Subscribe to this mod's changes

omnichannel-helpdesk-ticket-routing is a skill published in the GitHub repository hamzabellouch/agent-skills (8 stars, last pushed today), licensed MIT. It adds 87 tokens to every session and 1,138 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-29.

Related

Other skills, from other repositories

spec-create

Create a structured feature specification with self-contained task files organized into parallel execution batches. Use this skill when the user says "create a spec", "plan this feature", "write up an implementation plan", "break this into tasks", or after any planning conversation where the user wants to capture…

benjaminthomas/spec-driven-dev · 118 tokens

polya-plan

Phase 2 of the Pólya Heuristic Coder: Devising a Plan, Land and Expand Strategy, Vertical Tracer Bullets, Expand-Contract Pattern, Contingency Plan B, Task Sizing, and The Pause Rule (docs/plan/{slug}-plan.md).

GulajavaMinistudio/awesome-copilot-id · 63 tokens

to-prd

Optional Phase 0.5 of the Pólya Heuristic Coder: Product Requirements Document (PRD) detailing User Stories, SMART Acceptance Criteria, Personas, and Business Goals.

GulajavaMinistudio/awesome-copilot-id · 41 tokens

architectural-engineering-manager

Use when a task needs the judgment of an Architecture/Engineering firm or department manager — pricing a project fee (lump sum vs. hourly vs. % of construction cost), staffing a project against backlog, evaluating scope creep on a fixed-fee job, managing professional liability exposure, or deciding whether to pursue a…

wonsukchoi/domain-experts · 73 tokens

compensation-benefits-manager

Use when a task needs the judgment of a Compensation and Benefits Manager — designing or evaluating a pay structure/leveling system, benchmarking compensation against market, deciding on a benefits package tradeoff, or auditing for pay equity issues. Narrower and more specialized than the broader hr-people-manager…

wonsukchoi/domain-experts · 72 tokens

computer-systems-analyst

Use when a task needs the judgment of a Computer Systems Analyst — running requirements elicitation and gap analysis against a target system, writing a feasibility study for a build-vs-buy-vs-customize decision, designing a system integration approach (point-to-point vs middleware vs API-led), scoping data-migration…

wonsukchoi/domain-experts · 85 tokens