Skip to main content
GET
/
backend
/
reports
/
{orgId}
/
chats
/
missed
curl --location --request GET 'https://api-v2.opencopilot.so/backend/reports/chats/missed?startDate=2023-01-01T00:00:00Z&endDate=2023-12-31T23:59:59Z' \
--header 'Authorization: Bearer YOUR_TOKEN'

{
  "count": 42
}

​
Authentication

​
Authorization
string
required
Bearer token for authentication

​
Path Parameters

​
orgId
string
required
The ID of the organization to filter chats

​
Query Parameters

​
startDate
string
The start date for the date range filter (ISO 8601 format)
​
endDate
string
The end date for the date range filter (ISO 8601 format)

​
Response

​
count
number
The number of missed chats based on the specified criteria
curl --location --request GET 'https://api-v2.opencopilot.so/backend/reports/chats/missed?startDate=2023-01-01T00:00:00Z&endDate=2023-12-31T23:59:59Z' \
--header 'Authorization: Bearer YOUR_TOKEN'

{
  "count": 42
}

​
When is a chat considered missed?

A chat is considered missed when:
  1. AI Autopilot OFF:
    • A user initiates a chat
    • No human agent responds within a set time frame
    • The chat is automatically closed as unresolved
  2. AI Autopilot ON:
    • A user initiates a chat
    • The AI attempts to handle the query but fails to resolve it
    • No human agent intervenes to assist
    • The chat is automatically closed as unresolved
In both cases, the key factors are:
  • The chat session is closed
  • The issue remains unresolved
  • There is no last message, indicating no successful interaction