Sep 22, 2022 3:26 PM - edited Sep 22, 2022 3:26 PM
I want to confirm that I am able to create free users from our instance and confirm they can view and complete tasks assigned to them directly. I know that accessing tasks in a queue does depend on a Professional or Enterprise license. I also want to make sure that free users would be able to assign tasks to a specific person once they approve a change. How would tickets work for a free user (additional question)? Would tickets be a better option?
Solved! Go to Solution.
Sep 23, 2022 1:07 AM
Hi @clvtross,
Creating, editing, assigning and completing tasks and tickets are all features available to free users:
https://knowledge.hubspot.com/tasks/create-tasks
https://knowledge.hubspot.com/tickets/create-tickets
Which one's betters suited for your scenario depends on what exactly you'd like to achieve and what your process looks like. I'd recommend thinking of tasks as a feature that lets you see unadressed open to dos and track productivity. Tickets, on the other hand, are a fully-fledged object in HubSpot with default and custom fields and they can be created via form submission. While tickets can be enrolled in workflows, tasks can't.
In other words, if you want to build up a customer support process, ticket records would be the core of it. If you want productivity tool, you'd use tasks. Of course the usage of both can be intertwined.
Best regards!
Karsten Köhler |
![]() | Did my post help answer your query? Help the community by marking it as a solution. |
Sep 23, 2022 1:07 AM
Hi @clvtross,
Creating, editing, assigning and completing tasks and tickets are all features available to free users:
https://knowledge.hubspot.com/tasks/create-tasks
https://knowledge.hubspot.com/tickets/create-tickets
Which one's betters suited for your scenario depends on what exactly you'd like to achieve and what your process looks like. I'd recommend thinking of tasks as a feature that lets you see unadressed open to dos and track productivity. Tickets, on the other hand, are a fully-fledged object in HubSpot with default and custom fields and they can be created via form submission. While tickets can be enrolled in workflows, tasks can't.
In other words, if you want to build up a customer support process, ticket records would be the core of it. If you want productivity tool, you'd use tasks. Of course the usage of both can be intertwined.
Best regards!
Karsten Köhler |
![]() | Did my post help answer your query? Help the community by marking it as a solution. |