John

I've been wanting this module for a while, thank you! One feature I would love, but maybe it falls outside your scope: if a user has had no active or pending services, no open invoices, and no open tickets, it will change that users status to "Inactive" after X days.

Oh, cool! One other question: I remember you saying somewhere that you are going to raise the minimum PHP requirements, but will you be supporting 5.6 or 7.0? Not sure what you are supporting right now, but I am guessing only up to 5.5? Thank you

Hi Paul, Just wondering what the current status is on 4.0. It currently shows you have 12 tasks left (probably excluding hidden). Just so I can plan ahead, when can we expect a beta now? Thank you!

Would it be possible to have a setting that would prevent the client from closing the ticket? For example, an abuse department would use this so clients couldn't just close abuse tickets. It could maybe be either a per ticket or per department setting?

I know this is a major topic bump, but SSL has not been implemented on the forum yet. Can we get it implemented sometime soon? Especially since we are sending usernames and passwords over an unencrypted connection. It does not even need to be forced, just an option for those of us who want it.

Huh, didn't know that Stripe supported ACH. This would be a nice feature to have. +1

It would be nice to have a notification if someone attempts to login but cancels at the two factor auth prompt. Right now I believe that there is no way of knowing if someone abandons the login process at the two factor auth page.

Hello All, This is a feature request I hope no one will have to use. When a database gets breached, or there is a flaw in the security of Blesta, we might need to require all clients to change their passwords (and two factor auth tokens). Currently, there is no way to do this. Most sites just make you login, and then you can change your password. While this is very convenient for users, it is also extremely convenient for the person who managed to dump the database. Therefore, I recommend that after the user logs in, they get sent an email with a PIN number, which they have to put in to the webpage. Then, it will allow them to reset their password. If they do not enter the PIN, then staff would get an alert, because this could mean that the clients account is breached. While the Blesta team is very good at securing their product, this important feature is missing. I view it as a must-have. Right now, if a database were to get dumped we would have to manually reset clients passwords. (VERY time consuming) John

He accidentally bought two of them... he would rather not pay double.

Thank you. Glad to see that it is in your system.

That is a different priority than we are talking about. That is the ticket priority, and we are talking about the email priority. Check my reply above to see what I am talking about. Did not think of that. I do like the low/normal/high selection. I have never heard of SPAM filters not liking this. At this point it is nothing more than a thought, I just brought it up because it would be a good way to send suspension emails, etc. What about integrating it with the ticket system? That way, if a ticket gets sent out as "Emergency", it will get marked as high priority for emails that get sent out through it?

The order system can be configured to send out emails to staff when a new order is received. The issue we are having is that when a staff account is disabled, the emails are still getting sent out to the disabled staff member. Is there a way to set it up so that when a staff account is disabled, or no longer has access to view the order system, the emails automatically switch off?

The email protocol has a built in priority system. Look in your email client and see if you can find it for yourself. For example, I can send a high priority email to myself, and this is how it comes back in Outlook 2016:

I understand that people may have not complained, but it's not what we (as a company) want to be sending to customers. Additionally, we have to open tickets for things like abuse, and linking to the KB is definitely not desired in these situations. I'm sure you understand that we don't want every single one of our canned responses on our KB. It is a valuable tool, but it is not made for that. I am just asking that the system work how it was supposed to from the beginning. I understand this was an oversight, but let's see what we can do to fix the underlying cause, and not just have a temporary work-around. I'm not sure I understand how linking to something in an email (ticket) helps with rankings on search engines.

Hello, I think that a great feature would be the option to specify the email priority for template emails. A service suspension/credit card expiring/payment declined email is high priority, so there maybe should be a check box, saying "Send as high priority" This would mark the email in the clients inbox as having a high priority. What is everyone's thoughts about this feature request?

Maybe there could be an option in the settings for this? That way, the administrator could choose either the beginning or the end. If you force it to be one way, then only half of the people are happy. Is there a way to modify this temporarily, so that we can get this to work right for us? While linking to the knowledgebase may be a good temporary fix, it really takes out the human contact.

Hello, We are trying to set up predefined responses, and we have noticed a bug when we try and use it with a predefined signature. What happens is the system puts the agents signature before the predefined response, so the end result looks something like this: Can anyone else confirm this?

With 3.6, I understand that only transactions counted as 'income' are calculated for the Billing at a Glance plugin. My concern is that for us, we have to manually enter in PayPal payments. This means going under Record Payment, and choosing "Other -> PayPal Payments Standard". It looks like this is not being counted as income. Can anyone else confirm this?

+1 It would give Blesta quite the advantage over WHMCS, as well.

Hello! We support both IPv4 and IPv6 on our services. Each client is assigned one /64 of IPv6, and one IPv4 address by default. The issue comes into play when a client wants an additional IPv4 address. We add it through the configurable options, and everything goes well, until it is provisioned. Instead of provisioning a new IPv4 address, Blesta counts the IPv6 space! This results in the client getting one less IPv4 address than what they paid for. (See the screenshot as an example) Anyone else having this issue?

+1! It would really help for this: http://www.blesta.com/forums/index.php?/topic/3646-plugin-cleint-notices-set-text-or-html-notice-for-each-client/#entry34298

Oh, so it's not a plugin issue, but an issue with Blesta not allowing the re-ordering. Thanks for the insight!

+1, I would love to use this plugin, but this is making it unusable. If someone could please advise, that would be great.

Set the package to restricted, and then on the client page under Account Actions, click Set Packages.

+1!