nsantana
Forum Replies Created
-
Forum: Reviews
In reply to: [WP Gravity Forms HubSpot] Not bad, not perfectI work for a software company so I appreciate the challenge of maintaining user support and that it can sometimes feel thankless. Yet even for a freemium model, it’s hardly charity to provide support. Since you brought it up, even before I entered my review on this site, I went ahead and paid $59 for a premium license for your Gravity Forms Hubspot plugin, specifically to pay for the support ticket that I planned on submitting. Now that I’ve given my review, I’m going to submit a formal ticket, citing my license, and I’ll update this thread once that plays out.
That’s a fair chance for CRM Perks to challenge my 3 star review – a fix to this front end/back end disconnect would say a lot to other users and customers about CRM Perks. Update when I have it.
Forum: Reviews
In reply to: [WP Gravity Forms HubSpot] Not bad, not perfectThanks for the response and also for confirming that your plugin is precisely the problem: the front end works perfectly fine and as expected when it is set to not allow specific email domains via the filter. According to those settings on Gravity Forms, an alert tells the user that they can’t use a non-company domain email when they try to use it. Yet the backend connection receives the form submission from a domain set to be restricted e.g. gmail.com, without so much as a speed bump and stores it as a new form entry. No indication is given to the user that this is happening and we’re just sorting it on the Hubspot side manually. As you’ve stated, @sbazzi , and as @crmperks stated earlier, the CRM Perks Gravity Forms Hubspot plugin “connects your Gravity Form Submissions over to HubSpot” and in this case it connects what we don’t to be connected and so doesn’t sync as expected with the front end that is telling the form user the correct and expected message i.e. you need to use your company email address, but we’re going to upload your form submission any way. The 3 star rating I gave means exactly that the plugin is useful, but has some flaws that you need to work on.