Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Helloworks should not send initial notification email #5234

Open
alanna opened this issue Feb 15, 2022 · 11 comments
Open

Helloworks should not send initial notification email #5234

alanna opened this issue Feb 15, 2022 · 11 comments
Assignees
Labels
api Issues that require some work on the API (https://github.com/opencollective/opencollective-api) bug complexity → simple wontfix
Projects

Comments

@alanna
Copy link
Contributor

alanna commented Feb 15, 2022

People still get both emails simultaneously, from OC and HelloWorks.
Screen Shot 2022-02-11 at 2 11 33 PM
Screen Shot 2022-02-11 at 2 11 20 PM

The normal flow should be:

  • You get an email from Open Collective and click the link to HelloWorks
    
  • HelloWorks asks you to confirm your email, you click on something like "Send verification"
    
  • Click on the other email and actually start the flow
    

HelloWorks email should only be sent after clicking on the internal email

@alanna alanna added the bug label Feb 15, 2022
@Betree Betree added api Issues that require some work on the API (https://github.com/opencollective/opencollective-api) complexity → simple labels Feb 16, 2022
@Betree
Copy link
Member

Betree commented Feb 16, 2022

I looked into this quickly. It appears the regression was introduced in opencollective/opencollective-api#6956, it seems that using the delegated authentication is the only way to skip this email. I'll contact HelloWorks support to see what we can do.

@Betree Betree self-assigned this Feb 16, 2022
@Betree
Copy link
Member

Betree commented Mar 23, 2022

A bit late, but I sent out this message to HelloWorks. Now waiting for their reply.

Hi,

We've been using HelloWorks for more than two years now, and we're pretty happy with it. So first, thanks for this excellent service!

The account we're using is linked to the email "----------" and runs under the "----------" plan.

We recently implemented a notification email for the form request because our users were confused by the invitation email from a third-party service they were unaware of. We're now facing an issue where they receive two emails simultaneously: one from us and one from HelloWorks.

There are two ways we could solve that:
Ideally, we would like to use the "Delegated authentication" feature (as described in https://www.hellosign.com/products/helloworks/pricing). Our code is ready to handle this, so enabling the feature on our account would 100% solve the problem on our side.
If not possible, we would like to have a parameter in the createInstance API method to prevent the default email from being sent. People would have to reverify their email through HelloWorks, but the communication would still be clearer.

Thank you in advance,
Benjamin

@Betree
Copy link
Member

Betree commented Apr 13, 2022

No reply from HelloWorks to this date. I'll send the message again.

@alanna
Copy link
Contributor Author

alanna commented Nov 3, 2022

@Betree this is still happening. Did we ever hear back?

@Betree
Copy link
Member

Betree commented Nov 4, 2022

We did, I forgot to update this thread cause the reply did not help much:

TLDR ; move to the "Standard plan".

Hello,

Thank you for reaching out. Taking a closer look at your team's account, it looks like you current plan level does not have access to delegated authentication.

Your current HelloWorks plan is the Essentials 100 plan. The minimum plan level required for delegated authentication is the Standard 1k plan. That said, access to delegated authentication will require an update from Essentials 100 to Standard 1k.

If you'd like more information on the Standard 1k plan, or if you'd like to move forward with upgrading, please let me know and I'll be happy to connect you with someone that can assist with that process.

Please feel free to let me know if you have any questions, I will keep an eye out for your reply.

Best,
HelloWorks Technical Support

Now something worth mentioning: in the last week, HelloWorks seems to have gone through a complete rebranding from HelloSign to Dropbox Sign.

The "Essentials" plan disappeared, but the standard plan moved from $100/m to $25/m (billed by user). I believe we're currently paying $20/m, so it might be a good time to migrate.

image

@alanna
Copy link
Contributor Author

alanna commented Nov 4, 2022

@alinamanko what plan are we on now?

@alinamanko
Copy link

alinamanko commented Nov 7, 2022

@alanna we are on Essntials 100 - allowing us to send 100 forms per month. I checked our billing now - we paid $420 for the annual subscription (comes to $35 per month) back in July. Before migrating to a new plan I would just closely examine what is the monthly forms allowance. Given our past experience with them, I feel this would be a must.

Also, this is really difficult to access a clear outline of plans from their main page and to me, this is quite an annoyance. I think the above is not necessarily what would apply to HelloWorks.

@Betree
Copy link
Member

Betree commented Dec 7, 2022

I know we discussed the new HelloWorks Dropbox Forms plans in different channels and reached out to their support, did we get a reply from them? I'm particularly interested to know if we could fit under the "Standard" plan which I believe gives acces to the feature that would resolve this.

@Betree Betree added this to To do in Tax forms via automation Jan 2, 2023
@Betree
Copy link
Member

Betree commented Jan 30, 2023

Since we moved to a higher plan, I'm gonna try and give delegated authentication another shot

@Betree
Copy link
Member

Betree commented Jan 31, 2023

Since we moved to a higher plan, I'm gonna try and give delegated authentication another shot

It didn't work:

Failed to initialize tax form for account _____ Please contact HelloSign to upgrade to advanced features

Quite frustrating since we're now paying an expensive price for the service. I'm going to rollback opencollective/opencollective-api#8483 and contact their support.

@Betree
Copy link
Member

Betree commented Feb 26, 2024

This will be resolved by #7216. To share some context, here's the reply I got from Dropbox Forms at the time. TLDR ; Pay $10K+/year if you don't want us to send the email.

image

@Betree Betree added the wontfix label Apr 9, 2024
@Betree Betree moved this from To do to Done in Tax forms Apr 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api Issues that require some work on the API (https://github.com/opencollective/opencollective-api) bug complexity → simple wontfix
Projects
Development

No branches or pull requests

3 participants