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:
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:
Build and pilot the proposals
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.