@bwdjames thanks for your input
Thanks folks, let’s go on with the table 
Small preview of the news boxes on the dashboard.
Preview of the asset/monitoring portal
6 Likes
Honestly, the problem is both technical and commercial.
Technically if you buy Pizza with phone support and x tickets how can Nethesis separate them from other plans? How are support guys able to understand if you are allowed to make that call or not? It would be very tricky.
Commercially let me admit that is a bit crazy, you can buy 5 Crostino and 1 Fiorentina and spread all the tickets on all your subscriptions 
That’s a final version of the table
1 Like
If it’s not hardware bound I can just change a Fiorentina with a Crostino and use all my support tickets that way.
So, for presenting the specifics, the table is clearer. For catching attention, the columns are better, imho.
The website could advertise using (dressed down) columns, and when clicking present the table. This would be my preference. In the column view I would like prices and the short version of who this is targeted to, the table should explain the rest.
Let us please agree that most of us really do not need any support plan, but if we are running production environments, we need our asses covered. The real value, to me, is in delayed (aka stable) updates and the whole support ticket thing is a nice extra I do not expect to ever use except to steer the amount of money I would like to have our business invest in Nethserver in a non-obvious way 
What would be interesting is to know how an incident is defined … can that take multiple days for instance? If not (duh), how will that be handled? Will I be able to buy extra support tickets at a reduced rate when my Lasagna is finished or will that require an upgrade to Florentina or even switch back to 100/incident ?
Perhaps you should define an incident as 1 hour of labour, and charge per 15 minutes, as an incident taking several hours becomes expensive for you guys quickly, and no business expects to pay just 100€ for several hours of work … unless you define it like 100€ / incident 
3 Likes
We’re very close to the Subscription launch!
I need your opinion on this matter, people will ask questions about Subscription: subscribing process, pricing, features, as they have done so far on those topics.
My first thoughts were to ask people send an email to a private email address but it’s risky. I’m likely to answer the same questions multiple times while if I keep the discussions here people can read and learn beforehand.
Pratically, I’m thinking of a category called “subscription” here.
Just to be clear, not a category where people will get professional paid support but a place where people can find answers about the subscribe process, issues with registration or plans benefits. Through it, I can collect feedback to improve the whole subscription process and make it straightforward.
What do you think? Is it a good idea?
@planet_jeroen @bwdjames @mrmarkuz @dnutan @FixitFelix
1 Like
I think it’s a good idea: It’s open, transparent and efficient. In some time a kind of wiki page/post with answers to the questions asked in this category will come out of this. I don’t see anything against it except of maybe having much subscription questions overtaking the community board in the beginning but as it is an own category it should be manageable.
3 Likes
In the beginning, I can manage all the questions
2 Likes
I agree. Keeping it in the open will the most efficient way to handle the requests. The transparency will promote trust (not necessarily needed for active members but more for newcomers looking into support). And having it in the open will potentially boost the amount of subscriptions that you sell. As a consumer it’s frustrating to have to send an email and wait for a response because 1: you’re then at risk to receive spam, and 2: if I have to ask for pricing then I’ll have to correspond with a “salesman” and I don’t want to deal with it… Consumers are more likely to jump at “instant gratification” or at least the opportunity to learn about the products they’re interested in and then have an option to ask a question if they have one.
3 Likes
Definitely agree with category called “subscription” and having it transparent for all of the reasons given so far.
2 Likes
Announced here