← Back to What's New

First reply time on each conversation in the API

Week of September 30, 2026

Conversations in the Stoked API now carry the advocate’s first reply time, so reply speed can be compared conversation by conversation rather than only as each advocate’s median.

• first_advocate_reply_seconds on every conversation, on the list and on the single-conversation endpoint: the time from the prospect’s first message to the advocate’s first reply. It is measured exactly as the Reply Speed report measures a first reply, in active-hours seconds read in the advocate’s own time zone. It is null until the advocate has replied.
• Three early conversations now have a closed_at. Conversations closed before closing recorded a time or a reason were closed with a blank closed_at. They now carry the time they were closed, and are marked as updated so a sync picks them up. They still have no resolution, because no reason was ever given.

The documentation also now spells out how two waiver fields relate to the CSV export (agreement is HTML where the CSV has plain text, and the CSV’s Browser column is read from user_agent), and that a tag outside any group reads general/<name>.

Related: Conversations API, Reply Speed API