Feature Requests Sample Clauses
The Feature Requests clause outlines the process by which a party, typically the client, can formally request new features or enhancements to a product or service. It usually specifies how requests should be submitted, the evaluation criteria, and whether additional costs or timelines may apply for implementing such features. This clause ensures that both parties have a clear understanding of how new requirements are handled, helping to manage expectations and prevent disputes over scope changes during the project.
POPULAR SAMPLE Copied 1 times
Feature Requests. If Google deems a Request to be a Feature Request, Google will log the Request for consideration to add to a future update or release of the Services and will consider the matter closed. Google has no obligation to respond to or resolve any Feature Request or to include any Feature Request in any future update or release.
Feature Requests. OSA holders may submit Trouble Tickets requesting additional features or functionality be added to the rXg general release software. Trouble Tickets of this nature may be responded to with a description and timing of the modification to a future rXg software release containing the requested functionality. If the feature requested is not scheduled for a future release the Operator may wish to request a quote for the feature to be added within their desired timeframe and expense. These Trouble Tickets will be referred to the designated RG Nets account manager. There is a non-discounted fee for preparing a formal Statement of Work.
Feature Requests. Certain support requests are more accurately viewed as requests for additional features for the System. Where appropriate and in its discretion, Toybox is entitled to treat a User request as a feature request (and not a support request) and to add the request to its roadmap (or reject the request), as it sees fit.
Feature Requests. We encourage users to suggest their ideas for improving the Products/Services. We shall have all rights to such requests, suggestions, and any content that is part of that request.
Feature Requests. As part of the Regular Support Services, Customer may submit Feature Requests to Groundswell in writing. Feature Requests shall be prioritized by Groundswell according to the order in which they are received by Groundswell from its respective customers. Notwithstanding the immediately preceding sentence, in the event the Customer purchases Premium Support, the Feature Requests of the Customer will receive a higher priority than the Feature Requests of customers who did not purchase Premium Support. Groundswell has the right to develop Feature Requests in its sole and absolute discretion. For absolute clarity, Groundswell has no obligation hereunder to develop or provide Feature Requests to the Customer.
Feature Requests. OSA holders may submit Trouble Tickets requesting an additional features or functionality be added to the rXg general release code. Trouble Tickets of this nature may be responded to with a description and timing of an addition or modification to a future rXg revision release containing the requested feature or functionality. If the feature requested is not scheduled for a future release the Operator may wish to request a quote for the feature to be added within their desired timeframe and expense. These tickets will be responded with a quotation for Feature Request Professional Service if the request is deemed by RG Nets to be of value to rXg customers. Completed Feature Requests will be made available in a future revision update and included in the rXg firmware for general release.
Feature Requests. All requests from the Client for Development or Consultancy should be notified to Supplier by one of the following means:
Feature Requests. If a Request is deemed by Learning Objects to be a Feature Request, Learning Objects will log such Feature Request for consideration to include in a future update or release of the Service and
Feature Requests. 6.5.1 We welcome client feedback relating to feature requests. Feedback will be assessed as part of a larger development roadmap and proposed changes will be considered in the context of wider company strategy.