Fin's flawed assumed resolved & pricing design | Community
Skip to main content
Answered

Fin's flawed assumed resolved & pricing design

  • January 22, 2025
  • 30 replies
  • 1883 views

Show first post

30 replies

Conor
Super User ✨
Forum|alt.badge.img+5
  • Super User ✨
  • Answer
  • May 22, 2025

Hope everyone in this thread enjoyed Built For You yesterday 😃

 


bosbeest
Forum|alt.badge.img+1
  • Author
  • Active User
  • May 22, 2025

O.M.G.

 

Thanks for sharing ​@conor - this is amazing!


Julian Murray
Innovator ✨
Forum|alt.badge.img+3

I have been following this discussion for weeks and had a big smile during yesterdays session as this is the first thing I thought of. Seems like a perfect fit here! 


bosbeest
Forum|alt.badge.img+1
  • Author
  • Active User
  • June 4, 2025

Dear ​@conor , ​@Julian Murray and everyone else reading with us, 

 

As I wanted to try the subject of resolution assumption without all the previous posts about finances (which are sometimes quite long) muddying the waters, I opened a thread in another part of the forums

To my disappointment and surprise, Paul Adams’ words are being taken back 😶

 

 


Forum|alt.badge.img+1

Late to this thread but it keeps coming up, so here's the cleanest way to settle the billing question with your own data, no vendor required.

On the earlier disagreement: both sides are partly right, and the distinction matters. Intercom's published rule is that "assumed resolved" requires 24 hours of customer silence after Fin's last reply, and reopens are supposed to DEDUCT resolutions, including when the reopen lands in the next billing period. So a same-conversation re-contact within 24h shouldn't be billed. But the case where an agent steps in and the customer never re-contacts can still count as assumed resolved, because the clock only listens for customer replies. Both things are true at once, which is why this argument never ends.

The check, from your own export, 15 minutes:
1. Export one billing month of conversations with: Fin involvement, resolution state, reopen count, teammate replied, timestamps. Add 7 days on each side of the period so cross-period reopens show up.
2. Count conversations marked resolved where a teammate replied after Fin's last answer. Ask yourself if you'd have paid for those.
3. Count reopens inside your period that trace back to last period's "resolutions". Per the published rules those should deduct. Check whether your invoice reflects it.

Credit where due: the Intercom team in this thread acknowledged you shouldn't be charged for unresolved conversations. The gap is that no invoice shows the per-conversation list, so nobody can verify either way. That's the actual problem.

(Disclosure: I built a small local-run tool that automates this recount. Not linking it here, the manual check above works fine on its own.)