Conversation statistics are null | Community
Skip to main content
Answered

Conversation statistics are null

  • October 7, 2025
  • 2 replies
  • 130 views

Hello support!
When fetching a conversation using GET conversations/{id} or POST /conversations/search, the statistics fields are all null. I’m using version 2.10 but tried with 2.14 as well and it doesn’t work either.

 

This is the object I receive 

 

"statistics": {
      "type": "conversation_statistics",
      "time_to_assignment": null,
      "time_to_admin_reply": null,
      "time_to_first_close": null,
      "time_to_last_close": null,
      "median_time_to_reply": null,
      "first_contact_reply_at": null,
      "first_assignment_at": null,
      "first_admin_reply_at": null,
      "first_close_at": null,
      "last_assignment_at": null,
      "last_assignment_admin_reply_at": null,
      "last_contact_reply_at": null,
      "last_admin_reply_at": null,
      "last_close_at": null,
      "last_closed_by_id": null,
      "count_reopens": 0,
      "count_assignments": 0,
      "count_conversation_parts": 7
    }

 

 

My close is to know when was last time a conversation was closed and intended to use statistics.last_close_at

Best answer by Steeve Cayla

@haloqwant statistics will only be populated once the customer replies. Before that, if there’s no customer reply and the conversation is closed, no stats will be populated. 

2 replies

Steeve Cayla
Innovator ✨
Forum|alt.badge.img+5
  • Innovator ✨
  • Answer
  • October 8, 2025

@haloqwant statistics will only be populated once the customer replies. Before that, if there’s no customer reply and the conversation is closed, no stats will be populated. 


Emilygav
Intercom Team
Forum|alt.badge.img+6
  • Intercom Team
  • October 10, 2025

Hey ​@haloqwant, Emily here from Support Engineering at Intercom 👋🏼

 

Steeve is correct! But incase there is a user reply present, we currently do have the following bug open: Statistics object for closed conversations is empty for recent conversations, even when user reply is present. This seems to be affecting EU hosted workspaces.

 

We currently have our engineering looking into this issue and we hope to address it soon.