12 results found
-
Do not require request text
I only want to add the customer as a supporter and not be forced to type in text.
1 vote -
Add Custom Fields for Users
In the same manner that custom fields can be created for tickets I'd like to see the addition of custom fields for users.
New ticket rules could then be applied to new tickets based on the custom customer fields in addition to custom ticket fields.
This would allow you to identify certain customers tickets and handle them appropriately. For instance you could make sure VIP customers get their issues addressed as soon as possible or make sure that customers that are a drain on resources are limited.
1 vote -
search tickets by referrer URL
It would be helpful to be able to search tickets by referrer URL, to give an idea of what kinds of questions are asked from certain pages
2 votes -
Create useful spam filters
The current rules functionality is too limited to filter most spam. The only fields we can match are:
- Contact email (useless because of spoofing and because spammers can change domains as many times as they want)
- Message subject (somewhat useful for spam written in Western alphabet; useless for spam written entirely in Chinese, which is what I'm buried with)
- Message text (see above)
Additional useful match fields would be:
- Destination address
- Message HTML (potentially useful if you can't match by message text, see below)
- Additional email header fields
Furthermore, the only matches are "includes" and "does not include". Useful spam…
9 votes -
Copy and paste images
Would be great if I could just paste images into text areas instead of the multi-click process for uploading and attaching them.
24 votes -
Filter Tickets by Browser and OS
Looking at tickets by browser version would streamline the validation of user reported bugs. Retroactively searching through tickets to find the ones with the same browser OS combo is very slow. The browser data is already there for a subset of tickets, adding a search filter for these tickets would be helpful.
2 votes -
Keyboard shortcuts
keyboard shortcuts are so important for those of us who spend all day on the platform. Do these already exist and I just can't find them?
21 votes
Garrick Sawayn
responded
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Non igitur bene. Falli igitur possumus. Easdemne res? Duo Reges: constructio interrete. Eadem fortitudinis ratio reperietur. Velut ego nunc moveor.
-
Integrate with Olark
Integrate with Olark chat so that we can create and track support tickets in an on-line chat and to be able to use standard canned answers not just in support tickets but also in an on-line chat
7 votes -
Convert Facebook messages
add Facebook fan page channel(s) to be able to reply to the messages and convert messages
8 votes -
Support HTML based auto-reply e-mails within Setting/tickets/RULES
Within Setting/tickets/RULES, you can set auto-reply based on certain rules.
There should be a way to enter HTML so the e-mails can be A. Branded B. Have LINKs embedded into text.For e.g. to avoid ugly links like : Click here to track a package http://www.xyz.com/track-a-package/
and replace ugly links with as a link in itself.20 votes -
Have different Custom Fields On Different Widgets
You have given us the ability to add "Custom" fields to our widgets which are great but the only problem is, once you create a custom field it displays on all widgets.
I have created several different widgets to use on different areas of my site and I was hoping I could have had a different custom field for each widget e.g.
I have a "Report" button which I only want a "Custom Field" drop down to only show "Report" related stuff.
On another page, I only want to have a "Custom Field" with just "Advertising" related drop down.
So…
9 votes -
Merge duplicate tickets from different sources
Sometimes people send multiple tickets saying the same thing
Notes:
* Probably only works if the creators of each ticket are watchers/CC's in the other ticket
* Messages are combined and sorted chronologically
* Tags are combined
** Namespaced tags are kept for the "winning" ticket
* The creator of the "winning" ticket is used, other CC's/watchers are combined
* Assignee, priority, status, etc., are kept for the “winning” ticket.5 votes
- Don't see your idea?