Settings and activity
6 results found
-
6 votes
Ed
supported this idea
·
-
45 votesEd
supported this idea
·
-
527 votes
An error occurred while saving the comment Ed
supported this idea
·
-
455 votesEd
supported this idea
·
An error occurred while saving the comment Ed
commented
+1. Ties i with email verification and log in to create ticket requests.
-
22 votes
An error occurred while saving the comment Ed
commented
Agree. Detects typing mistakes made by older, stiff finger seniors like myself. Enter 2x and they must match.
But this could also be implemented by the customer login database requested elsewhere.
Ed
supported this idea
·
-
297 votes
An error occurred while saving the comment Ed
commented
+1 here. I plan on testing Hesk with our customers. I don't want any person off the street being able to "play games" or submit a ticket for work they don't intend to pay for. I know I can filter them manually but it's time I don't have being a one man shop right now.
If you plan to implement this, then I suggest having one "superuser" such as the owner of the business being able to see what tickets his/her employees have created and their status. Like groups for customers. This would necessitate a db change but maybe something you could work on in the future.
Agreed but don't call them "deparments". I plan to use this with about 30 different customers so it would be great to be able to group by "customer" vs. departments. Perhaps make the option title editable.
Along the same lines (and the user/customer name database suggestion) is to allow some or all in the department/user/customer category to view tickets for their respective group.