# Detect and Block Leads Using Profanity

**URL:** <https://community.hubspot.com/t/detect-and-block-leads-using-profanity/28993>\
**Category:** HubSpot Ideas\
**Tags:** object\
**Created:** [December 10, 2020, 3:22am UTC](https://community.hubspot.com/t/detect-and-block-leads-using-profanity/28993 "2020-12-10T03:22:28Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Blink\_Jared](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/blink_jared/32/24779_2.png) [@Blink\_Jared](https://community.hubspot.com/u/Blink_Jared)\
**Post date:** [December 10, 2020, 3:22am UTC](https://community.hubspot.com/t/detect-and-block-leads-using-profanity/28993/1 "2020-12-10T03:22:28Z")

</div>

One of our clients recently received a lead using excessive profanity. Everything from the name to the email address to the message was laced with profanity. It would be great if HubSpot had a way to automatically filter and block leads who use profanity in their form submissions.

---

<div class="post-metadata">

**Author:** ![craftylafty](https://avatars.discourse-cdn.com/v4/letter/c/90ced4/32.png) [@craftylafty](https://community.hubspot.com/u/craftylafty)\
**Post date:** [December 22, 2021, 6:18pm UTC](https://community.hubspot.com/t/detect-and-block-leads-using-profanity/28993/2 "2021-12-22T18:18:24Z")

</div>

Agree completely. In this day and age, we should have a way to filter out form responses in general that include hate speech, profanity, etc. It goes against the Terms of Service for many companies, including [Hubspot’s](https://community.hubspot.com/t5/Getting-Started-on-the-Community/HubSpot-Community-Guidelines/bc-p/4#M10). Yet they don’t have a feature for this.

---

<div class="post-metadata">

**Author:** ![squigglebit](https://avatars.discourse-cdn.com/v4/letter/s/74df32/32.png) [@squigglebit](https://community.hubspot.com/u/squigglebit)\
**Post date:** [February 27, 2023, 1:18pm UTC](https://community.hubspot.com/t/detect-and-block-leads-using-profanity/28993/3 "2023-02-27T13:18:37Z")

</div>

Just came here to search for a solution to this, shocked to see it’s not something we can do!
