Claude CRM Integration: Setup and 25 Prompts That Run Your Pipeline

Most guides to a Claude CRM integration stop once the connector shows up. This one covers setup quickly, then spends most of its time on what comes next: what to ask, how to phrase it so Claude touches the right record, and how to check its work. If you want the background on MCP itself or need ChatGPT and Grok steps too, start with our pillar guide on how to connect Claude, ChatGPT or Grok to your CRM.

What a Claude CRM integration actually changes

Without a connector, Claude only knows what you paste into the chat. You copy a customer's history out of the CRM, ask for a follow-up draft, then copy the result back. It works, but you're the integration.

With a connector, Claude calls the CRM's tools directly through the Model Context Protocol, the open standard Anthropic introduced in 2024 for connecting AI assistants to software. You ask a question, Claude picks the right tool (search contacts, list tasks, update a ticket), runs it under your login, and answers from the actual data. Here's what that means in practice with Argento:

That last row matters more than it looks. A misread instruction can at worst edit a record, which you can fix. It can't remove a hundred contacts.

Setting up a Claude CRM connection in five minutes

These are the exact steps from our Help Center article on connecting Claude. Each person on your team does this for their own account; there's nothing for an Argento admin to configure first.

1. Copy the connector URL. In Argento CRM, open Settings, expand MCP Server, and select Copy next to https://app.argentocrm.com/mcp.
2. Add it in Claude. Go to Settings → Connectors → Add custom connector and paste the URL. Name it something obvious, like "Argento CRM." (As of October 2026, some versions of Claude label this area Customize → Connectors, with an Add button that offers "Add custom connector.")
3. Sign in. A sign-in window opens. Use the same email and password you use for Argento CRM and approve the connection.
4. Turn it on in a chat. In a new conversation, open the + menu, choose Connectors, and make sure Argento CRM is toggled on.

Two plan details worth knowing, from Anthropic's custom connector guide as of October 2026: custom connectors work on Claude's Free, Pro, Max, Team and Enterprise plans, but Free accounts are limited to one custom connector. On Team and Enterprise, an owner adds the connector in organization settings first, and members then select Connect.

The first ten minutes: test before you trust

Before asking Claude to change anything, ask it things you already know the answer to. If the answers match the app, you're connected to the right workspace with the right permissions.

1. "Give me an overview of my workspace." Compare the counts against what you see in Argento.
2. "List contacts at [a company you know well]." Check nobody is missing.
3. "What ticket statuses does this workspace use?" This tells you the exact words Claude will use when it updates a status.
4. Create one throwaway task: "Create a task called Test connector, due tomorrow, assigned to me." Then find it in the app.
5. Open Settings → MCP Server and look at Recent Claude activity. Your test task should be there.

