Before creating a Salesforce account or contact
Your agent is about to create a new account or contact in Salesforce. Call Anchord first to check whether a matching record already exists. Anchord catches near-duplicates that Salesforce's own duplicate rules miss, and escalates ambiguous matches to a human via the Review Queue.
When to use this
- Your agent is about to create a new account or contact in Salesforce
- You're importing records from another CRM, spreadsheet, or pipeline into Salesforce
- You need to catch near-duplicates (e.g. "Acme Corp" vs "Acme Inc") that Salesforce doesn't flag
Endpoints to call
| Step | Endpoint | Purpose |
|---|---|---|
| 1 | POST /api/v1/ingest/batch | Ingest the record you intend to create |
| 2 | POST /api/v1/resolve/company | Check for existing match (or /resolve/person for contacts) |
| 3 | POST /api/v1/guard/write | Evaluate whether the create is safe |
Expected outcomes
resolved → allowed Record already exists in Anchord. Update the existing Salesforce record instead of creating a new one.
not_found → allowed No existing match. Safe to create the new account or contact in Salesforce.
needs_review Near-duplicates found (e.g. "Acme Corp" and "Acme Inc" both score above threshold). Do not create. Escalate to a human.
blocked Entity has unresolved conflicts or missing links. Do not create until the issue is resolved.
What the agent should do next
If resolved + allowed: The record already exists. Use the AnchorID to find the matching Salesforce record and update it instead of creating a duplicate.
If not_found + allowed: No match exists. Proceed with the Salesforce create.
If needs_review: Do not create. Store the attempt_id and link the user to the Review Queue.
If blocked: Do not create. Log the blocks array and surface the issue.