Team performance
See what each teammate did in a period: leads assigned, messages sent, escalations resolved and overdue, and the median first reply after an escalation.
Choose the period
period in the response echoes the exact bounds used, in UTC.
What each number means
Who is listed
- Every active teammate, even with zeros.
- Former members, partners, and Nexor support staff only when they did something in the period.
unattributedcounts messages that no teammate can take credit for:business_app_messageswere sent from the WhatsApp Business App through Coexistence, andother_human_messageswere sent by a person who is not a current teammate.
Filter by task
Addworkflow_id to count only leads active in that task (workflow in the API), and the messages and escalations on those leads.
Before you start
- MCP keys need
reports:read. Full-access REST keys need nothing else. - Errors return a stable code in
error, such asinvalid_date_rangeorworkflow_not_found. Map the code to your own copy. - An AI connected to the Nexor MCP server reads the same report with the
get_team_performancetool.
Authorizations
API key for authentication. Keys are prefixed with nxr_live_.
Query Parameters
Task ID (workflow in the API). Counts only leads active in this task, and messages and escalations on those leads. A malformed ID returns 400 invalid_workflow_id, and a task outside this account returns 404 workflow_not_found.
Start of the period, inclusive. Defaults to 30 days before date_to. Accepts YYYY-MM-DD (read as midnight UTC) or an ISO 8601 date-time.
End of the period, exclusive. Defaults to now. Accepts YYYY-MM-DD (read as midnight UTC) or an ISO 8601 date-time. The period must be positive and at most 92 days, or the request returns 400 invalid_date_range.
Response
One row per teammate for the period.