...
- Feature Requests: Features requested and logged in the Readysell Feature Requests forum
- Change Requests: Paid change requests from customers who have been provided with and accepted a proposal
- Customer Contact: We get the chance to meet customers and hear their successes and challenges via telephone, email, at user group meetings and trade shows
- Technical Support: Our support team provides clear insights into the issues that are challenging for customers, and which are generating the most requests to support
- Office Brands Steering Committee: The steering committee Advisory Groups: Our advisory groups provides insights into real-world customer issues and strategic direction for the group
- Evaluator Feedback: When someone new tries Readysell, we want to know what they liked and disliked and often reach out to them for more detail
- Automated Metrics: Readysell automatically collects performance, reliability and usage metrics about Readysell on your system and uses this to target areas for improvement
- Product Strategy: Our long-term strategic vision for the product
...
After a short period of piloting (typically 1 or 2 days), we commence staged rollout of the new version to customers. Customers are placed into deployment "rings" that dictate this rollout. If you would like to know which ring you are part of and/or change rings, please contact Readysell support.
| Ring Name | Number of Customers | Description |
|---|---|---|
| Fast Ring | ~10% | First group of customers after the pilot to receive an update. Typically customers with whom we have a particularly close working relationship and can provide timely and quality feedback. |
| Slow Ring | ~20% | Next group of customers to receive and update. Typically a mix of customers with different operational practices and configurations to ensure that an update works correctly in various conditions. |
| Stable Ring | Remainder | Final rollout of a Readysell update to entire customer base. |
See also
- Software bug at Wikipedia