Skip to main content
GET
Get clients with the lowest resolved conversations
Returns the top 3 client domains that have the highest number of unresolved conversations within the given date range. A conversation is considered unresolved if it does not contain a resolved category.

Request

Headers

Path Parameters

Parameter Format

  • Format: YYYY-MM-DD (ISO 8601 date)
  • Timezone: UTC
  • Default: Last 7 days if not provided

Response

200 OK - Successfully retrieved clients with lowest resolved conversations

400 Bad Request

401 Unauthorized

500 Internal Server Error

Example

Data Fields Explained

Clients by Lowest Resolved Array

Use Cases

  • Problem Identification: Identify clients with resolution issues
  • Service Improvement: Target improvements for specific domains
  • Quality Assurance: Monitor resolution quality by client
  • Relationship Management: Address client-specific issues
  • Process Optimization: Identify patterns in unresolved conversations

Analysis Examples

Resolution Rate Calculation

Trend Monitoring

Best Practices

  1. Regular Monitoring: Track unresolved conversations weekly
  2. Root Cause Analysis: Investigate why certain domains have more unresolved issues
  3. Client Communication: Proactively address issues with problematic domains
  4. Process Review: Review resolution processes for specific client types
  5. Performance Tracking: Monitor improvement over time
  • Use /email-meter/stats/clients/top-domains for overall domain volume
  • Use /email-meter/stats/clients/response-times for domain performance metrics
  • Use /email-meter/stats/resolved-times for overall resolution analysis

Notes

  • Only domains with unresolved conversations are included
  • Unresolved conversations are those without resolved status
  • Data helps identify clients needing special attention
  • Results are sorted by highest unresolved count first
  • Limited to top 3 to focus on most critical issues

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

startDate
string<date>
required

Start date for the range (YYYY-MM-DD)

endDate
string<date>
required

End date for the range (YYYY-MM-DD)

Response

Successfully retrieved clients with lowest resolved conversations

message
string
Example:

""

data
object