Skip to main content
Human guide: task steps and agent prompt → Turn an authorized meeting transcript into CRM proposals and a follow-up draft. Keep each proposal attached to its speaker and supporting passage. The first pilot produces review artifacts only: no CRM writes, task creation, or message delivery.

Check transcript readiness and record identity

A meeting-ended event does not prove the transcript is available. Use the source’s supported readiness signal or an explicit retrieval check. Keep these outcomes separate: Resolve participants to the intended CRM account, contact, and opportunity before proposing updates. Hold ambiguous identities. Supported change feeds can use Monitor setup; confirm the source actually supports the required feed.

Test extraction with this synthetic call

Example input:
Expected proposals under this example policy: A seller’s suggestion is not an accepted buyer commitment. Keep missing owners and dates unknown; preserve the original phrase and its context if a relative date cannot be resolved. The source identity and timestamps above are example evidence references, not a universal transcript format. Return a review artifact for each proposal. For example:
The follow-up draft can say: “I’ll send the security questionnaire by October 28. You said you would share it with your security team after receipt. Please confirm whether November 3 works for a follow-up.” Keep the recipient unresolved until their address and CRM identity are verified. Do not describe November 3 as booked or budget as approved.

Build and pilot the proposals

Inspect a returned ID with deepline describe <returned-id> --json. For activity or follow-up variants, search deepline search "meeting transcript CRM activities" --type tools,prebuilts --json. Confirm identifiers, readiness behavior, output, access mode, and price. Author post-call-crm-automation.play.ts using Build a Play. Declare the input and preserve source IDs. Implement readiness checks, participant resolution, evidence-linked extraction, and separate outputs for CRM field proposals, task proposals, and drafts. Keep external changes and sending disabled in the authored logic for this pilot. Prepare a small authorized sample using CSV-safe selection. Include an unready transcript, retrieval failure, no commitment, an unaccepted date, an unknown owner, and the synthetic case above. Review the source and price before provider-backed execution, which can incur usage.
Use the returned run ID and select a dataset path if several exist.

Verify this task

Trace every field, task, and draft claim to the passage that supports it. Confirm that unaccepted dates remain proposed, unknown owners remain unresolved, and retrieval errors remain distinct from calls with no commitment. Every source ID needs a result or explicit exception; the first pilot must create no external tasks, updates, or messages. Before enabling an approved action, verify the destination identity and field authority. Keep stage changes and commercial terms under the required review. For a timeout after an update, task creation, or delivery attempt, reconcile the destination before retrying; repeating an uncertain action can create a duplicate task or message. Repair CRM records covers write verification, and Integrate a Play into your app covers destination reconciliation.