brian.kneebone

I absolutely love it, just encountered it today and wondered if the feedback helped. Thanks, what a great experience.

Hello, in the current team view (and as directed by this article from your support), I can see how many seats are used versus total.

But if I look at the new view, I don't see any seat usage? Is there a different way I should audit seat usage that maybe this older article doesn't address? I can appreciating needing to differentiate seat usage by type and so maybe this auditing has moved elsewhere? We need at least a breadcrumb I would think in this newer view on where to look as part of my bare minimum feedback.

I've shared this feedback in this comment on the support page for this new view too with at least one other user reporting the same concern. Thank you and kind regards!

Hi @..., yes a printable view would be sufficient to let the browser save to PDF (no need to render to PDF on the back end or front-end, at least for what I'd care about). Generally I think I'd be printing the full side conversation (at least as the default), but having the ability to pick and individual message and its thread history optionally or multiple would be really nice too. There might be some things I wouldn't want others to see in a side conversation (e.g. sharing snippets out to specific audiences so they don't get distracted by the broader conversation OR intentionally obscuring data that has protected data like personally identifiable information of 3rd parties within it). In fact, a good chunk of why we have side conversations is to communicate private information we often do have to filter as I think of it.

I really like the side-conversations abilities, but Michael C. mentioned earlier above, I find it strange why I can't export a conversation to PDF. It would be nice to have this admin controlled or role-based access control managed more generally for people who feel that would too easily allow information to leak out. But the use case for me is about sharing snippets of conversations with people I don't want in the private ticket history generally, but may need something better than copying and pasting out (and dealing with the weird formatting that goes with that) for specific portions or specific side conversations if in whole. I'm hoping this areas gets improved to make them more functional over time. But I like the concept so far.

I spent 45 minutes only to find this later. I'm assuming there's some hosting cost avoidance for costly operations going on here. The ticketing recommendation as a work around is not practical for me. I would like to see the ability to filter on subject conditionals like others are requesting here. Thank you.

+1 for OIDC, we have application teams wondering why we chose this platform without basic federated sign-in for business. Looking forward to seeing this implemented so we can move away from the JWT sign-in.

I see the updated post from @... about a year ago indicating there was going to be an early access program for this with links (pinned as the first article) which is great. But when I try to access the links or request access to EAP to the second link, I get an access denied. Is there an update on the status of this EAP or info on what's intended to be developed that I could get insight into? Thank you & kind regards.