{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/support.research-context/",
    "json": "https://www.anchorterminal.com/niches/support.research-context/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/support.research-context/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/support.research-context/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| 6 | 15 | 20 | 15 | 7 |\n\n## What counts as done\n\nThe conversation thread or a filtered list of matching tickets, with only the fields asked for.\n\nMeasured, for our own tests: in at most two calls and under 4,000 tokens per ten results.\n\nHow agents ask for it: what has this customer asked us before; find tickets like this one; pull the conversation for ticket 4821; search tickets about login failures this month\n\n## Does the job\n\nThe docs show it meets the test above, and nothing we read says otherwise.\n\n- **Front API + MCP (FrontApp, Inc.)**: search_conversations takes full text plus inbox, teammate, team, tags, status and date filters; read_conversation pages the timeline with a limit; a read-only scope exists. Core search costs 40 per cent of the company limit.\n- **Intercom API + MCP (Intercom, Inc. (with Intercom R\u0026D Unlimited Company in Ireland))**: MCP search takes a query DSL with free text, and search_conversations filters by state, assignee and timing with cursor paging; REST conversation fetch has display_as plaintext. Permissions are granted per app.\n- **Kustomer (Kustomer, LLC)**: POST /v1/customers/search takes and/or criteria with queryContext conversation, date ranges and sort, and fields limits returned attributes to up to 20. Keys are limited to named org.permission roles.\n- **LiveAgent (Quality Unit, s. r. o.)**: search_tickets takes a full-text query plus status, department and agent filters, returns 10 to 50 compact tickets per page with a cursor, and get_ticket_messages pages 20 messages at a time.\n- **Plain API + MCP (Not Just Tickets Ltd)**: searchThreads runs full-text search over titles, message contents and customer names with a ThreadsFilter, and GraphQL returns only the fields selected. Machine-user keys carry named permissions.\n- **Zoho Desk (Zoho Corporation Private Limited)**: Search Tickets takes _all for full text plus status, priority, assignee, tag, contact and created or modified ranges, and a fields parameter trims each record. OAuth scopes can be read-only.\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)**: search-conversations, get-conversation and list-conversation-messages with cursor paging cover history, and inboxes and permissions are chosen at connect, but the Free plan keeps 30 days of history and field selection isn't documented.\n- **Chatwoot API (Chatwoot Inc.)**: Conversations List takes q (message text), status, labels, team and inbox, and Contact Conversations gives history, but there is no field selection and user tokens carry the full role.\n- **Crisp API + MCP (Crisp IM SAS)**: List Conversations takes search_query by text, segment or filter, and MCP has search_conversations, but pages are 20 to 50 whole conversations and the MCP token holds the website tier with no scopes; REST plugin tokens can be scoped.\n- **Dixa (Dixa ApS)**: POST /v1/search/conversations searches by text, filter or both, and end-user conversation lists exist, but records come whole. acc-31 hit a 404 on the MCP activity-log tool, fixed in July 2026.\n- **Drag (DragApp.com Ltd)**: search_threads searches across boards and filter_threads narrows by label, assignee or status, but the API key has full workspace access with no read-only option and field selection isn't documented.\n- **FreeScout (FreeScout)**: List Conversations filters by mailbox, folder, status, state, assignee, customer email and subject text, but not body text; embed defaults to threads, making records large, and keys have no scopes.\n- **Freshdesk API + MCP (Freshworks Inc.)**: Filter Tickets queries fields (status, priority, tag, agent, dates) but not body text, returns 30 a page for at most 10 pages, and excludes archived tickets; acc-18 calls the built-in search weak.\n- **Gladly (Gladly Software, Inc.)**: Customer profiles are found by email, phone or external id and their conversations listed, but there is no full-text conversation search, and lists stop at 100 conversations with no next page. Tokens have no scopes.\n- **Gorgias API + MCP (Gorgias Inc.)**: MCP search_tickets matches subjects, messages and customer details, but filtering by status or assignee needs a saved view, REST /api/search does not cover tickets, and the MCP has no read-only mode.\n- **Help Scout API + MCP (Help Scout PBC)**: List and Search Conversations take an advanced query over subject, body, email, tag, assignee and dates, and the MCP server is read-only by design, but threads are embedded whole and OAuth tokens have no scopes.\n- **HelpDesk (Text, Inc.)**: GET /v1/tickets takes query plus filters for status, requester, tags, priority, teams and date ranges with cursor paging, but no field selection, and a token inherits its creator's role.\n- **Missive API + MCP (Heliom Inc.)**: MCP Read conversations searches across accounts under a read-only grant, but REST List conversations must be filtered by mailbox, label or team and has no text query; REST tokens are personal with full access.\n- **Pylon API + MCP (Pylon Labs, Inc.)**: POST /issues/search takes fuzzy search_text intersected with a filter and cursor paging, and MCP has search_issues, but no field selection is documented and tokens have a role, not scopes.\n- **Zammad (Zammad GmbH)**: Endpoint, global and condition-based search run over Elasticsearch with paging, and a token can be narrowed to ticket.agent, but records have no field selection beyond expand off.\n- **Zendesk Support API (Zendesk, Inc.)**: GET /api/v2/search has a query syntax over status, dates, requester and tags, and OAuth scopes allow read-only, but records come whole with no field selection; acc-13 measured about 9KB a record.\n\n- not this job: Landbot MCP server (Landbot): No conversation or contact read tools are in the published tool list.\n\n## What stops agents finishing\n\n- search returns whole records at kilobytes each with no field selection\n- lists capped with no next page, such as 100 conversations\n- MCP token holds the whole workspace with no read-only option\n\n## Around it\n\nBefore: chat.user-asks, support.webhook-on-new. After: support.draft-reply-for-review, support.summarise-and-report, issue-tracking.create.\n\n## Where this comes from\n\nWeight 15 of 100 in Customer support \u0026 helpdesk: 7 of 42 accounts (acc-13, 14, 18, 31, 33, 34 and acc-12); the job most hosted MCP servers are limited to, and the one read-only servers from Help Scout and Intercom are built for\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/support.research-context.json, or the MCP tool get_use_case with id support.research-context. 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": "Read a customer's history before acting",
        "url": ""
      }
    ],
    "description": "Read a customer's history before acting: 6 companies fully do it, 15 with a limit, 20 carry the tag. Every listing in Customer support \u0026 helpdesk with the reason and a source.",
    "facts": null,
    "h1": "Read a customer's history before acting",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/support.research-context/",
    "published": "",
    "section": "agents",
    "title": "Read a customer's history before acting: who does it | Anchor Terminal",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/support.research-context/"
  },
  "tokens": {
    "markdown": 1900,
    "slim": 380
  },
  "version": 1
}
