Hi! I would be extremely useful to have a button for "New Ticket" or "Add a New Ticket" when looking at the customer on the dashboard. This would eliminate me from having to then click tickets and then choose "Add a ticket". The most common action when you open a customer's information is going to be to add a ticket, in my opinion. At a minimum, the option to add a ticket should be listed under the "ACTIONS" button. ...more »
The ability to provide customer logins / access restricted to only themselves for self-service offers great opportunities in itself but this option lead not only to problems with the policy management (as you are able to access all policies) but also the active discovery. If you have two different customers with a custom login for self-service certain scenarios can lead to both customers seeing each others network. ...more »
The customer ticket request portal should be mobile friendly. Customers that want to manage their tickets and either lose internet or are on the road away from their company can't do anything because they can't work with the customer portal.
Currently you can only set a customer to active or non-active. When non-active they arent displayed as a customer to assign a ticket too.
We currently have a customer 'on-hold' due to lack of payment. I would like an option to put the customer ON-HOLD and then add a note to say why.
Doing this should also put ALL exiting and new tickets ON-HOLD automatically.
it would be extremely handy to be able to, at the very least, export the selected customers from the rules grant customer/site access tab, at the very most, have a report that will show me the associations between customers and rules, allowing me to pick which customers, or which rules I want to run the report against. In particular I need this for all of my patch management rules as we currently have to audit patch ...more »
The ability to move customers or sites between SOs at the system level would be useful. We have managed and un-managed customers in separate SOs, sometimes they change their agreement and need to be moved.
The ability to move customers/sites/devices already exists within an SO, this would just be an extension of this feature up to the system level.
I don't think customer level users should automatically be able to see all so level filters, dashboards, recipients.
We should be able to choose to make any of these specifics available to them.
We would like to see an option to revieve a notification via e-mail or trigger in CMC when selected size is increasing a lot during a short period. Some customers would like to keep the montly costs stable and would like to be informend when their bill wil increase a lot when their selected data size is growing.
Custom fields at the Customer and Site levels that are accessible via the rules would provide a lot of flexibility when it comes to service templates or notifications. For example: If I want to roll out Security Manager to a customer, but I need to do it on a site by site basis, it would be very easy to have a custom field that indicates that a site should have Security Manager. Then I can create a filter and eventually ...more »
I would like to be able to apply a "notification window" to a device, site and/or company directly or via a rule. The most specific setting wins. This will provide the ability to set up simplified notifications so that administrators don't need to take into account all the possible permutations of service levels for notifications. They simply say, "I want to be notified about X when it is important to the customer/site/device." ...more »
Supporting custom domains, especially on customer's portal would be great for our customers. It would look more professional to use something like helpdesk.mydomain.com but the real problem is that the current customer portal URL is just way too long. Thanks.
We sell different plans for customers, some need 8x5x6 and others 24x7x4. Service Desk treat both as equals, and that leads to bad SLA warning and breachs, hard to choose right priority. I think its a must to be able to create multiple SLA Levels and set the right SLA for Customer and/or Contract. Rules should consider SLA Levels too..