Context:
Running bulk recording exports via /api/v2/recordings/search for legal discovery in Europe/London. Digital channel sessions routed via Predictive Routing show missing routing_skill attributes in the exported JSON payload compared to standard queue routing.
Question:
Why does this setting cause the recording metadata to be incomplete when pulling digital channel exports for legal discovery? The chain of custody requires these specific routing tags. Is Predictive Routing stripping attributes before the recording job commits to S3?
{
“fields”: {
“routing_skill”: “{{routing.skill.id}}”
}
}
Make sure you explicitly request the routing metadata in the search body. The default export often omits these attributes for digital channels to reduce payload size. Adding the specific field mapping ensures the skill ID persists in the JSON, satisfying legal discovery requirements.
{
“fields”: {
“routing_skill”: “{{routing.skill.id}}”,
“routing_strategy”: “{{routing.strategy.name}}”
}
}
You might want to look at including the strategy name too. Predictive routing often strips the skill ID if the strategy metadata isn't explicitly requested in the search body.
You need to include the strategy name alongside the skill ID to prevent Predictive Routing from stripping the metadata. The default payload optimizes for size, so explicit inclusion is required for digital channels.
{
"fields": {
"routing_skill": "{{routing.skill.id}}",
"routing_strategy": "{{routing.strategy.name}}"
}
}
TL;DR: Explicit field mapping is required.
Make sure you define the fields object in your search body. Predictive Routing defaults to minimal payloads, dropping skill IDs to save bandwidth. Adding the explicit mapping forces the API to return the full metadata needed for legal compliance.