Ticket Status vs Conversation Status

This is a great question! The way I'd frame it: conversation status is Front's default, where every request lives as a conversation with the standard statuses (Open, Snoozed, Archived) plus assignment, comments, and tags. Ticket status just adds more structure on top, so each conversation has a status (Open, Waiting, Resolved, plus custom stages) and a ticket ID. The real difference: with conversation status a request is basically open or done, while ticket status gives you the in-between stages plus the reporting and automation that come with them.

It tends to work well when a team needs a real Waiting vs. Resolved distinction, reporting by stage through the Resolution report, ticket IDs for escalation, or customer facing request tracking.

If you mostly need collaboration, assignment, tags, and a clean way to close the loop, plain conversations might be enough. If more of the above sounds like your team, the easiest way in is to turn it on for one inbox first and live with it for a couple of weeks.