{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/crm.find-record/",
    "json": "https://www.anchorterminal.com/niches/crm.find-record/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/crm.find-record/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/crm.find-record/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 | 27 | 11 | 7 |\n\n## What counts as done\n\nThe matching record ids across contacts, companies and deals, or an explicit none; current open records are not hidden by default filters; a just-created record is findable.\n\nMeasured, for our own tests: the ids come in one or two calls, and a just-created record is findable within 10 seconds.\n\nHow agents ask for it: is this person already in the CRM; find the lead with this phone number; which deal is this email about; look up Acme's open opportunities\n\n## Does the job\n\nThe docs show it meets the test above, and nothing we read says otherwise.\n\n- **Relaticle (Relaticle, Inc.)**: search spans companies, people, opportunities, tasks and notes, phones are stored as E.164 and match in any format, and emails ignore case, but no indexing delay after a write is stated.\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- **Affinity (Project Affinity, Inc.)**: Separate search tools for persons, companies and opportunities, plus a semantic search endpoint; the search endpoints are beta and no indexing delay after a write is stated.\n- **Attio API + MCP (Attio Limited)**: search-records does full-text search across people, companies and deals by name, email or domain in one call, but phone normalisation and any indexing delay after a write are not stated.\n- **Breakcold (Logike SAS)**: records_list takes a search term and inbox search matches names, emails and phone numbers, but whether records search spans every object type, normalises phones, or lags writes is not stated.\n- **Capsule CRM (Zestia Limited)**: list_contacts filters on email, name and custom fields with is and contains operators, and REST has separate party, opportunity and project searches; there is no single cross-object search and no indexing delay is stated.\n- **Close API + MCP (Elastic Inc)**: find_contacts matches exact emails and secondary entries, normalises phones to the user's country, and list_objects spans leads, contacts and opportunities, but no indexing delay after a write is stated.\n- **Copper API (Copper CRM, Inc.)**: Per-entity search endpoints with documented phone normalisation (partial and fuzzy), and fetch person by email, but no single search across people, companies and opportunities and no stated indexing delay.\n- **Microsoft Dynamics 365 Sales (Microsoft Corporation)**: search_data searches structured and unstructured data across tables and read_query runs SQL SELECT, but search_data is billed per use in Copilot Credits and no indexing delay is stated.\n- **folk API + MCP (Folk Inc.)**: Separate search tools for people, companies and objects filter on emails and phones with eq and like, but there's no single cross-object search, no phone normalisation is stated, and no indexing delay is given.\n- **Freshsales API (Freshworks Inc.)**: /api/search spans leads, contacts, accounts and deals in one call and /api/lookup matches an exact email, but results stop at 100 and phone normalisation and indexing delay aren't stated.\n- **HubSpot API + MCP (HubSpot, Inc.)**: search_crm_objects filters any object type with up to five filter groups, on the CRM search API with no vector search, and a17 shows search lagging a fresh write by seconds.\n- **Nutshell (Nutshell, Inc.)**: Separate MCP searches for leads, companies and people, following the web app's visibility rules; no cross-object search, phone normalisation or indexing delay is documented.\n- **Payani AI (Payani Media LLC)**: Contacts, companies and deals can be looked up, but the tool list sits behind OAuth, so search fields, matching rules and indexing delay can't be read.\n- **Pipedrive API + MCP (Pipedrive Inc.)**: /itemSearch searches deals, persons, organisations and leads in one call with exact_match, but search has its own 10-requests-per-2-seconds limit, and a24 shows a community MCP hiding current deals behind default filters.\n- **Salesflare (Salesflare BVBA)**: /contacts filters by email, phone_number and domain and /accounts by domain, but each object is searched separately and phone normalisation and indexing delay aren't stated.\n- **Salesforce API + MCP (Salesforce, Inc.)**: A find tool sits beside soqlQuery in the standard servers (a36), but a12 shows a voice agent failing to match leads by phone number, and the search docs could not be read.\n- **Streak API + MCP (Rewardly, Inc.)**: The MCP searches pipelines, boxes, contacts and organisations, but how search matches emails or phones and any indexing delay are not documented, and the tool list isn't published.\n- **SugarAI (SugarCRM) (SugarAI Software Inc.)**: /globalsearch searches across modules and /:module/filter takes exact filters, but the index is Elasticsearch with an admin-set refresh interval, so a fresh record can lag, and phone normalisation isn't stated.\n- **Twenty API + MCP (Twenty.com PBC)**: find_records filters any object and direct mode adds per-object find tools, but each object is searched separately and phone normalisation and indexing delay aren't documented.\n- **Zoho CRM (Zoho Corporation Private Limited)**: Search takes email and phone across every email and phone field, states its default filters (non-converted, approved only) and returns more_records, but searches one module at a time and documents an indexing delay right after a write.\n\n## What stops agents finishing\n\n- search hides current records behind undocumented default filters (a24)\n- phone or email formats not normalised, so lookups miss (a12)\n- search index lags writes (a17)\n\n## Around it\n\nBefore: voice-agents.tool-call-mid-call, personal-assistants.inbox-triage-draft, support.research-context. After: crm.upsert-contact, crm.log-activity, crm.move-deal.\n\n## Where this comes from\n\nWeight 11 of 100 in CRM \u0026 customer platforms: 7 of 48 accounts (a04, a11, a12, a17, a20, a24, a35); other maps call this crm.lookup or crm.contact-lookup\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/crm.find-record.json, or the MCP tool get_use_case with id crm.find-record. Draft, read 2026-11-15 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": "Find the right record before acting",
        "url": ""
      }
    ],
    "description": "Find the right record before acting: 1 companies fully do it, 19 with a limit, 27 carry the tag. Every listing in CRM \u0026 customer platforms with the reason and a source.",
    "facts": null,
    "h1": "Find the right record before acting",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/crm.find-record/",
    "published": "",
    "section": "agents",
    "title": "Find the right record before acting: who does it | Anchor Terminal",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/crm.find-record/"
  },
  "tokens": {
    "markdown": 1750,
    "slim": 380
  },
  "version": 1
}
