- Meeting in 60 min
- Perplexity research
- Claude writes brief
Build a pre-call brief for every discovery meeting
An hour before each discovery call, get a one-page brief on the account, the attendee and recent news, saved to Salesforce.
After each sales call, Zapier sends the transcript to Claude, which writes the notes and updates next steps and deal fields in Salesforce.
Reps finish a call, jump straight into the next one, and the CRM update waits until Friday or never happens. Managers forecast from stale deal stages and missing next steps. The notes that do get written are a line or two, so nobody else can pick up the account.
In Zapier, start with your meeting tool's transcript-ready trigger, such as Zoom's new recording transcript trigger. Add a Filter step that continues only when at least one attendee email is outside your company domain.
Add a Salesforce Find Record step that looks up the Contact by the external attendee's email, then a second Find Record for the open Opportunity on that Account. Use Paths so calls with no open Opportunity log the note on the Contact only.
Add the Anthropic (Claude) Send Message action with the prompt below. Map in the transcript plus the Opportunity's current Stage and Next Step so Claude can tell what changed.
Claude replies in JSON only. A Code by Zapier step runs JSON.parse and outputs summary, next_step, next_step_date, stage_suggestion and risks as separate fields.
Log a completed Task with the summary as its description, update the Opportunity's Next Step field, and create a follow-up Task due on next_step_date. Put stage_suggestion in the note instead of changing Stage directly.
Ask reps to skim the logged notes for two weeks and correct anything wrong. Most fixes become one-line additions to the prompt, such as how your team names products and plans.
You are updating Salesforce after a sales call between {{rep_name}} and {{account_name}}.
Current opportunity stage: {{current_stage}}
Current next step: {{current_next_step}}
Read the transcript and return JSON only, with these keys:
- summary: 4 to 6 bullet points covering pain, budget, timeline, decision makers and objections
- next_step: the specific agreed next action, under 15 words
- next_step_date: ISO date if one was agreed, otherwise null
- stage_suggestion: a stage name if the call clearly moved the deal, otherwise null
- risks: up to three short phrases, such as "no budget owner identified"
- competitors_mentioned: an array of names
Only include what was actually said. Do not invent dates or names.
Transcript:
{{transcript}}An hour before each discovery call, get a one-page brief on the account, the attendee and recent news, saved to Salesforce.
Score every demo request against your ICP, update HubSpot and ping the right rep in Slack within a minute of the form submit.
Every new Zendesk ticket gets a category, priority and sentiment tag plus a draft reply in an internal note before an agent opens it.