Preview Fin without creating a conversation | Community
Skip to main content
Submitted

Preview Fin without creating a conversation

Related products:Fin & AI
  • Oct 19, 2026 2:35 PM UTC
  • 2 replies
  • 11 views

Sam Wilson
Forum|alt.badge.img

Problem:

Every conversation started in the Fin preview lands in the live inbox as unassigned, alongside real customer conversations. Our support engineers work from that view, so each test conversation looks like a customer waiting for a reply. It's frustrating for the person testing as well. After every preview session I assign the conversations to myself just to get them out of my teammates' way. That's an extra manual step on every test, and it's the opposite of what preview is for.

Why it matters:

It distracts the team and discourages testing. Test conversations pull attention away from real customers, and when you know someone will see each test, or each test means cleaning up after yourself, people test less.

What we'd like:

Preview conversations kept out of the inbox entirely, or assigned automatically to the person running the preview, or put somewhere separate that team views don't include. The person testing should be able to go back to their own preview conversations without anyone else seeing them.

2 replies

Conor
Super User ✨
Forum|alt.badge.img+6
  • Super User ✨
  • Oct 26, 2026 4:48 PM UTC

Hey Sam! This is an interesting one because part of what I value in Fin Preview is being able to test as closely as possible what would happen with a real conversation. So, skipping the real flows would be a painful experience for me! 

I do agree that anything that gets in the way of testing creates a barrier to testing. 

One thing that’s a bit confusing though, is that it seems like Fin automatically closes conversations for most of my testing (occasionally, it won’t close an escalated conversation, and I don’t have a sense of a pattern for why!). 

Do you mostly test escalation flows, or have the auto-close timing set particularly long?


Sam Wilson
Forum|alt.badge.img
  • Author
  • Connector
  • Oct 27, 2026 1:52 PM UTC

Thanks for the reply, and you're right. Preview is valuable because it follows the real flow, and I wouldn't want to lose that either. I should have been clearer, the problem isn't how preview behaves, it's where the conversations end up. I see two issues:

  • They get in the way. Until they close, they sit in the same views our engineers use for real customers.
  • They get lost. Once they close, they mix in with thousands of real conversations. Finding my own test from last Tuesday to compare it against today's behavior takes real effort.

What I'm really missing is a home for preview conversations. They would still be real, full-flow conversations, just kept apart from customer traffic and easy to come back to. Batch testing and evals have that kind of space, but preview doesn't.