Sales Call Summary And Handoff with Claude Code: API Runtime Pattern
A production playbook for sales call summary and handoff in cross-industry operations using Claude Code: api runtime pattern, run-scoped inputs, logs, typed results, and artifacts.
Audience: Revenue operations teams
The problem
Revenue operations teams need sales call summary and handoff to run repeatedly against transcripts, CRM notes, and qualification criteria. In cross-industry operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.
Implementation path
Package the sales call summary and handoff instructions as a skill, send transcripts, CRM notes, and qualification criteria as run-scoped inputs, execute with Claude Code, poll terminal status, and consume argo.result.v1 instead of parsing a transcript.
Tradeoffs and failure modes
The API boundary forces the workflow to define inputs, terminal states, and result shape before customers depend on it. For sales call summary and handoff, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.
Run request
POST /api/skills/<skill_id>/run
provider=claude-code
workflow=sales-call-summary
inputs[]=@./input-pack.zip
result_schema=argo.result.v1
Run this on Argo