31–40 of 69 posts
Is it due to some (technical) reason that would require a monetary compensation to be profitable?
SSO has security benefits (on top of the maintainability aspect) which would also benefit small businesses.
Key things for support are:
1. Ability to share access to the customers machine with out any hassle and easy acknowledgement for sharing access
2. Recordings and summarirs automatically gets added to tickets and issues
3. Playbooks are handy for the support engineer during the call
Side question: Do these animations linked to scrolling add some real value to the readers? Is there some experimental data showing value (e.g., conversion rate) over a static page? Thanks.
Earlier quoted context omitted.
Hi, Fred here – I’m one of the founding team members. Thanks for the comment. First, to the question about team sizes. We view "Startups" as generally teams with Regarding pricing, we haven’t finalized it yet because we’ve prioritized understanding how teams actually use emdash—what works, what doesn’t, and where we should focus. Pricing is important, and we want to get it right. Typical usage patterns, evolving AI a…
"We haven't figured out pricing" sounds like a big turnoff for anyone seriously considering this who wants self service. Just pick something that's a no brainier for people to try, change it later if you have to. Your biggest risk right now is people walk without giving the product real consideration. Lack of clarity on pricing will do that for a lot of people, even though you are offering a free trial.
Being able to tag chats with keywords would be nice. Being able to pull chats into docs easily would be nice. Being able to pull chats into more than one doc -- not just move, but tag/reference/copy. Global tags (with ACLs) as well as team and personal tags (also with ACLs) would be fantastic. Don't forget read and access ACLs, not just write ACLs.
Email integration would be nice. Emails -> IM, so I can read IMs and emails in one app. IM -> email (right-click on a range of messages, click send, get placed in $MUA and edit).
Don't forget retention controls, support for on-prem, etc.
I see no mention here of using a pre-existing standard chat protocol like XMPP or Matrix, it looks like they rolled their own. Therefore this is not interoperable and is yet another proprietary walled garden. No GNU/Linux client either. Next.
Side question: Do these animations linked to scrolling add some real value to the readers? Is there some experimental data showing value (e.g., conversion rate) over a static page? Thanks.
This looks great. What is the reason for adding the https://sso.tax ? Why did you make SSO an enterprise feature? Is it due to some (technical) reason that would require a monetary compensation to be profitable? SSO has security benefits (on top of the maintainability aspect) which would also benefit small businesses.