AutomationintermediateHITL requiredupdated 2026-08-11

Meeting Notes → CRM Update

Turn a call transcript into a structured CRM update: next steps, deal stage, risks, and a follow-up draft.

#crm#sales#transcription#automation

Tools in the pipeline

llm
summarizer
Extract decisions, objections, commitments.
llm
field-mapper
Align to CRM fields as a proposed diff.
human
rep-review
Confirm the diff before write-back.
api
crm-writer
Patch the record only after confirm.

Stack: transcript · LLM · CRM API

What it does

Converts a sales-call transcript into fields your CRM actually stores: proposed next step, updated deal stage, identified risks, and a follow-up email draft. All as a structured object a human confirms before write-back. Same shape as ARC's FieldNote portfolio candidate.

Pipeline

Summarize — extract decisions, objections, and commitments.
Map — align to CRM fields (stage, next step, close date, risk).
Draft — write a follow-up email referencing the specific commitments.
Stage — present the proposed update as a diff against the current record.
Write-back — on human confirm, patch the CRM via its API.

Guardrails

Only propose a stage change the transcript supports; show the evidence line. Never overwrite a human-entered field silently. Always diff and confirm. Store the transcript reference with the update for auditability.

Structural dry-run

No model call. Validates required fields only.

Prefills the example payload for Discovery call. Edit it, then run.

Evidence → Operating Objects →