Overview
Get the average time it takes for your team to send the first response to new customer messages within a specific date range. This critical metric helps you measure customer service quality and SLA compliance. First response time is one of the most important customer service metrics, directly impacting customer satisfaction and retention.Use Cases
- SLA Monitoring: Track compliance with response time SLAs
- Customer Satisfaction: Monitor key customer experience metric
- Team Performance: Measure overall team responsiveness
- Trend Analysis: Compare first response times across different periods
- Improvement Tracking: Monitor the impact of process changes
- Reporting: Generate executive reports on customer service quality
Authentication
This endpoint requires authentication using an API key. Include your API key in the request header:Query Parameters
Parameter | Type | Required | Description |
---|---|---|---|
startDate | string | No | Start date (ISO 8601 format). Default: 7 days ago |
endDate | string | No | End date (ISO 8601 format). Default: today |
agentIds | string[] | No | Filter by specific team member IDs |
pipelineId | string | No | Filter by specific pipeline |
Default Range: If no dates provided, returns data for the last 7 days.
Response Structure
Field | Type | Description |
---|---|---|
averageFirstResponseTime | number | Average first response time in seconds |
Example Requests
Get Last 7 Days (Default)
Get Specific Date Range
Filter by Pipeline and Team Members
Example Response
Common Use Cases
1. Display Response Time Metric
2. Compare Different Time Periods
3. SLA Compliance Check
4. Compare Team Member Performance
5. Weekly Performance Report
Date Format
Dates should be in ISO 8601 format (YYYY-MM-DD):- โ
Correct:
"2024-09-30"
- โ
Correct:
"2024-01-15"
- โ Incorrect:
"09/30/2024"
- โ Incorrect:
"30-09-2024"
Time Zone Considerations
- Dates are interpreted in your accountโs configured time zone
- Response time calculations respect your business hours
- Default date range: Last 7 days from current time
Error Responses
Status Code | Description |
---|---|
400 | Bad Request - Invalid date format |
401 | Unauthorized - Invalid or missing API key |
500 | Internal Server Error - Something went wrong |
Performance Benchmarks
Typical first response time benchmarks:Time Range | Rating | Use Case |
---|---|---|
< 3 minutes | Excellent โญโญโญ | Premium support, urgent |
3-5 minutes | Good โญโญ | Standard support |
5-10 minutes | Fair โญ | Non-urgent inquiries |
> 10 minutes | Needs Work โ ๏ธ | Consider staffing/processes |
Related Endpoints
- GET /api/public/analytics/agents/response-time - Individual team member metrics
- GET /api/analytics/team/snapshot/agent-distribution - Current workload distribution
- Analytics Overview - Complete analytics guide
Notes
- First Response Only: Measures time to FIRST team member response per conversation
- Team Average: Aggregates across all team members (or filtered subset)
- Seconds Unit: Response time returned in seconds
- Default Period: Last 7 days if no dates specified
- Business Impact: Lower times generally correlate with higher satisfaction
Headers
API key
Query Parameters
Start date (ISO 8601). Defaults to today-7d 00:00.
Example:
"2025-05-27"
End date (ISO 8601). Defaults to today 23:59.
Example:
"2025-06-03"
Optional array of agent IDs to filter by specific agents
Example:
["agent-id-1", "agent-id-2"]
Optional pipeline ID to filter by specific pipeline
Example:
"pipeline-id-1"
Response
200 - application/json
Successfully retrieved average first response time
Average first response time in seconds
Example:
300