Currently, the QA reviewer fields set in the monitor UI (qa_monitor_assignees, qa_monitor_statuses, and qa_assignee_id) are not exposed as attributes in the reporting dataset. The only attribute wired to scorecard metrics is conversation.admin_assignee_id, which represents the conversation assignee rather than the reviewer.
Because these fields are missing from the reporting dataset, users cannot filter reporting metrics by QA reviewer or segment reviewed_count by the person who performed the review. Exposing these QA-specific fields in reporting would allow teams to accurately track reviewer output without misattributing review activity to the conversation assignee.