​
Purpose

Post-call push sends structured call outcomes to a CRM after CXB Core completes the call and CXB API stores the result. Typical payload fields:
  • customer identifiers from call.* or crm.*
  • call status
  • disposition
  • sub-disposition
  • call duration
  • recording URL
  • analysis fields
  • QC scores

​
Mapping

In bot Tools & Integrations, configure the post-call push mapper:
CRM keyCX Bridge variable
disposition{{analysis.DISPOSITION}}
sub_disposition{{analysis.SUB_DISPOSITION}}
recording_url{{result.recording_url}}
duration{{result.call_duration_seconds}}
customer_id{{CUSTOMERID}}
Use exact CRM key names required by the receiving system.

​
Transfer-state fields

If the bot may transfer calls, map the native transfer-state result fields (populated by the API service; empty when no transfer happened):
CRM keyCX Bridge variable
was_transferred{{result.was_transferred}} (yes / no)
transfer_destination{{result.transfer_destination}}
transfer_target{{result.transfer_target}}
transfer_reason{{result.transfer_reason}}
transfer_method{{result.transfer_method}}
transfer_at{{result.transfer_at}} (seconds into call)
transfer_failed_reason{{result.transfer_failed_reason}}
drop_unresolved is true for outbound push. Unlike in-prompt rendering (where an unresolved {{...}} is left as a literal so you can spot mistakes), the post-call push renders templates with drop_unresolved=true: any unresolved token becomes an empty string. A typo’d variable silently sends "" rather than the curly braces. Verify the actual payload after a test call.
For the complete catalog of every namespace and field, see Post-call variables.

​
Recording URLs

For CRM push, use: 
{{result.recording_url}}
CXB API generates a stable public recording route backed by a per-call access token. This avoids sending long raw S3 signed URLs that may be clipped by external CRMs.

​
Auto-disposition cases

Some calls skip LLM post-call analysis. In those cases the configured auto disposition fields should provide the CRM outcome. Common auto cases:
  • RNR
  • voicemail / IVR
  • timeout
  • system error
  • no customer message

​
Validation checklist

After a test call:
  1. Open call detail.
  2. Confirm post-call analysis or auto disposition.
  3. Confirm recording URL works.
  4. Confirm CRM received the payload.
  5. Confirm CRM fields are populated, not curly-brace placeholders.
  6. Confirm failed CRM pushes are visible in integration logs or backend logs.