<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Filtering Demo Requests – Cross-Checking Email &amp;amp; Company Domain in Lead Capture Tools</title>
    <link>https://community.hubspot.com/t5/Lead-Capture-Tools/Filtering-Demo-Requests-Cross-Checking-Email-amp-Company-Domain/m-p/1101101#M12410</link>
    <description>&lt;P&gt;Hi &lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/891045"&gt;@NChayban&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This is a difficult one – generally, if you want to request this from the product team, the best place for these kinds of suggestions would be the HubSpot Ideas section of the community.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Personally, I'm a proponent of reviewing each submission, unless the volume is high that it's not humanly possible to do so. The reason is that you'll likely have false positives in any automated filtered or blocking here, preventing actual prospect or customers from getting through. In my eyes, this is simply too high of a risk to accept to filter out a handful of bad submission.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Secondly, I don't think AI would be good enough to evaluate submissions reliably. If someone wants to abuse your meeting link, they will find a way, sadly.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So all in all, I'd recommend simply deleting the records if you find that they are not valid. That will also help with keeping your reports clean. I'm not aware of an automated solution which solves this. But, as mentioned above, it doesn't hurt to flag this with the product team.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best regards!&lt;/P&gt;</description>
    <pubDate>Wed, 29 Jan 2025 11:25:10 GMT</pubDate>
    <dc:creator>karstenkoehler</dc:creator>
    <dc:date>2025-01-29T11:25:10Z</dc:date>
    <item>
      <title>Filtering Demo Requests – Cross-Checking Email &amp; Company Domain</title>
      <link>https://community.hubspot.com/t5/Lead-Capture-Tools/Filtering-Demo-Requests-Cross-Checking-Email-amp-Company-Domain/m-p/1101096#M12409</link>
      <description>&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We've recently been receiving &lt;STRONG&gt;suspicious demo requests&lt;/STRONG&gt; via our website, where the &lt;STRONG&gt;email credentials seem valid, but the request wasn’t actually submitted by the person in question&lt;/STRONG&gt;. While this could be a competitor, an ex-employee, or just someone wasting time, it ultimately &lt;STRONG&gt;distorts lead tracking and marketing KPIs&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;To address this, I was wondering if &lt;STRONG&gt;HubSpot could implement a feature that cross-checks the email domain and the company domain&lt;/STRONG&gt; before allowing a form submission. The idea would be:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;If &lt;STRONG&gt;email domain ≠ company domain&lt;/STRONG&gt;, the form submission could either be &lt;STRONG&gt;flagged&lt;/STRONG&gt; or &lt;STRONG&gt;blocked&lt;/STRONG&gt; (depending on the settings).&lt;/LI&gt;&lt;LI&gt;This would help filter out requests that seem fishy while keeping real leads.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;That said, I can see potential &lt;STRONG&gt;downsides&lt;/STRONG&gt;, such as valid prospects using personal emails or companies with multiple domains. I’d love to hear if:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Anyone else is facing a similar issue?&lt;/LI&gt;&lt;LI&gt;How are you currently handling such cases?&lt;/LI&gt;&lt;LI&gt;Would a &lt;STRONG&gt;domain validation feature&lt;/STRONG&gt; help, or does anyone have a better idea to filter out fake demo requests?&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;Looking forward to your insights!&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;</description>
      <pubDate>Wed, 29 Jan 2025 11:15:56 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Lead-Capture-Tools/Filtering-Demo-Requests-Cross-Checking-Email-amp-Company-Domain/m-p/1101096#M12409</guid>
      <dc:creator>NChayban</dc:creator>
      <dc:date>2025-01-29T11:15:56Z</dc:date>
    </item>
    <item>
      <title>Re: Filtering Demo Requests – Cross-Checking Email &amp; Company Domain</title>
      <link>https://community.hubspot.com/t5/Lead-Capture-Tools/Filtering-Demo-Requests-Cross-Checking-Email-amp-Company-Domain/m-p/1101101#M12410</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/891045"&gt;@NChayban&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This is a difficult one – generally, if you want to request this from the product team, the best place for these kinds of suggestions would be the HubSpot Ideas section of the community.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Personally, I'm a proponent of reviewing each submission, unless the volume is high that it's not humanly possible to do so. The reason is that you'll likely have false positives in any automated filtered or blocking here, preventing actual prospect or customers from getting through. In my eyes, this is simply too high of a risk to accept to filter out a handful of bad submission.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Secondly, I don't think AI would be good enough to evaluate submissions reliably. If someone wants to abuse your meeting link, they will find a way, sadly.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So all in all, I'd recommend simply deleting the records if you find that they are not valid. That will also help with keeping your reports clean. I'm not aware of an automated solution which solves this. But, as mentioned above, it doesn't hurt to flag this with the product team.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best regards!&lt;/P&gt;</description>
      <pubDate>Wed, 29 Jan 2025 11:25:10 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Lead-Capture-Tools/Filtering-Demo-Requests-Cross-Checking-Email-amp-Company-Domain/m-p/1101101#M12410</guid>
      <dc:creator>karstenkoehler</dc:creator>
      <dc:date>2025-01-29T11:25:10Z</dc:date>
    </item>
    <item>
      <title>Re: Filtering Demo Requests – Cross-Checking Email &amp; Company Domain</title>
      <link>https://community.hubspot.com/t5/Lead-Capture-Tools/Filtering-Demo-Requests-Cross-Checking-Email-amp-Company-Domain/m-p/1101116#M12411</link>
      <description>&lt;P&gt;Hi Karsten,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you for your response!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Intuitively, I had a feeling that automated filters wouldn’t be a viable solution, but I guess I needed to hear it from someone else. And you’re absolutely right—if someone wants to abuse the system, they’ll always find a way.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Appreciate the insight! I’ll proceed with manual filtering for now.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks again!&lt;/P&gt;</description>
      <pubDate>Wed, 29 Jan 2025 12:04:35 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Lead-Capture-Tools/Filtering-Demo-Requests-Cross-Checking-Email-amp-Company-Domain/m-p/1101116#M12411</guid>
      <dc:creator>NChayban</dc:creator>
      <dc:date>2025-01-29T12:04:35Z</dc:date>
    </item>
  </channel>
</rss>

