Zendesk Customer Context

Ticket history, requester context

16 stars

Best use case

Zendesk Customer Context is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Ticket history, requester context

Teams using Zendesk Customer Context should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/zendesk-customer-context/SKILL.md --create-dirs "https://raw.githubusercontent.com/diegosouzapw/awesome-omni-skill/main/skills/testing-security/zendesk-customer-context/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/zendesk-customer-context/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How Zendesk Customer Context Compares

Feature / AgentZendesk Customer ContextStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Ticket history, requester context

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

## Zendesk Customer Context

When gathering customer context from Zendesk:

- Search tickets by requester (email or id) to see prior conversations.
- Use get ticket details to read full thread and internal notes.
- Summarize ticket history (open/closed, dates, subjects) before answering or escalating.
- When the user asks about a specific ticket, fetch details and summarize key points and status.
- Use help center search when the request is about documentation or known issues.

## Step-by-step instructions

1. For “context for customer X”: search tickets by requester (email or id); get details for the most relevant tickets.
2. Summarize ticket history: open vs closed, dates, subjects, and key resolution or escalation points.
3. For a specific ticket: get ticket details and summarize status, requester, and main comments/notes.
4. When the user asks about docs or known issues: search help center and cite articles in the summary.

## Examples of inputs and outputs

- **Input**: “What’s the ticket history for john@example.com?”  
  **Output**: Short list: ticket IDs, subjects, status, dates; optionally one line per ticket (e.g. “resolved”, “escalated”).

- **Input**: “Summarize ticket 12345.”  
  **Output**: Status, requester, subject, and key points from the thread and internal notes; from get ticket.

## Common edge cases

- **No tickets for requester**: Say “No tickets found for [email/id]” and suggest checking spelling or subdomain.
- **Ticket not found**: Say “Ticket [id] not found” and suggest checking ID or permissions.
- **Many tickets**: Summarize the most recent or relevant (e.g. open first, then recent closed); do not dump full content.
- **API/oauth error**: Report Zendesk error and suggest reconnecting or retrying.

## Tool usage for specific purposes

- **Search tickets (by requester)**: Use to find all tickets for a customer (email or id) for history and context.
- **Get ticket**: Use to read full thread and internal notes for one ticket before summarizing or escalating.
- **Search help center**: Use when the question is about documentation or known issues to cite in the summary.

Related Skills

customer-health-scorecard

16
from diegosouzapw/awesome-omni-skill

Create or update a customer health scorecard

context-session-end

16
from diegosouzapw/awesome-omni-skill

AI behavioral guideline for autonomously detecting work session boundaries and proposing updates to current_focus.md. The AI monitors conversation flow for natural breakpoints and acts without explicit invocation.

ai-context

16
from diegosouzapw/awesome-omni-skill

Generates AI IDE context files (AGENTS.md, CLAUDE.md, .cursorrules, copilot-instructions.md) from codebase analysis. Creates project-specific instructions for AI coding assistants so they understand conventions, architecture, and workflows. Use when setting up AI tool context for a repository.

_context-ack

16
from diegosouzapw/awesome-omni-skill

在每次回复中使用固定前缀并列出本次实际参考的指令/文件,便于校验是否遵循上下文与规则。

customer-discovery

16
from diegosouzapw/awesome-omni-skill

Find where potential customers discuss problems online and extract their language patterns. Provides starting points for community research, not exhaustive coverage.

agent-context-generator

16
from diegosouzapw/awesome-omni-skill

Generate project-level AGENTS.md guides that capture conventions, workflows, and required follow-up tasks. Use when a repository needs clear agent onboarding covering structure, tooling, testing, task flow, README expectations, and conventional commit summaries.

cdd-gather-context

16
from diegosouzapw/awesome-omni-skill

新規機能・複数ファイル変更前にコンテキスト収集

using-context7-for-docs

16
from diegosouzapw/awesome-omni-skill

Use when researching library documentation with Context7 MCP tools for official patterns and best practices

Tero Voice Project Context

16
from diegosouzapw/awesome-omni-skill

Load full project context, tech stack, status, and guidelines for the AI Receptionist SaaS project

project-context-discovery

16
from diegosouzapw/awesome-omni-skill

Discover project structure, package managers, test frameworks, and automation without hardcoded assumptions

moai-context7-lang-integration

16
from diegosouzapw/awesome-omni-skill

Enterprise-grade Context7 MCP integration patterns for language-specific documentation access with real-time library resolution and intelligent caching

init-context

16
from diegosouzapw/awesome-omni-skill

Analyze the codebase and generate context rules for Cursor. Use when setting up or populating .cursor/rules/ files.