{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/support.summarise-and-report/",
    "json": "https://www.anchorterminal.com/niches/support.summarise-and-report/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/support.summarise-and-report/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/support.summarise-and-report/index.min.md"
  },
  "markdown": "Four or more companies' docs show a full fit.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 7 | 14 | 21 | 12 | 6 |\n\n## What counts as done\n\nA summary that names the open questions, or a category table with counts, produced from paged calls without exceeding the rate limit, and written back as a note or left outside the helpdesk.\n\nMeasured, for our own tests: the summary is under 200 words.\n\nHow agents ask for it: summarise this thread; what are the top issues this week; categorise our ticket history; are we falling behind on tickets\n\n## Does the job\n\nThe docs show it meets the test above, and nothing we read says otherwise.\n\n- **Gorgias API + MCP (Gorgias Inc.)**: get_reporting_stats and ticket_pattern_breakdown group tickets by contact reason, messages carry stripped_text, and add_internal_note writes back.\n- **HelpDesk (Text, Inc.)**: About thirty report endpoints cover new tickets, status, response and resolution time, tickets page by cursor, and a private message writes the summary back. Calls are metered against the Text plan.\n- **Intercom API + MCP (Intercom, Inc. (with Intercom R\u0026D Unlimited Company in Ireland))**: Conversations page by cursor, reporting data exports run as jobs, and add_internal_note writes the summary back without reaching the customer.\n- **Kustomer (Kustomer, LLC)**: Search with field selection pages conversations, AI summaries can be fetched in batches, and notes write a summary back.\n- **Plain API + MCP (Not Just Tickets Ltd)**: Threads page by cursor with chosen fields, and notes write the summary back; the MCP server suggests precisely this summary prompt.\n- **Pylon API + MCP (Pylon Labs, Inc.)**: Issues and their messages page by cursor, search narrows by filter, and /issues/{id}/note writes the summary back as an internal note.\n- **Zendesk Support API (Zendesk, Inc.)**: Incremental ticket export and search export page to completion, search/count gives counts, and an internal note carries the summary back; acc-12 runs such a monitoring agent.\n\n## Does the job, with a limit\n\nIt does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.\n\n- **Chatway MCP (Poptin Ltd)**: The insights skill pages list-conversations at up to 100 and reads messages by cursor, with add-note for write-back, but it warns of sampling and pagination truncation, and Free keeps 30 days.\n- **Chatwoot API (Chatwoot Inc.)**: Paged conversation lists, messages and report endpoints (counts by inbox, label matrix) exist, and a private note can carry the summary, but cloud rate limits are unpublished and records have no field selection.\n- **Crisp API + MCP (Crisp IM SAS)**: Conversations and messages page through REST and a note carries the summary back, but pages stop at 50 and the daily token quotas limit how many conversations one run can read.\n- **Dixa (Dixa ApS)**: Messages, notes and activity logs are readable and a note writes back, but paging uses opaque pageKey at 10 requests a second per token, slow for thousands of conversations.\n- **Drag (DragApp.com Ltd)**: get_thread reads a thread, analytics tools give response times and daily activity, and add_comment writes back; how far list_threads pages was not documented.\n- **FreeScout (FreeScout)**: Conversations page up to 100 at a time with threads embedded, Get Report gives queue figures, and a note thread writes back; no rate limits are documented, so pacing depends on the operator's server.\n- **Freshdesk API + MCP (Freshworks Inc.)**: Conversations return body_text and a private note carries the summary, but ticket lists stop at 300 pages and closed tickets archive after 120 days of inactivity.\n- **Front API + MCP (FrontApp, Inc.)**: read_conversation returns the whole timeline and read_message strips quoted replies; add_comment writes the summary back. Bulk counts mean paging at 50 requests a minute on Starter.\n- **Gladly (Gladly Software, Inc.)**: The Export API sends conversations as daily files and a note can carry a summary back, but files are removed after 14 days and reports allow 10 calls a minute.\n- **Help Scout API + MCP (Help Scout PBC)**: Reports endpoints (volumes, productivity, drilldowns) and paged conversation lists cover the queue, and Create Note writes back, but reports need Plus or Pro and each v3 search counts double.\n- **LiveAgent (Quality Unit, s. r. o.)**: get_ticket_summary returns an AI summary on personal connections and add_note writes back, but v3 GET /tickets returns at most 10,000 tickets per filter and rate-limit responses are undocumented.\n- **Missive API + MCP (Heliom Inc.)**: Analytics reports, message and comment lists, and posts for writing a summary back exist, but message bodies come only from Get a Message, one at a time.\n- **Zammad (Zammad GmbH)**: POST /tickets/{id}/summarize returns a summary, but acc-29 hit JSON parse errors on German quotation marks and acc-30 truncation from a hardcoded 1,024 max_tokens, both open. Paging has hard per-page limits.\n- **Zoho Desk (Zoho Corporation Private Limited)**: Threads, metrics and counts are readable and a private comment carries the summary back, but lists page 50 at a time and deep offsets cost up to 100 credits a call against a daily allowance.\n\n- not this job: Landbot MCP server (Landbot): No conversation, transcript or reporting tool is in the tool list.\n\n## What stops agents finishing\n\n- model output rejected by the helpdesk's parser or truncated by a fixed token limit\n- pagination caps below the number of tickets wanted\n- each v3 search counts double against the limit\n\n## Around it\n\nBefore: support.research-context. After: knowledge.write-article, messaging.slack-notify.\n\n## Where this comes from\n\nWeight 12 of 100 in Customer support \u0026 helpdesk: 6 of 42 accounts (acc-11, 12, 13, 29, 30, 34); read-only MCP vendors name this as their first use case\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/support.summarise-and-report.json, or the MCP tool get_use_case with id support.summarise-and-report. Draft, read 2026-11-12 from public docs and first-hand accounts, not yet reviewed by a person.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Summarise tickets and report on the queue",
        "url": ""
      }
    ],
    "description": "Summarise tickets and report on the queue: 7 companies fully do it, 14 with a limit, 21 carry the tag. Every listing in Customer support \u0026 helpdesk with the reason and a source.",
    "facts": null,
    "h1": "Summarise tickets and report on the queue",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/support.summarise-and-report/",
    "published": "",
    "section": "agents",
    "title": "Summarise tickets and report on the queue | Anchor Terminal",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/support.summarise-and-report/"
  },
  "tokens": {
    "markdown": 1750,
    "slim": 380
  },
  "version": 1
}
