Turn Sybill call notes into CRM updates and follow-up emails

Start with the Sybill meeting summary, transcript, participants, speaker notes, recording link, and any automatically detected action items. Add the matching HubSpot deal or contact record, current deal stage, owner, next step field, and any pre-call notes the rep used. Save everything in one Google Doc or deal workspace so the rep can compare the summary against the transcript before updating CRM. QA check: make sure the packet includes the call date, account name, attendee names, and transcript link before any follow-up copy is drafted.

Use Claude to convert the call notes into a structured qualification summary before writing any follow-up. Include the buyer problem, current process, urgency, decision criteria, stakeholders, timeline, budget clues, competitors, and unknowns. Ask Claude to mark each item as confirmed, inferred, or missing so the rep does not treat assumptions as facts. QA check: every confirmed item should point back to a transcript quote, Sybill note, or CRM field.

Analyze these sales call notes and create a structured qualification summary.

Call notes and transcript:
{{call_notes_and_transcript}}

CRM context:
{{crm_context}}

Return:
1. Buyer problem
2. Current process
3. Business impact
4. Urgency
5. Decision criteria
6. Stakeholders mentioned
7. Timeline
8. Budget or commercial clues
9. Competitors or alternatives
10. Next step
11. Unknowns to clarify

For each item, label it as confirmed, inferred, or missing. Include evidence from the call where available. Do not invent missing details.

Pull the exact phrases the buyer used to describe pain, urgency, objections, success criteria, and internal politics. Store each phrase with speaker, topic, and where it can be reused: follow-up email, proposal, internal handoff, or manager coaching. Keep the quotes short and only use language that appears in the transcript or approved call notes. QA check: remove anything that paraphrases the buyer as if it were a direct quote.

Extract buyer language from this sales call.

Transcript or notes:
{{call_notes_and_transcript}}

Create a table with:
1. Exact buyer phrase
2. Speaker if known
3. Topic: pain, urgency, success criteria, objection, stakeholder, process, or decision criteria
4. Why the phrase matters
5. Recommended reuse: follow-up email, proposal, CRM note, handoff, or coaching

Rules:
- Quote only words that appear in the transcript or notes
- Keep phrases short
- Do not paraphrase as a quote
- Flag anything sensitive that should stay internal

Before editing HubSpot, create a field update checklist from the call. Include lifecycle stage, deal stage, next step, follow-up date, close-date confidence, pain summary, competitor mention, objection, stakeholder notes, forecast risk, and owner notes. For every recommended update, include the evidence, confidence level, and whether the rep should update now or verify first. QA check: do not change stage, amount, close date, or forecast fields unless the call gives enough evidence.

Convert this call summary into HubSpot updates.

Call summary:
{{qualification_summary}}

Transcript evidence:
{{buyer_language_snippets}}

Current HubSpot fields:
{{current_hubspot_fields}}

Return a table with:
1. HubSpot field
2. Current value
3. Recommended value
4. Evidence from call
5. Confidence: low, medium, or high
6. Update now or verify first
7. Notes for the rep

Do not recommend changes to amount, close date, stage, or forecast unless there is clear evidence.

Use Claude to draft a concise follow-up email while the call context is fresh. The email should thank the buyer, restate the pain in their language, confirm the agreed next step, include promised resources, and name the owner and date for the next action. Keep assumptions out of the email unless they are framed as items to validate. QA check: the rep should compare the email against the transcript and remove anything that was not actually discussed.

Write a concise post-call follow-up email.

Buyer and company:
{{buyer_and_company}}

Call context:
{{qualification_summary}}

Buyer language to mirror:
{{buyer_language_snippets}}

Promised resources:
{{promised_resources}}

Agreed next step:
{{agreed_next_step}}

Rules:
- Keep under 180 words
- Use the buyer's language where natural
- Confirm the owner and date for the next step
- Do not add new promises, pricing, legal terms, or timelines
- End with a soft confirmation question

