# Ticketing Form?

**URL:** <https://community.hubspot.com/t/ticketing-form/148093>\
**Category:** CRM\
**Tags:** starter\
**Created:** [April 7, 2026, 8:38pm UTC](https://community.hubspot.com/t/ticketing-form/148093 "2026-04-07T20:38:04Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![cclark2](https://avatars.discourse-cdn.com/v4/letter/c/a88e57/32.png) [@cclark2](https://community.hubspot.com/u/cclark2)\
**Post date:** [April 7, 2026, 8:38pm UTC](https://community.hubspot.com/t/ticketing-form/148093/1 "2026-04-07T20:38:04Z")

</div>

Hello,

We are implementing a new ticket pipeline for pour legal team. we want an internal ticket form that users can fill out to submit a ticket. We don’t want to use the create ticket form as it could cause confusion with the different pipelines. Are there any other ways to have a form within Hubspot for them to fill out and this be routed as a ticket?

---

<div class="post-metadata">

**Author:** ![stassey](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/stassey/32/36_2.png) [@stassey](https://community.hubspot.com/u/stassey)\
**Post date:** [April 7, 2026, 9:23pm UTC](https://community.hubspot.com/t/ticketing-form/148093/2 "2026-04-07T21:23:03Z")

</div>

Hey @cclark2,

Thanks for bringing this to the Community!

One approach you may want to explore is using a form combined with a workflow that simply creates/routes the ticket to a pipeline. Heres a Community post that may hopefully spark some ideas!

- [Creating a standardized internal form](https://community.hubspot.com/t5/Tips-Tricks-Best-Practices/Creating-a-standardised-internal-form/m-p/352410)

I’ll tag in a few of our Top Contributors who may have additional creative solutions or best practices to share!

Hey @EugeneAtKiwi, @JWingate2, [@zach\_threadint](https://community.hubspot.com/t5/user/viewprofilepage/user-id/324811) -- do you have any specific suggestions for @cclark2 on this?

Thanks in advanced!

Sam, Community Manager

---

<div class="post-metadata">

**Author:** ![zach\_threadint](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/zach_threadint/32/46318_2.png) [@zach\_threadint](https://community.hubspot.com/u/zach_threadint)\
**Post date:** [April 7, 2026, 10:12pm UTC](https://community.hubspot.com/t/ticketing-form/148093/3 "2026-04-07T22:12:06Z")

</div>

Hi @cclark2 👋

Have you considered customising the standard “Create Ticket” form, as outlined [here?](https://knowledge.hubspot.com/records/create-tickets#create-a-ticket-from-the-index-page) Looks like it’s possible to use conditional logic here, so you can tailor the form to specific teams / cases -- this might help you avoid the confusion you mentioned.

Another option could be to handle this via a [UI Extension](https://developers.hubspot.com/docs/apps/developer-platform/add-features/ui-extensions/overview), effectively enabling you to build custom HubSpot UI experiences. Note that this option requires custom development.

Please let me know if you have any follow-up questions.

---

<div class="post-metadata">

**Author:** ![SanjayKumar](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/sanjaykumar/32/16943_2.png) [@SanjayKumar](https://community.hubspot.com/u/SanjayKumar)\
**Post date:** [April 8, 2026, 1:12pm UTC](https://community.hubspot.com/t/ticketing-form/148093/4 "2026-04-08T13:12:29Z")

</div>

Hi @cclark2,

Thanks for raising this. It’s a great use case and something that comes up quite often when working with multiple ticket pipelines.  
One option is to use conditional logic in the default ticket creation form. You can set it up so that when a user selects a specific pipeline (for example, Legal), only the fields related to that pipeline are shown. This keeps the form clean and easier for users to fill.  
Steps to set this up:  
1. Navigate to Settings → Objects → Tickets → Forms  
2. Edit the default Ticket Creation Form  
3. Add all required properties (Pipeline, Ticket Status, Legal-specific fields, etc)  
4. Use “Add logic” to apply conditions. For eg: If Pipeline = Legal, then show Legal-specific fields like Request Type, Priority, etc.  
5. Guide users to select the correct pipeline while creating tickets.  
An alternative approach is to use a custom HubSpot form combined with a workflow to create tickets.

1. Create a standard form (Marketing- Forms) with the required fields. Before that, create the same ticket fields as contact properties, because forms in HubSpot can only store contact data.
2. Then go to the form’s Automation tab. You can either enable create ticket directly or create the workflow within the automation tab.
3. In the workflow- Add an action to create a record and select ticket. Map the form (contact) fields to ticket properties. You can also copy any extra information from contact to ticket.

One important point to take care of: HubSpot forms are designed to capture contact data, name, country, etc. As a result, each submission will create or update a contact record. If internal team members are submitting the form, they will be stored as contacts in the CRM.  
Let me know if you’ve any questions.

 ![image (22).png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/5/8/58b8c1abebb532f294cf2cd2ac4f658517317131.png)

 ![image (23).png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/a/6/a603b59aa12436c8b2ab77bf1ef089bfdef6d06b.png)

(Taken help from ai)
