# Read a customer's history before acting

> 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 & helpdesk with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/support.research-context/
- Markdown: https://www.anchorterminal.com/niches/support.research-context/index.md (~1,900 tokens)
- Slim: https://www.anchorterminal.com/niches/support.research-context/index.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/support.research-context/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

Four or more companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 6 | 15 | 20 | 15 | 7 |

## What counts as done

The conversation thread or a filtered list of matching tickets, with only the fields asked for.

Measured, for our own tests: in at most two calls and under 4,000 tokens per ten results.

How 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

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **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.
- **Intercom API + MCP (Intercom, Inc. (with Intercom R&D 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.
- **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.
- **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.
- **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.
- **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.

## Does the job, with a limit

It 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.

- **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.
- **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.
- **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.
- **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.
- **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.
- **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.
- **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.
- **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.
- **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.
- **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.
- **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.
- **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.
- **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.
- **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.
- **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.

- not this job: Landbot MCP server (Landbot): No conversation or contact read tools are in the published tool list.

## What stops agents finishing

- search returns whole records at kilobytes each with no field selection
- lists capped with no next page, such as 100 conversations
- MCP token holds the whole workspace with no read-only option

## Around it

Before: chat.user-asks, support.webhook-on-new. After: support.draft-reply-for-review, support.summarise-and-report, issue-tracking.create.

## Where this comes from

Weight 15 of 100 in Customer support & 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

As 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.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
