Harden a CRM Update Tool
Add evidence, validation, approval, and audit fields to a system-of-record write tool.
A CRM update tool writes next_step after sales calls, but transcripts are messy and revenue managers use the field for forecast review. System-of-record write = extracted proposal -> target validation -> approval at consequence -> audit log The common trap is treating a CRM write like a text transformation because the model can summarize the meeting well. Separate proposal from write Create propose_crm_next_step before update_crm_next_step. The proposal can be inspected, scored, and rejected without altering the record. Validate target and value Require opportunity_id, field_name enum, proposed_value, source_transcript_id, and transcript_timestamp. The write should fail closed if the opportunity is stale, archived,…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in