If another rep, sales engineer, manager, or customer success owner needs context, create a separate internal handoff. Include account, attendees, deal status, buyer priorities, technical or commercial risks, support needed, next step, and owner. Format the handoff for Slack or a CRM note rather than a long document. QA check: every handoff should include a clear ask, not just an information dump.

Create an internal sales handoff summary from this call.

Call summary:
{{qualification_summary}}

CRM context:
{{crm_context}}

Support needed:
{{support_needed}}

Format for Slack with:
1. Account and deal
2. Attendees
3. Buyer priority
4. Current status
5. Risks or blockers
6. Next step
7. Owner
8. Specific ask from the internal team

Keep it concise and action-oriented.

Review the transcript for explicit objections, hesitation signals, procurement concerns, competitor mentions, unclear decision process, missing stakeholders, or weak next steps. Assign each issue a severity level and a recommended response or follow-up action. Separate deal risks from coaching opportunities so the manager knows what threatens the opportunity versus what the rep can improve next time. QA check: do not mark something as resolved unless the buyer clearly accepted the answer on the call.

Find objections and deal risks in this sales call.

Call transcript and notes:
{{call_notes_and_transcript}}

Qualification summary:
{{qualification_summary}}

Return:
1. Explicit objections
2. Implicit hesitation signals
3. Missing stakeholders
4. Unclear decision process
5. Procurement, legal, or security concerns
6. Competitor mentions
7. Weak or vague next steps
8. Recommended follow-up action for each item
9. Severity: low, medium, or high
10. Evidence quote or source note

Do not mark a risk as resolved unless the buyer clearly accepted the answer.

Apply the approved CRM updates in HubSpot after the rep reviews the field checklist. Add the qualification summary, next step, follow-up date, stakeholder notes, objection notes, and call recording link. Use the notes field for nuance, but keep forecast-critical fields clean and evidence-backed. QA check: the next step should be specific, dated, owned, and tied to the buyer's agreed action.

Open the draft in Gmail and edit it like a seller, not a copy editor. Remove robotic phrasing, unsupported claims, internal-only context, or details that the buyer did not agree to. Attach promised resources, meeting links, pricing references, or technical notes only if they were approved. QA check: send the follow-up within 24 hours and confirm the email points to one clear next step.

For important calls, use Claude to create a short coaching note for the rep and manager. Highlight strong discovery moments, missed questions, vague buyer answers that needed follow-up, deal risks, and one specific behavior to improve on the next call. Keep the note separate from the buyer-facing follow-up so coaching does not leak into external language. QA check: every coaching point should be behavior-specific and tied to something that happened on the call.

Review this sales call for coaching.

Call transcript and notes:
{{call_notes_and_transcript}}

Rep name:
{{rep_name}}

Deal stage:
{{deal_stage}}

Return:
1. What the rep did well
2. Missed questions
3. Vague buyer answers that needed follow-up
4. Deal risks created or uncovered
5. One specific behavior to improve next call
6. Suggested manager coaching question

Keep the feedback behavior-specific and constructive.

Create HubSpot tasks for every promised resource, internal follow-up, buyer next step, and manager review item. Assign an owner and due date to each task, and send a Slack reminder only for items that require cross-functional help. Do not rely on the email thread to preserve commitments. QA check: every action item should have an owner, date, source call, and success condition.

Once per week, review a sample of calls processed through this workflow. Check whether follow-ups were sent on time, CRM fields were complete, next steps were specific, and risks were captured before the next meeting. Use Claude to summarize recurring issues and update the prompts, field checklist, or coaching questions. QA check: the goal is not prettier notes; it is fewer dropped balls and better deal movement.

Review these post-call records and outcomes.

Post-call records:
{{post_call_records}}

CRM completion report:
{{crm_completion_report}}

Follow-up timing report:
{{follow_up_timing_report}}

Manager feedback:
{{manager_feedback}}

Evaluate:
1. Were follow-ups sent within target timing?
2. Were CRM fields complete and evidence-backed?
3. Were next steps specific and dated?
4. Were risks captured before the next interaction?
5. Which prompt or checklist needs improvement?
6. What coaching pattern should managers reinforce next week?

Return concrete workflow improvements.