That's it. You've checked reading, writing and the audit trail. Mark the test task done (Claude can't delete it, which is the point).

25 prompts that run your pipeline

These are grouped by when in the day you'd use them. Swap in your own company names, people and status words. They all stay inside what the connector can do: search and filter, summarize, pull profiles, create and update records, and manage subtasks.

Morning: what needs me today (1–5)

1. "Give me an overview of my workspace: open tickets, tasks due today, overdue tasks, active projects and open deals."
2. "Which of my tasks are overdue? Sort by how long they've been overdue."
3. "List tasks due before Friday assigned to me, grouped by company."
4. "Which open tickets haven't moved out of New? Who are they assigned to?"
5. "From everything open, pick the three follow-ups I should do first and tell me why."

Before a call (6–9)

6. "Show me everything on file for Northside Plumbing."
7. "Summarize Northside Plumbing in five bullets: who we talk to, what's open, what's overdue, and the last thing we promised them."
8. "Which contacts at Northside Plumbing don't have a phone number or job title?"
9. "Is there a knowledge base article on our warranty process? Summarize the steps so I can explain them on the call."

After a call: logging without forms (10–15)

10. "Add a contact: Dana Whitfield, office manager at Henderson Roofing, dana@example.com."
11. "Create a task to send Dana the revised quote, due Thursday, assigned to me, linked to Henderson Roofing."
12. "Set Henderson Roofing's lifecycle stage to Opportunity and Dana's lead status to Connected."
13. "Add to Henderson Roofing's notes: they want the second crew start date in writing before signing."
14. "Move the Henderson Roofing deal to the next stage in our pipeline and add a subtask to confirm the start date."
15. "Draft a follow-up email to Dana that references what's open on her account. Don't send anything; I'll review it."

Prompt 15 is a drafting job, not a CRM action. Claude writes the text in the chat using the account history; you copy it into your email.

Support tickets (16–19)

16. "Create a ticket for Cedar Valley Dental: front desk can't log in to the patient portal. Priority high, assigned to Priya."
17. "Move the Cedar Valley login ticket to Waiting on client and add a subtask to chase their IT contact."
18. "List every open ticket for Cedar Valley Dental with its subtasks and which ones are ticked off."
19. "List every ticket in Waiting on client, with the company and who owns it."

Projects and handoffs (20–22)

20. "Create a project for the Henderson Roofing job, linked to the company, and add subtasks: site survey, materials order, crew schedule, final walkthrough."
21. "Tick off site survey on the Henderson project and reword materials order to say 'materials order: confirm shingle color first.'"
22. "Which active projects have no subtasks completed yet?"

End of week: cleanup and review (23–25)

23. "Find contacts that aren't linked to any company."
24. "List tasks with no due date and suggest one for each based on what they're about. Don't change anything yet."
25. "List open tasks and tickets by person so I can see who's overloaded going into next week."

Notice the phrase "don't change anything yet" in prompt 24. When a request could touch many records, ask Claude to propose first and apply second. It costs one extra message and saves you from a batch of edits you didn't want.

A day with a Claude CRM, start to finish

Here's an example of how it fits together. Say you run a four-person commercial cleaning company. You sell, Jamie runs the crews, and two team leads handle the sites.

7:45 a.m. Over coffee you ask for the workspace overview (prompt 1). Claude reports two overdue tasks, one of them a bid for a property management company that's three days late. You ask for the full profile on that company. It shows the facilities contact, an open ticket waiting on floor plans, and a task assigned to you.

10:30 a.m. You call the facilities contact. Afterward you type one message: "Log that I spoke to Rosa at Willow Creek Property Management. They want two options, nightly and three times a week. Create a task for me to send both by Wednesday, and close the floor plans ticket since she sent them this morning." Claude creates the task, updates the ticket to your workspace's closed status, and tells you what it did.

2:00 p.m. A new lead comes in through your website form and lands in Argento automatically. You ask Claude what's on file for that company and to draft a first reply. You edit two sentences and send it from your own inbox.

4:45 p.m. Jamie asks Claude which active projects have nothing ticked off (prompt 22) and finds one new site that never got its supplies-order subtask updated. Ten seconds to fix.

Nobody opened a form all day. The records are still complete, and the activity log shows each change.

How to phrase requests so Claude hits the right record

Most problems with a CRM that works with Claude come from ambiguity, not from the AI. These habits fix almost all of them:

• Use full company names. "Henderson" might be a contact, a company and a project. "Henderson Roofing" is one company.
• Use your own status words. If your ticket list says "Waiting on client," say that. If you ask for a status that doesn't exist, Claude tells you which values your workspace allows instead of inventing one.
• One change per sentence. "Create the task. Then update the ticket." is easier to check than a single long instruction.
• Ask for a readback. End write requests with "tell me exactly what you changed." Compare it to what you meant.
• Propose, then apply for anything touching more than a few records.

When something goes wrong

Is a Claude CRM integration worth it for your team?

It's worth it if your CRM gets stale because updating it feels like a chore. Typing one sentence after a call is easier than filling in three fields on two screens, so records actually get updated.

It's less useful in two cases. If your team lives in the CRM all day and already knows every screen, clicking may be just as fast for simple lookups. And if nobody agrees on what your statuses mean, Claude will apply that confusion faster. Fix the process first.

On cost: Argento includes the MCP server on every plan, from $25 a month for up to 10 users, so you pay for your Claude plan and your CRM plan and nothing on top. Compare that with CRMs that sell AI as a per-user add-on, a point we cover in CRM without per-user pricing. For how a CRM's MCP server is built and what it should expose, see what an MCP server for a CRM does.