interesting perspective
the overwhelmed PM is one instance of the bombardment with questions and requests from multiple sources.
this will not fix organizational issues but it should assist knowledge workers with staying on top of things to be done
fair points all.
we are looking to address the overload through the prioritization so maybe that will somewhat address the first concern
I agree there are multiple use cases.
absolutely right.
that is already on our radar given the types of customers we are currently talking to.
we are also seeing increased scrutiny from the API providers who are insisting on their own security audits to allow API access.
thank you for the feedback.
a couple of comments
1. if you use cloud based services (google, office365, slack etc) which are the only services we currently integrate, your company already allows a third-party to access your email and chat history.
2. depending on the circumstance, we are prepared to discus an on prem deployment and in fact are already involved in some of those discussions.
thanks for your questions
FollowUp is powered by the Loop HQ backend (loophq.com) and is in essence the task extraction functionality broken out into a stand alone product.
1. when a user connects a platform (google for example), the Loop backend runs the metadata from the platform's content through its graph database to identify where does a specific email or file fit in to the user's world. based upon that analysis, Loop scores each contact and by association, each content item with a "Loopscore" which determines the relative importance of that contact or content. this is a continuously iterative process and is impacted by the user's continued behavior.
2. I refer you to our privacy policy which outlines the considerable protections and restrictions we have put on ourselves in order to safeguard user information https://loophq.com/privacypolicy
thanks miker64
our experience has actually not been that - and once security teams have had a chance to review there has been terrific acceptance.
we are only interacting with information that is already on a cloud platform and our protections, policies and structure look to build on that security not subvert it.
the common fear is that we would aggregate information and sell to third parties and that is dealt with in our privacy policies https://loophq.com/privacypolicy
we totally understand the concerns and are hyper-vigilant about security and access to user information.
the permissions we ask to approve are the minimum and standard permissions required by the underlying cloud platform (google, office365, slack etc).
part of the loop functionality allows the user to interact with content that exists on the user's underlying platform i.e. read/reply/forward emails, open/access/edit files etc.
all of that is specific to the individual user, is protected through the encrypted credentials and token provided by the cloud platform upon oauth and governed by out privacy policy and terms of use.https://loophq.com/privacypolicy