Update your CRM after every call, with proof

A connector links Claude to another tool, so Claude can read it for you (Anthropic). Several meeting transcribers are listed, including Fireflies, Granola, Fathom and Otter.ai. As of October 2026.

1. 1

   In Claude, open Customize, then Connectors.

2. 2

   Search for your transcription service.

3. 3

   Click Connect and sign in to that service.

4. 4

   Ask Claude: "List my last three call transcripts." Check that the calls are yours.

On a Team or Enterprise plan, a Claude Owner may need to turn the connector on first.

Do the check in step 4 properly. Ask for the three calls, then compare the names and dates with your calendar. If a call is missing, the transcriber may still be processing it, or it may sit under a different account than the one you connected. Fix that now, because every later step depends on Claude reading the right call.

Claude needs the current record to compare against. You have two routes.

• CRM connected. If your CRM is in Claude's connector list, connect it the same way. For example, there is a HubSpot connector.
• CRM not connected. Copy the deal's fields into the chat yourself. This works just as well, and you still approve every change.

If you paste, copy the whole record, not only the fields you think changed. Stage, next step, owner, follow-up date and notes all matter, because Claude can only compare what it can see. A field you leave out shows up blank in the Current value column, and Claude has nothing to compare it with.

Replace the curly-brace parts and send it. Start with your last sales call, so you can check every field it changes against what you remember. Use the contact's name and the date exactly as your transcriber shows them. If you had two calls with the same person that week, say which one by time of day.

Check three things before you approve a row:

• The quote. Does the line from the call say what the suggested value claims?
• Not mentioned. Fields the call never covered stay as they are.
• Questions for me. Answer these in the chat, then ask Claude to update the table.

Reply with the rows you approve, for example: "Approve rows 1, 2 and 5. Change row 3 to Friday." Claude gives you a clean list to paste into the CRM.

Only paste updates that came from a real call. If you tried the flow with a made-up or practice transcript, stop after the table and change nothing in your CRM. Run it again once you have the real transcript.

Common mistakes

• Approving the whole table at once. The table feels official, so people reply "approve all". Go row by row. A wrong deal stage or follow-up date is the kind of error that costs you a call later.
• Running it days after the call. You can no longer tell whether a quote is right from memory. Run it within an hour, while you still remember what was said.
• Treating a vague quote as proof. A line like "we should probably talk next week" supports a rough follow-up, not a firm Tuesday. If the quote is softer than the suggested value, ask Claude to write it as "Next week, date unconfirmed".
• Skipping the Not mentioned rows. These are the prompt working properly. Leave the CRM value as it is. Do not ask Claude to fill the gap with a best guess.
• Pasting notes and calling them a transcript. Notes hold what you remember of the call, and they can miss things. If you paste them, say so. Then everyone reading the table knows the quotes are your own words.

Picture a six-person bookkeeping firm. The owner has just finished a first call with the office manager of a small dental clinic. The CRM record says the stage is Discovery, the next step is Send proposal, and the follow-up date is blank.

She sends the prompt with the clinic's name and today's date. Claude finds the call and returns a table. Here are four of its rows, made up for this example.

Under the table, Claude adds one line in Questions for me: "Did you promise to send the proposal by a specific day?"

Notice what is missing. Claude did not invent a follow-up date, and it asked a question instead of guessing about the promise. That is what you want to see every time.

She reads it row by row. The stage row is backed by a clear request, so she approves it. The follow-up row says Not mentioned, which matches her memory, so it stays blank. The objection is in the client's own words, which is exactly what she wants in the record. She answers the question: "Yes, by Friday." Claude updates the promise row.

She replies: "Approve the deal stage, objections and promise rows." Claude returns a clean list. She pastes it into the CRM, and adds the three-line note. It takes a few minutes, and she can point to a quote behind every change.

If Claude still looks stuck after one retry, stop and paste the transcript yourself. A fresh chat with the transcript and the record pasted in is slower, but it removes the connector as a cause, so you can tell where the problem is.