Copy Outbound UUI SIP Header to a Custom Field
Updated
Tracking outbound calls across multiple platforms can be difficult because each system uses different identifiers. For example, Sprinklr generates conversation IDs, while telephony providers (such as SignalWire or Genesys) use their own call identifiers.
This article explains how to capture the User-to-User Information (UUI) SIP header generated during outbound calls and store it in a custom field. This enables consistent call tracking, improved reporting, and seamless integration with external systems, including call recording platforms using SIPREC.
This article will be useful for:
Contact center administrators
CX engineers managing integrations
Workflow automation users
Reporting analysts
Business Use Case
Map Sprinklr call data with external telephony systems
Enable accurate call recording decisions in external platforms
Standardize identifiers for reporting and reconciliation
Prerequisite
Ensure outbound calling is configured in your environment
Confirm the UUI SIP header is enabled via your telephony setup
Create a custom field to store the header value
Accessing Guided Workflow
Click the New Tab 
icon. Under the Sprinklr Service tab, select Guided Workflows within Agent Augementation > Resolve.
Configure the Workflow
Step 1: Fetch Conversation Participants
Add a Get Records node
Select Conversation Participant as the entity
Filter by Conversation ID
Store the participant IDs
Step 2: Fetch Contact Details
Add another Get Records node
Filter using Participant ID
Retrieve UUI/UUID header value from the contact
Step 3: Store the Header Value
Save the UUI header in a workflow variable (resource)
Step 4: Update Custom Field
Use the Custom Field action
Map the variable to your target custom field
Output
The outbound call’s UUI SIP header is stored in the selected custom field
This value can be used for integrations, reporting, and tracking
Key Considerations
Configure the workflow to trigger only for outbound calls
The UUI header format depends on your telephony provider
Ensure proper permissions to update custom fields