<?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 Routing Form Submissions based on User Input in Tips, Tricks &amp; Best Practices</title>
    <link>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Routing-Form-Submissions-based-on-User-Input/m-p/1142385#M12543</link>
    <description>&lt;P&gt;Hello! I'm interested to know how other businesses handle form submissions/new contacts from multiple locations.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Our brand is adding a second location and we are using embedded Hubspot forms on our website. My initial thought was to add a dropdown field with the two location options and route the form submission to the correct Hubspot Inbox based on the location chosen.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The Inbox is important because our agents use it to make first communication with any new contact. Contacts start online then become in-person students. I would like to use two different Inboxes or Inbox Views because the agents at each physical location are different.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've since learned that one form cannot be connected to two different Inboxes, so I've tried a combination of different workarounds but have yet to find a working solution. These attempts include using workflows to assign Conversation and Contact owners, logic within the form itself, and even a third-party platform, but there is always some limitation in making the full connection.&lt;BR /&gt;&lt;BR /&gt;Is there any way to implement a dropdown in forms for two different locations/teams? Or are completely separate forms for each location the only way? My concern with this route is having to rework the entire website to make sure the user is completing the correct form.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any insight to how others are handling this would be so appreciated!&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 29 Apr 2025 20:49:48 GMT</pubDate>
    <dc:creator>MTellez25</dc:creator>
    <dc:date>2025-04-29T20:49:48Z</dc:date>
    <item>
      <title>Routing Form Submissions based on User Input</title>
      <link>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Routing-Form-Submissions-based-on-User-Input/m-p/1142385#M12543</link>
      <description>&lt;P&gt;Hello! I'm interested to know how other businesses handle form submissions/new contacts from multiple locations.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Our brand is adding a second location and we are using embedded Hubspot forms on our website. My initial thought was to add a dropdown field with the two location options and route the form submission to the correct Hubspot Inbox based on the location chosen.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The Inbox is important because our agents use it to make first communication with any new contact. Contacts start online then become in-person students. I would like to use two different Inboxes or Inbox Views because the agents at each physical location are different.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've since learned that one form cannot be connected to two different Inboxes, so I've tried a combination of different workarounds but have yet to find a working solution. These attempts include using workflows to assign Conversation and Contact owners, logic within the form itself, and even a third-party platform, but there is always some limitation in making the full connection.&lt;BR /&gt;&lt;BR /&gt;Is there any way to implement a dropdown in forms for two different locations/teams? Or are completely separate forms for each location the only way? My concern with this route is having to rework the entire website to make sure the user is completing the correct form.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any insight to how others are handling this would be so appreciated!&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 29 Apr 2025 20:49:48 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Routing-Form-Submissions-based-on-User-Input/m-p/1142385#M12543</guid>
      <dc:creator>MTellez25</dc:creator>
      <dc:date>2025-04-29T20:49:48Z</dc:date>
    </item>
    <item>
      <title>Re: Routing Form Submissions based on User Input</title>
      <link>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Routing-Form-Submissions-based-on-User-Input/m-p/1142466#M12544</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/934495"&gt;@MTellez25&lt;/a&gt;,&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P class="" data-start="93" data-end="465"&gt;One idea might be to keep your single form with a location dropdown, and then use a &lt;STRONG data-start="177" data-end="189"&gt;workflow&lt;/STRONG&gt; to assign a custom property (like “Location” or “Team”) based on the dropdown selection. From there, you could set up &lt;STRONG data-start="308" data-end="323"&gt;Inbox Views&lt;/STRONG&gt; filtered by that property so each team only sees conversations relevant to their location—even though it’s technically the same shared Inbox.&lt;/P&gt;
&lt;P class="" data-start="467" data-end="662"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P class="" data-start="664" data-end="918"&gt;If that still feels clunky for your setup, separate forms per location could make things easier in the long run. You could use smart content to make sure visitors are seeing the right one—so you’re not totally restructuring the site.&lt;BR /&gt;&lt;BR /&gt;Best,&lt;/P&gt;
&lt;P class="" data-start="664" data-end="918"&gt;Jess&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 30 Apr 2025 03:40:05 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Routing-Form-Submissions-based-on-User-Input/m-p/1142466#M12544</guid>
      <dc:creator>JessicaBaskey</dc:creator>
      <dc:date>2025-04-30T03:40:05Z</dc:date>
    </item>
    <item>
      <title>Re: Routing Form Submissions based on User Input</title>
      <link>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Routing-Form-Submissions-based-on-User-Input/m-p/1142832#M12547</link>
      <description>&lt;P&gt;Thank you for your reply,&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/823321"&gt;@JessicaBaskey&lt;/a&gt;&amp;nbsp;! This was my initial thought because it seems the most straight forward but the Inbox Views can't filter by Contact Properties (it would be amazing if they could), only Call, Conversation, or Ticket Properties.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So I did try to use a workflow to update Conversation and Ticket Properties (we handle our calls elsewhere), but they weren't able to cross-reference/update any Contact Properties in the way I needed and vice-versa.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am new to the platform so there might be something I'm missing, but I do appreciate your response and will give it another go before committing to separate forms. Thank you for the tip on Smart Content for the site!&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 30 Apr 2025 18:07:55 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Routing-Form-Submissions-based-on-User-Input/m-p/1142832#M12547</guid>
      <dc:creator>MTellez25</dc:creator>
      <dc:date>2025-04-30T18:07:55Z</dc:date>
    </item>
  </channel>
</rss>

