{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/support.create-ticket-from-system/",
    "json": "https://www.anchorterminal.com/niches/support.create-ticket-from-system/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/support.create-ticket-from-system/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/support.create-ticket-from-system/index.min.md"
  },
  "markdown": "One company's 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| 1 | 19 | 21 | 7 | 4 |\n\n## What counts as done\n\nOne ticket exists per source event after the call, with requester and fields set, no auto-reply sent unless wanted, and a retry does not create a second ticket.\n\nHow agents ask for it: open a ticket for this bug report; log this chat as a ticket; create a ticket from the form submission; import these historical conversations\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.)**: POST /inboxes/{id}/imported_messages takes external_id (Front won't import two messages with the same one), sender, tags and assignee, and importing sends nothing to the customer.\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- **Chatwoot API (Chatwoot Inc.)**: Create New Conversation takes a contact source_id and an initial message, but no idempotency key or external id lookup is documented, so a retried create can duplicate.\n- **Crisp API + MCP (Crisp IM SAS)**: Create A New Conversation then a message works, and a message fingerprint avoids duplicate messages, but a retried conversation create has no idempotency key.\n- **Dixa (Dixa ApS)**: POST /v1/conversations and /conversations/import create conversations, and inbound messages take a client externalId, but the docs don't say a repeated externalId is refused.\n- **Drag (DragApp.com Ltd)**: POST /v2/card and MCP create_card make a card in a column, but no idempotency key or external id is documented.\n- **FreeScout (FreeScout)**: Create Conversation with imported true sends no email or auto-reply, but there is no idempotency key; only a timed-out call is documented as safe to retry.\n- **Freshdesk API + MCP (Freshworks Inc.)**: Create a Ticket takes requester and fields, but has no idempotency key; unique_external_id identifies contacts, not tickets. acc-17's free account was deleted and its widget broke.\n- **Gladly (Gladly Software, Inc.)**: Conversation items accept a client id and return 409 if it is in use, which prevents duplicates, but items created this way are not part of a conversation and are non-routable.\n- **Gorgias API + MCP (Gorgias Inc.)**: create_ticket logs a customer message and sends nothing by default, but message external_id is 'not used by Gorgias', so it is no idempotency key; a retry duplicates unless the agent lists by external_id first.\n- **Help Scout API + MCP (Help Scout PBC)**: Create Conversation and threads accept imported true so no email or notification goes out, but no idempotency key or external id is documented, so a retried create duplicates.\n- **HelpDesk (Text, Inc.)**: POST /v1/importedTickets imports without sending, and tickets carry an externalID, but the docs don't say a repeated externalID is refused and no idempotency key exists.\n- **Intercom API + MCP (Intercom, Inc. (with Intercom R\u0026D Unlimited Company in Ireland))**: POST /tickets takes a ticket type, contact by external_id and attributes, but the request has no idempotency key or external id for the ticket, so a retry can duplicate.\n- **Kustomer (Kustomer, LLC)**: Conversations and messages can be fetched by external id, so a retry can check first, but create takes no idempotency key and the check is not atomic.\n- **LiveAgent (Quality Unit, s. r. o.)**: Tickets can be created over the REST API, but no idempotency key or external id lookup was found, so a retry can duplicate.\n- **Missive API + MCP (Heliom Inc.)**: Create a message makes incoming messages in a custom channel and Create a post can start a conversation, but no idempotency key is documented, so a retry can duplicate.\n- **Plain API + MCP (Not Just Tickets Ltd)**: createThread takes a customer and threads can carry an externalId with a threadByExternalId lookup, but the id is unique per customer only and the docs don't say a duplicate create is refused; importThread skips autoresponders.\n- **Pylon API + MCP (Pylon Labs, Inc.)**: POST /issues takes requester, account, priority, tags and fields, but no idempotency key or external id is in the request, so a retry can duplicate.\n- **Zammad (Zammad GmbH)**: POST /api/v1/tickets takes customer, group and first article, and X-On-Behalf-Of acts for another user, but no idempotency key is documented, so a retry can duplicate.\n- **Zendesk Support API (Zendesk, Inc.)**: Tickets carry an external_id you can list by, but it is not enforced unique and create takes no idempotency key, so the agent must look up before creating; acc-05 and acc-06 describe the integration as costly.\n- **Zoho Desk (Zoho Corporation Private Limited)**: Create Ticket sets contact, subject and fields, but takes no idempotency key or external id, so a retry can duplicate.\n\n- not this job: Chatway MCP (Poptin Ltd): No tool creates a conversation or ticket from outside data; conversations start from the visitor's chat widget.\n- not this job: Landbot MCP server (Landbot): Landbot has no ticket object in the MCP server and no tool creates a conversation from outside data.\n\n## What stops agents finishing\n\n- no idempotency key so a retried create duplicates\n- creating a historical conversation emails the customer unless an import flag is set\n- widget or API removed when a free account is closed\n\n## Around it\n\nBefore: forms.submit, monitoring.alert, agent-harnesses.tool-call. After: support.triage-and-route.\n\n## Where this comes from\n\nWeight 7 of 100 in Customer support \u0026 helpdesk: 4 of 42 accounts (acc-05, 06, 07, 17); the oldest integration job and the one people describe abandoning\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/support.create-ticket-from-system.json, or the MCP tool get_use_case with id support.create-ticket-from-system. 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": "Create or update a ticket from another system",
        "url": ""
      }
    ],
    "description": "Create or update a ticket from another system: 1 companies fully do it, 19 with a limit, 21 carry the tag. Every listing in Customer support \u0026 helpdesk with the reason and a source.",
    "facts": null,
    "h1": "Create or update a ticket from another system",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/support.create-ticket-from-system/",
    "published": "",
    "section": "agents",
    "title": "Create or update a ticket from another system | Anchor Terminal",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/support.create-ticket-from-system/"
  },
  "tokens": {
    "markdown": 1700,
    "slim": 380
  },
  "version": 1
}
