Rename "Commercial Support" to "Paid Support" #80 #93
Conversation
Simplify/update wording regarding our planned relaunch of the 'Incident-based Support subscription'. Present as a "Support included" variant of our existing 'Stable Updates subscription' membership tier. Incidental changes: - Proposed relaunch cost revision. - Update website copyright notice. - Add Hugo page alias re our prior "/commercial_support.html" url.
Notes on proposed relaunch cost revisionThe more current thoughts on this from me are that we incorporate a Stable Updates subscription within any support tier that we offer. This way we avoid the complexities, on our and other's sides, of having to subscribe to both a stable Updates subscription and an incident based support tier. Ergo we have say a €240 / year single instance support tier that includes a Stable Update subscription. €24 - Stable Updates subscription membership So the equivalent of a €216 premium for single incident paid support. In the context that we are a non-business non-profit and small !! This way Appman would treats each near identically. We may need an additional flag (order.field) to indicate if an incident has been used, and we show this element within Appman's Web-UI only if this is a support tier variant. Upon yearly renewal (New Transaction updating existing order) we ensure this order.field is re-set to what-ever number of support incidents the specific tier level represents. Pricing is based on BareOS https://www.bareos.com/ from around 7 month ago. https://www.bareos.com/pricing/ From the details we have: https://www.bareos.com/Bareos_Pricelist.pdf
So our current equivalent of 48 hours response would be their €2600/10 = €260/incident |
Caveat re Draft
[EDIT] see spin-off issue: "Hugo v0.123.0 breaks downloads page" #94 Building using last know working Hugo version of 0.122.0 and we again have a populated download page. |
|
Moved status to 'ready for review' as our back-end has now received a work-around re our upstream Hugo update sensitivity detailed in the last comment. |
content/paid_support.md
Outdated
| **How much do you charge for Rockstor support?** | Support is charged on a per incident basis, expected relaunch price €240 + tax (if applicable) per incident. | ||
| **How is an incident defined?** | An incident is defined as a question relating to a specific, discrete issue, and may involve several interactions with support prior to that issue's resolution. | ||
| **What is not an incident?** | If your issue is caused by a Rockstor package software bug then there is no charge. In this case we prioritising the related bugfix. | ||
| **How do I contact you for paid support?** | Email support with your Open Collective 'Incident-based Support subscription' membership tier order number. |
There was a problem hiding this comment.
Maybe add the support email address in here, even though it's mentioned in other places.
There was a problem hiding this comment.
If I do, it doesn't show as a link, only text. I tried initially popping in our base-of-page email link but the way we do this table does not allow that kind of rich content. I'll have another look thought.
|
Two small comments on the page text ... |
|
@Hooverdan96 Thanks for the suggestions. I'll take another pass and see what it looks like then. |
Co-authored-by: Hooverdan96 <[email protected]>
Post review suggestions added and further simplification re redundancy and clarification.
|
I've done another pass and incorporated @Hooverdan96 suggestion, it does mean we now have a couple of rouge hard-coded email links (markdown), but it works from the user perspective and I've added an comment to note these in config.toml where all other emails references come from. That boostrap table addition is a tricky one via the shortcode. I've also done some more simplification/reduction word-wise which I think helps. If there are no more suggestions I'll merge and publish this on the 17th. |
|
PR product PRODUCTION published |
Simplify/update wording regarding our planned relaunch of the 'Incident-based Support subscription'. Present as a "Support included" variant of our existing 'Stable Updates subscription' membership tier.
Incidental changes:
Fixes #80