Intercom closed conversations
One search per page over conversations updated since the window opened, and three things on each: its id, its state and its close statistics. Never a message, never a contact, never an email address.
Access
- Kind
- A read-only key you paste
- What to give
- Access token
- Why that one
- An Intercom access token that can read conversations. This source writes no spend: it reports what the spend produced.
What it attributes on its own
- From the source
- conversations closed per day, at the moment each last closed · reopens, counted apart so a conversation closed twice is still one conversation
- Needs a rule or a trace
- which conversations an assistant handled — Intercom's search does not tell us, so cost per closed conversation is a floor on the cost per assisted one · the workflow, which you tell us · how hard a conversation was: a one-line answer and a week-long thread both count as one
The addresses it calls
- https://api.intercom.io/conversations/search
Only these. A call anywhere else is refused before it leaves, and every call is logged.
Connecting it
- Create an access token. Developer Hub → your app → Authentication. Read permissions on conversations are all it needs. Open ↗
- Name the workflow these count for. The workflow your assistant serves in the inbox. Its spend divided by these closes is your cost per resolved conversation.
- Paste both and click Test and connect. Valistry searches the last seven days, reports how many closed, then fills thirty.
Where your assistant writes the conversation id into a trace, we can join conversation to spend exactly instead of by workflow; ask us and we will read it.