Choose your source of truth
Decide whether CallForge or your CRM owns lead status. Most teams import from CRM, dial in CallForge, and write outcomes back.
Map disposition codes before launch so sales reps see familiar labels: qualified, callback, not interested, wrong number.
Webhooks for custom stacks
Use webhooks for real-time events: call completed, appointment booked, handoff ready. Payloads include lead ID, duration, transcript summary, and next steps.
Authenticate webhook endpoints and implement idempotency — carriers occasionally deliver duplicate events.
Measure what reps actually use
Push only fields your team will read. Over-syncing creates noise; under-syncing means reps work from two systems.
Review a weekly sample of CRM records against call transcripts to catch mapping drift early.