Thanks for the switch, Vlad ... but this editor is different than on your Forum and, unfortunately, worse.
Please switch support.ActionTiles.com back, ASAP.
Frankly, I very, very much prefer the original editor before you messed with it a couple months ago (?). The update has been very troublesome for us. If you can please return the even older editor, that would be my personal preference - by far!
Yes ... I think we would like to try the "test mode" Editor you are using. If it isn't much better (or if it is much worse), I presume you can switch us back.
It looks like we can still do code blocks by using HTML-Source mode and the <code> tag.
Please update support.ActionTiles.com editor at your convenience.
Checking for updates, please?
The Editor is still giving me major issues:
In general: The editor is really, really messed up since your last major update. The editor box looks better but functions horribly.
Please revert the editor or replace it with markdown or anything that works consistently.
Hmmmm... I'm finding the editor is working well here on your own Forum (though I haven't tested Issue #1 (mobile predictive text). Why not deploy this version to support.actiontiles.com ?
I can't emphasize enough how important SSL is to my company and Customers.
Chrome and other browsers are starting to give very visible and severe looking alerts to non-SSL https websites, especially if they include password inputs (such as on the user profile Common Settings / Change Password screen!).
Each free Let's Encrypt certificate can be expanded to support a very large number of custom domains. Expanding a certificate does not fall under the "five certificate requests per 7 days" limitations.
Running multiple certificates is probably complicated; but if we're lucky, a single certificate can hold enough domains. Let me help you research this if necessary.
I would love an API call to fetch "Average time to first response" for my Helpdesk.
I guess it would take a time range (perhaps past 2 or 7 days...), thus it would be a moving average (that I can graph).
I want to feed this into my public website (or even a widget in my UserEcho page!), so that I can set Customer expectations as to our current average service time when they open a new Ticket.
Ah... thanks. That's a good option in the meantime (just takes one extra step to remember!); and, yes ... perhaps there are some Closed Topics which I don't mind further comments on though so.... Flexibility is good.
I'm finding very few Customers are using the Reply Vote thumb-up function ... and ever fewer use the Reply Vote thumbs-down ... but that just makes the occasional thumbs-down even more "jarring".
Perhaps a "Like" button is handy to show a comment is acknowledged by various Agents and Customers, but, as stated by Ryann, it does confuse and distract Customers from the most importing button: Topic Vote.
So... I think I lean towards eliminating Reply voting entirely (as a Forum configuration option). Thank-you.
That is a nice and appreicated bit of an improvement choice, thanks, but unfortunately, it doesn't quite fix all my circumstances.
My Topic Type Status values are not always identical between different Topic Types, though they match closely enough that a notification shouldn't be sent. For example, I may have "type=Bug, status=Reproducing", "type=Question, status=Researching".
My suggested approach is to offer a combined Topic Type-Status Edit drop down menu; i.e., a menu that would show:
Waiting for Clarification
This is modeled after your drop-down that is used to move a Topic from one Forum to another (which is a great feature!). In one action, I can move a Topic not only to another Forum, but actually to the specific Topic Type in that Forum.
So that same Edit functionality at the Topic level would be amazing; i.e., in one action, I can change a Topic not only from one Topic Type to another, but actually to the specific Topic Type Status.
Yah... It's the 2-step requirement that's causing the "extra" notification:
Thanks ... Actually, I think I meant to refer to Topic-Labels; but I guess it is just as applicable for Topic-Tags.
Customer support service by UserEcho