Submitting Custom Requests

Updated by Erik Jensen on Sep 22, 2016
Article Code: kb/369


CenturyLink Cloud offers a robust, self-service cloud environment for building and maintaining complex infrastructure topologies. There are times, however, when native functionality doesn't provide the desired result. In some cases, CenturyLink will approve a custom configuration. We aim to delight every customer in whatever way we can, and thus offer this option. However, the CenturyLink Cloud team is extremely selective about approving non-standard configurations because they introduce the possibility for human error and may cause side effects with system automation.

We encourage customers to submit feature requests for new capabilities, but in the meantime, there is an option to request a non-standard configuration for review.

How should Custom Requests be submitted?

All customer requests (e.g. support, service tasks, product questions) should be sent to If that request requires a custom configuration, the support engineer will route it for approval.

What qualifies as a custom request?

By default, anything that cannot be done via self-service or Service Task is categorized as a Custom Request.

What is the evaluation process?

Custom Requests are sent to a queue monitored by CenturyLink Cloud management. An executive reviews each request and approves or rejects the request after careful consideration (note that a custom request that was approved in the past MAY not get approved a second time). The result of the Custom Request review process is then communicated back to the customer.

How long does it take for a request to get evaluated?

There is no SLA on custom requests, but all items are typically reviewed and acted upon within 72 hours. If the request is urgent then it may be escalated using the how do I escalate a ticket process.

What are the possible outcomes?

After assessing the details of the Custom Request, the CenturyLink Cloud team will either accept or reject the request. If accepted, we will either perform the work outright, or based on complexity, offer to do it as part of a Service Task. The customer can then choose whether or not they wish to still have this work performed.

If the request is rejected, we recommend that the customer submit a feature request so that we can introduce the proposed feature as a first-class capability of the cloud platform.